Brightcove adds video management to Claude, with approval required for changes

Brightcove users can now ask Claude to work with their video libraries, live streams and analytics in plain language. Added to Claude in October 2026, the Brightcove connector reaches beyond retrieving information: it supports operational changes, too. Its listing says the assistant must ask for confirmation before running tools that change or delete data.

From a video library to live operations

Made by Brightcove, the connector uses the company’s MCP server to link Claude to a Brightcove account. The listing describes roughly 460 tools across the platform. That scope includes both the content itself and the systems used to organize, publish, measure and control access to it.

For library work, supported tasks include searching, creating and updating videos, playlists, folders, labels and custom fields. Users can also start and monitor ingests—the process of bringing video into the platform—and manage captions, audio tracks and metadata, the descriptive information attached to content.

The operational scope extends into several other parts of Brightcove:

• Players and live video: Create and configure players and embeds, and create and manage live jobs and schedules.
• Measurement and access: Query video and account analytics, and manage playback authorization, playback rights and delivery rules.
• Other platform services: Work with Gallery, Interactivity, Audience and Social, plus Cloud Playout channels and server-side advertising configurations.

An enabled account is the starting point

Using the connection requires a Brightcove account with the MCP server enabled. The software connecting to that server must support remote MCP servers and OAuth sign-in. The listing supplies https://mcp.brightcove.com/mcp as the connector’s server address.

Sign-in uses OAuth 2.0, and every action runs under the user’s Brightcove account permissions. The account’s authority and the confirmation prompt are separate controls: permissions govern what the connection can do, while confirmation applies before a supported tool changes or deletes data.

The verification label has limits

The directory labels the connector Anthropic verified, but its trust warning places an important limit on that designation. Anthropic says it does not control which tools developers make available and cannot verify that they will work as intended or remain unchanged. It advises users to connect only to developers they trust.