Categories › Cloud & DevOps › Monitoring, logs & incidents
Query and analyse your data from Bitmovin Observability
Remote server: your requests and data go to analytics.mcp.bitmovin.com. Claude Code: claude mcp add --transport http bitmovin-observability-mcp https://analytics.mcp.bitmovin.com · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
query — Query 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 aqueryGroupBy — query metric grouped by categories. Queries resolve against API metric keywords, which can differ from a metric's common name — 'plays', forqueryTotal — Get an aggregated value (one number) for a metric over a time range — no chart, no time bucketing. Can fetch SEVERAL metrics in one call: papeekAllLicenses — View a summary of all available licenses with their recent play counts and percentage distribution. Use this to understand what licenses exigetImpressionOverview — The facts of a SINGLE playback session identified by an impressionId, together with the findings evaluated over them. Facts cover the sessioanalyzeImpression — Deep-dive analysis of a SINGLE playback session identified by a specific impressionId: static properties, aggregated metrics, state-transitifetchImpressions — List the impression ids (individual playback session ids) for a license over a time range, optionally narrowed by filters. Returns the ids tgetAvailableMetrics — List the full catalog of metrics with their supported aggregation methods. Prefer searchMetrics to resolve a single keyword; use this only wgetAvailableFilters — List the full catalog of filter attributes with their supported operators. Prefer searchFilters to resolve a single attribute; use this onlysearchMetrics — Find the exact metric keyword for a topic or question (e.g. 'buffering', 'how many errors'). Preferred way to resolve a metric keyword; use searchFilters — Find the exact filter/group-by attribute keyword for a topic or question (e.g. 'browser', 'device type', 'content tier'). Preferred way to rNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.