# Bitmovin Observability MCP server

> Query Bitmovin video analytics: playback metrics, trends, breakdowns and single-session troubleshooting for your licenses.

- Listing: https://mcp.tc/i/bitmovin-observability
- Connect: use the server's own URL `https://analytics.mcp.bitmovin.com` (with your API key); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: API key
- Category: [Data & Analytics](https://mcp.tc/c/analytics)
- Vendor: Bitmovin
- Homepage: <https://bitmovin.com>
- Docs: <https://developer.bitmovin.com/playback/docs/bitmovin-observability-mcp-server>

## About

Connects to Bitmovin Observability (video analytics) and lets an assistant query playback metrics for a license over a time range. It can return time series, aggregated totals, and breakdowns by category such as browser or device, including ad metrics. It can also list individual playback sessions (impressions) and analyze one in detail.

Runs as a hosted streamable HTTP endpoint at analytics.mcp.bitmovin.com. The registry entry lists an x-api-key header, found in Account Settings in the Bitmovin Dashboard. All listed tools are read-only. Bundled prompts cover license summaries, daily checks and impression comparison.

## What it can do

- Chart a metric as a time series over a date range
- Get totals, averages or percentiles for one or more metrics
- Group metrics by categories such as browser or device
- List all licenses with recent play counts
- List playback session ids with filters
- Analyze a single session with a state timeline and interpretation
- Search the metric and filter catalogs for exact keywords

## Tools (11)

- `query`: Chart a metric as a time series over a start/end range for a license. (read-only)
- `queryGroupBy`: Query a metric grouped by categories, including ad metrics. (read-only)
- `queryTotal`: Get one aggregated value per metric over a period, without a chart. (read-only)
- `peekAllLicenses`: Summarize available licenses with recent play counts and share. (read-only)
- `getImpressionOverview`: Show static properties and aggregated metrics for one playback session. (read-only)
- `analyzeImpression`: Deep-dive on one session with timeline and AI interpretation of quality. (read-only)
- `fetchImpressions`: List impression ids for a license and time range, with optional filters. (read-only)
- `getAvailableMetrics`: List the full metric catalog with supported aggregations. (read-only)
- `getAvailableFilters`: List the full filter attribute catalog with supported operators. (read-only)
- `searchMetrics`: Find the exact metric keyword for a topic or question. (read-only)
- `searchFilters`: Find the exact filter or group-by attribute keyword for a topic. (read-only)

## Example prompts

- "Show plays for my main license over the last 30 days"
- "What was the p95 startup time yesterday?"
- "Break down rebuffering by browser for last week"
- "List errored sessions on Safari and analyze one of them"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http bitmovin-observability https://analytics.mcp.bitmovin.com --header "x-api-key: <YOUR_API_KEY>"
```

2. Replace the placeholder with your key before you run it, then check it with `/mcp` inside Claude Code.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Use the `mcp-remote` bridge, which keeps the key on this computer (a connector added on claude.ai with the key under **Request headers** also shows up here). Open **Settings → Developer → Edit Config** and add:

`claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "bitmovin-observability": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://analytics.mcp.bitmovin.com",
        "--header",
        "x-api-key: <YOUR_API_KEY>"
      ]
    }
  }
}
```

2. Replace the placeholder with your key and restart Claude Desktop.

The bridge needs Node.js on your computer.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Bitmovin%20Observability&connectorUrl=https%3A%2F%2Fanalytics.mcp.bitmovin.com>) (opens connector settings)

2. Check that the URL reads `https://analytics.mcp.bitmovin.com`. Under **Request headers**, add `x-api-key: <YOUR_API_KEY>` with your key from Bitmovin, then click **Add**.

3. Turn it on in a chat from the tools menu.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=bitmovin-observability&config=eyJ1cmwiOiJodHRwczovL2FuYWx5dGljcy5tY3AuYml0bW92aW4uY29tIiwiaGVhZGVycyI6eyJ4LWFwaS1rZXkiOiI8WU9VUl9BUElfS0VZPiJ9fQ%3D%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "bitmovin-observability": {
      "url": "https://analytics.mcp.bitmovin.com",
      "headers": {
        "x-api-key": "<YOUR_API_KEY>"
      }
    }
  }
}
```

### VS Code

Add it to `.vscode/mcp.json`. VS Code asks for the key the first time and stores it securely:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "bitmovin-observability": {
      "type": "http",
      "url": "https://analytics.mcp.bitmovin.com",
      "headers": {
        "x-api-key": "${input:x-api-key}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "x-api-key",
      "description": "x-api-key",
      "password": true
    }
  ]
}
```

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "bitmovin-observability": {
      "serverUrl": "https://analytics.mcp.bitmovin.com",
      "headers": {
        "x-api-key": "<YOUR_API_KEY>"
      }
    }
  }
}
```

2. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add bitmovin-observability --url https://analytics.mcp.bitmovin.com
```

`codex mcp add` can’t set the `x-api-key` header, so this step is required: put this entry in `~/.codex/config.toml` instead of running the command, or add its `env_http_headers` line to the entry the command made:

`config.toml`:

```toml
[mcp_servers.bitmovin-observability]
url = "https://analytics.mcp.bitmovin.com"
env_http_headers = { "x-api-key" = "X_API_KEY" }
```

Codex reads the header values from the environment variables named in `env_http_headers`.

### Gemini CLI

```bash
gemini mcp add --transport http --header "x-api-key: <YOUR_API_KEY>" bitmovin-observability https://analytics.mcp.bitmovin.com
```

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "bitmovin-observability": {
      "type": "http",
      "url": "https://analytics.mcp.bitmovin.com",
      "headers": {
        "x-api-key": "<YOUR_API_KEY>"
      }
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://analytics.mcp.bitmovin.com`.

## Recent changes

- 2026-10-06 21:22 UTC: Tracking started: 11 tools read. Source: automatic check.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/bitmovin-observability#history (Atom feed: https://mcp.tc/i/bitmovin-observability/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 0.0.1
- MCP protocol version: 2025-11-25
- Last checked: 2026-10-07 (reachable)
- Listed: 2026-10-05
- Updated: 2026-10-07

---
Source: https://mcp.tc/i/bitmovin-observability (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
