AI at Bitmovin

Bitmovin is built for AI-augmented developers. Point your AI agent — Claude, Codex, Cursor, Windsurf, GitHub Copilot, ChatGPT — at Bitmovin and have it build, encode, and operate your video workflows directly. This page is the entry point.

Beyond the agent experience, Bitmovin also ships AI products of its own: AI Scene Analysis for video metadata, and the Bitmovin Assistant for in-dashboard chat.

Bitmovin skill — drop us into your AI agent

bitmovin.com/skill is the one-prompt way to give any AI coding agent context on Bitmovin's full product suite. Two paths:

Paste into your AI:

Learn about Bitmovin from bitmovin.com/skill

Or run in your terminal:

npx @bitmovin/skills

The wizard detects your AI tool (Claude Code, Codex, Cursor, Windsurf, Copilot) and installs the canonical Bitmovin skill into the right place. After that, your agent knows how to use Player, VOD/Live Encoding, Observability, AI Scene Analysis, Streams, and Stream Lab — and will walk you through connecting the MCP server below.

Source: github.com/bitmovin/skills.

MCP servers — bring Bitmovin into your own AI tools

We expose our agents over the Model Context Protocol (MCP), so you can connect them to Claude, ChatGPT, Cursor, or any other MCP-compatible client and use Bitmovin's capabilities alongside your other tooling.

One endpoint for everything: mcp.bitmovin.com

mcp.bitmovin.com is the unified Bitmovin MCP server. It aggregates every per-product Bitmovin MCP (encoding, player, documentation, observability, Stream Lab) under a single endpoint, with tools namespaced by product (e.g., encoding_*, player_*, observability_*) so agents can pick the right tool without name collisions.

Most users should start here — one URL, one sign-in, all Bitmovin products.

Authentication

Two ways to authenticate. OAuth is the primary path — most MCP-aware clients (Claude Desktop, ChatGPT, Cursor, Claude.ai connectors) walk you through it automatically when you add the server.

For multi-org accounts, add x-tenant-org-id: <id> (header) in either flow.

Per-product MCP servers

If you only need one product, you can connect to it directly. The unified server above forwards to these exact endpoints, namespacing tools to avoid collisions.

Quick start

Claude Desktop / Cursor / Windsurf / Claude.ai (OAuth)

Add the server URL and follow the in-product sign-in prompt:

{
  "mcpServers": {
    "bitmovin": { "url": "https://mcp.bitmovin.com" }
  }
}

On first use, your client opens a browser to sign you into Bitmovin and stores the resulting tokens.

Claude Code / mcp-remote (API key)

claude mcp add bitmovin --transport http https://mcp.bitmovin.com \
  --header "x-api-key: $BITMOVIN_API_KEY"

npx mcp-remote https://mcp.bitmovin.com \
  --header "x-api-key: $BITMOVIN_API_KEY"

ChatGPT

1. Open chatgpt.com and go to Settings → Connectors.
2. Click Add connector and select MCP.
3. Enter the URL: https://mcp.bitmovin.com
4. Sign in with your Bitmovin account when prompted.
5. Click Save.

Coming soon: Bitmovin is landing as an official app in the ChatGPT App Store — install in one click without copy-pasting the MCP URL.

Claude Marketplace (coming soon)

The Bitmovin connector is landing in the Claude.ai connector directory imminently — install in one click from the marketplace, no MCP URL to copy. We'll link the install button here once it goes live.

Docs-only quick start (no API key)

If you only want to ask Bitmovin documentation questions, connect to the Documentation MCP directly — no auth required:

claude mcp add bitmovin-docs --transport http https://agentic.bitmovin.com/documentation/mcp

Bitmovin CLI — manage everything from your terminal

The Bitmovin CLI is the terminal companion to the dashboard and MCP servers. It covers encoding templates and jobs, inputs/outputs, codec configurations, player licenses, and Analytics queries — ideal for scripting, automation, and CI/CD pipelines.

npm install -g @bitmovin/cli
bitmovin config set api-key YOUR_API_KEY

What it covers:

• Encoding templates — create, validate, start, and monitor YAML-based workflows
• Encoding jobs — list, start, stop, and monitor with live progress
• Inputs/Outputs — manage S3, GCS, Azure, and HTTP storage connections
• Codec configs — list and inspect H.264, H.265, AV1, VP9, and audio configurations
• Player licenses — list and manage license keys and allowed domains
• Analytics — query playback metrics, impressions, and license info

Requires Node.js 20+. Public Beta. Full command reference and install instructions in the bitmovin/cli repo.

AI Scene Analysis

AI Scene Analysis (AISA) is Bitmovin's flagship AI product. It transforms video content into rich, structured metadata by analyzing every scene for context, themes, and visual characteristics — making every content minute discoverable, reusable, and advertisable.

AISA runs as part of your encoding workflow and produces per-scene metadata including:

• Scene boundaries with start/end timestamps
• Summaries and descriptions of each scene
• Visual elements — objects, brands, settings, locations, characters
• Mood and atmosphere — lighting, time of day, weather, sentiment
• IAB taxonomy classifications and keywords for contextual ad targeting
• Sensitive topic flags and content ratings
• Multi-language support — analyze in any language, output in multiple languages

Use cases

• Intelligent ad placement — automatic SCTE marker insertion and keyframe placement at natural scene boundaries, with contextual ad matching via IAB taxonomies. Integrates with AWS MediaTailor, Broadpeak, and SpringServe.
• Content discovery — feed scene-level metadata into recommendation engines and search.
• Operational automation — highlights extraction, metadata generation, subtitle and caption workflows.
• Player enhancements — contextual overlays and interactive features powered by scene metadata.
• Performance analytics — correlate viewer engagement with scene context to identify what works.

To get started, see the full AI Scene Analysis documentation.

Bitmovin Assistant

The Bitmovin Assistant is a chat-based AI assistant built into the Bitmovin Dashboard. It gives you a single conversation surface for navigating the product, inspecting your encodings, searching documentation, finding SDK examples, and querying your Observability data.

No setup required — sign in and start asking questions at dashboard.bitmovin.com/assistant.

Under the hood

• The Bitmovin skill is plain markdown served from bitmovin.com/skill and installed into your agent's local context — no model or service runs on Bitmovin's side for skill use.
• The MCP servers do not ship any AI model. They are tool servers — your chosen MCP client's model does the reasoning. mcp.bitmovin.com is a thin aggregator that validates incoming OAuth tokens (or x-api-key), namespaces tools by product, and forwards calls to the per-product MCPs; the agentic MCPs at agentic.bitmovin.com wrap agents that orchestrate retrieval, docs search, and product calls; Observability and Stream Lab are thin wrappers over the Bitmovin REST API.
• AI Scene Analysis runs during encoding and produces structured metadata — no separate service to manage.
• The Bitmovin Assistant uses its own LLM behind the scenes — see Bitmovin Assistant for details.

Data handling

• The Bitmovin skill is static markdown — no user data, no requests back to Bitmovin when an agent reads it.
• The unified mcp.bitmovin.com server doesn't persist user data — it verifies your OAuth token or x-api-key, forwards calls to the appropriate per-product MCP, and returns the result. Scoping is identical to calling the per-product MCPs directly.
• The Documentation MCP uses only public Bitmovin documentation and public SDK example repositories.
• The Encoding, Observability, and Stream Lab MCPs scope every call to the API key you provide — they can only see data your key already has access to.
• The Player MCP is stateless — it accepts a stream URL and player config from the chat client and returns a rendered player; it does not persist your streams.
• AI Scene Analysis processes your video content during encoding. The generated metadata is stored with your encoding output and is accessible via the Bitmovin API.