Adobe for creativity
Edit photos, cut video and design from templates via an AI agent.
Query Bitmovin playback analytics, debug encodings, render a player and run Stream Lab tests from Claude.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Bitmovin MCP server connects Claude to the Bitmovin video platform through one endpoint: query playback analytics, inspect and debug encodings, render a Bitmovin Player in the chat, run Stream Lab playback tests, search the docs and file support tickets. Anthropic lists 57 tools. Sign-in is Bitmovin OAuth, or an API key for headless use.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
x-tenant-org-id.streamlab_getLimits exists, but we could not find whether test runs draw on a paid quota.Yes, for headless use such as CI or scripts. Bitmovin says OAuth is the default and recommended path, but you can send an API key as an Authorization Bearer header. It must not go in x-api-key: Bitmovin's edge requires an Authorization header on every request and rejects an x-api-key-only request with a 401 before it reaches the server.
Use an API key with an x-tenant-org-id header naming the sub-organization. Bitmovin states the organization is fixed for the life of a connection, so switching means reconnecting. The Claude custom-connector path is OAuth-only and cannot carry custom headers, so multi-org users who need a sub-organization should use Claude Code or a desktop config with headers instead.
Because tool visibility follows your access. Bitmovin's documentation says the tools you actually see depend on what your API key or account can reach. An account without Stream Lab, Observability or Encoding access will get a shorter list than the 57 tools in Anthropic's directory, and each call is scoped to the credential you presented.
No, according to Bitmovin. Its data-handling notes say the server verifies your credential, forwards each call to the owning service and returns the result without persisting user data. Player tools are stateless and do not keep your stream URLs. The server ships no AI model of its own; your MCP client's model does the reasoning.
initialize returned 401 with resource_metadata; descriptor at https://mcp.bitmovin.com/.well-known/oauth-protected-resource — 2026-11-18 · retrieved 2026-11-18Connect Bitmovin once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.