Brightcove MCP Server

The Brightcove MCP server connects AI assistants such as Claude and ChatGPT to your Brightcove account. This topic explains how to connect the server, sign in, and fix common problems.

Introduction

The Brightcove MCP server connects AI assistants to your Brightcove account. It uses the Model Context Protocol (MCP), an open standard for giving an assistant a set of tools it can call. After you connect an assistant and sign in, the assistant can work with the videos, players, live streams, analytics, and other resources your account is entitled to.

Brightcove hosts the server at this address:

https://mcp.brightcove.com/mcp

The server is remote. It uses the standard MCP transport (Streamable HTTP) and the standard OAuth 2.0 authorization flow, so any MCP client that supports remote servers with OAuth can connect to it.

Requirements

  • An MCP client that supports remote servers with OAuth. Common clients are Claude, ChatGPT, and Claude Code.
  • A Brightcove account with the MCP server enabled. Contact your account administrator or Brightcove Support if you are not sure whether your account is enabled.
  • A user who has the permissions for the operations you want the assistant to run. For accounts that use Roles and Permissions, the user also needs the MCP access role.

Connect the server

The exact steps depend on the assistant, but the flow is the same:

  1. Open the connector or MCP server settings in the assistant.
  2. Add a remote MCP server and enter https://mcp.brightcove.com/mcp as its address.
  3. Start the connection. The assistant opens a Brightcove sign-in page.
  4. Sign in with your Brightcove account and approve the connection.
  5. Return to the assistant and confirm that the Brightcove tools are available.

Available tools

The server exposes tools across the Brightcove platform. The tools that a user can call depend on the account and on the user's permissions. The main product areas are:

Tool areas
Area Examples
Content and CMS Search, create, and update videos, playlists, folders, and labels
Ingest Create ingest jobs and manage captions, audio tracks, and metadata
Players Create and update players and embeds
Live Create and manage live jobs and schedules
Analytics Query video and account analytics
Playback and delivery Playback authorization, playback rights, and delivery rules
Engagement Gallery, Interactivity, Audience, and Social
Cloud Playout and SSAI Channels, schedules, and server-side ad insertion

Tools that change or delete data are marked as destructive, so your assistant asks for confirmation before it runs them.

Troubleshooting

Common problems
Symptom Cause Solution
The assistant cannot connect The client does not support remote MCP servers with OAuth Use a client that supports remote MCP servers over Streamable HTTP with OAuth
The connection is rejected The MCP server is not enabled for the account Ask your account administrator or Brightcove Support to enable it
A tool returns a permission error The signed-in user does not have the permission for that operation Grant the permission to the user. For accounts that use Roles and Permissions, also grant the MCP access role.
No tools appear, or the client reports too many tools The client loads the whole catalog at once Use a client that supports dynamic tool loading
The connection stops working after a while The access token expired Reconnect the server and sign in again

Responsibilities

Brightcove supplies the MCP server. The AI assistant you connect is a separate product that you choose and manage. You are responsible for the security, compliance, and behavior of that assistant and of any third-party service it calls.

Brightcove does not manage, endorse, or secure third-party AI assistants or MCP servers, and does not control how an assistant uses, stores, or shares the account data it retrieves. Review the assistant's own privacy and security documentation before you connect it.

For more information, see the Brightcove privacy policy.