Bitmovin Observability MCP: playback analytics by asking

Bring Bitmovin playback data into your AI app

1. 1Click Connect Bitmovin Observability free. There's no sign-in, so its tools are ready at once.
2. 2All 11 tools query or look up data. Keep `query`, `queryGroupBy` and `analyzeImpression` for most analysis, and switch off `peekAllLicenses` if people shouldn't see play counts for every license.
3. 3Add ContextGate to your AI app as a connector or MCP server. The steps for each app are on the Works with page.
4. 4Ask your AI app how buffering changed on your license last week, then open Activity to see the `searchMetrics` and `query` calls.

Playback questions you can ask

• Chart a metric over a time range with `query`, or get one total with `queryTotal`.
• Break a metric down by category, such as browser or device type, with `queryGroupBy`.
• Deep-dive a single playback session's timeline and findings with `analyzeImpression`.
• Find the right metric keyword for a question about buffering or errors with `searchMetrics`.

Control over license data

• Switch off `peekAllLicenses` or any other tool; it's hidden from your AI app and refused if called.
• Activity records every query your team runs against Bitmovin.

What you get with Bitmovin Observability and ContextGate

• Your AI apps can use Bitmovin ObservabilityClaude, Cursor, ChatGPT and other AI apps reach Bitmovin Observability through the one ContextGate connection you add to them.
• You choose which tools they can useSwitch off any Bitmovin Observability tool you don't want used. It's hidden from your AI apps and refused if called.
• Every call is checked and recordedYour policies check each call (for example, personal data is hidden and secrets are blocked), and Activity keeps a record of it.

ContextGate sees only the tool calls that go through it, not your AI app's built-in tools or your chats.

Bitmovin Observability tools

Examples of what your AI apps can do in Bitmovin Observability. You'll see the exact list of tools after you connect it.

• queryQuery a metric over a time range (start/end) for a license as a TIME SERIES — always renders a chart. Use this for trends and license-wide analytics over a peri
• queryGroupByquery metric grouped by categories. Queries resolve against API metric keywords, which can differ from a metric's common name — 'plays', for example, is 'impres
• queryTotalGet an aggregated value (one number) for a metric over a time range — no chart, no time bucketing. Can fetch SEVERAL metrics in one call: pass an array to `metr
• peekAllLicensesView a summary of all available licenses with their recent play counts and percentage distribution. Use this to understand what licenses exist and their relativ
• getImpressionOverviewThe facts of a SINGLE playback session identified by an impressionId, together with the findings evaluated over them. Facts cover the session context (device, l
• analyzeImpressionDeep-dive analysis of a SINGLE playback session identified by a specific impressionId: static properties, aggregated metrics, state-transition timeline, and an
• fetchImpressionsList the impression ids (individual playback session ids) for a license over a time range, optionally narrowed by filters. Returns the ids themselves — NOT coun
• getAvailableMetricsList the full catalog of metrics with their supported aggregation methods. Prefer searchMetrics to resolve a single keyword; use this only when you need every m
• getAvailableFiltersList the full catalog of filter attributes with their supported operators. Prefer searchFilters to resolve a single attribute; use this only when you need every
• searchMetricsFind the exact metric keyword for a topic or question (e.g. 'buffering', 'how many errors'). Preferred way to resolve a metric keyword; use getAvailableMetrics
• searchFiltersFind the exact filter/group-by attribute keyword for a topic or question (e.g. 'browser', 'device type', 'content tier'). Preferred way to resolve an attribute;