Model Context Protocol server for Rollbar
Nothing to run from here
Bitmovin Observability is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
11
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Query and analyse your data from Bitmovin Observability
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http bitmovin-observability-mcp https://analytics.mcp.bitmovin.com
# 2 — ask your agent for something these tools do
# query, queryGroupBy, queryTotal and 8 more
Bitmovin Observability costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
BIAll 1 server
bitmovin1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http bitmovin-observability-mcp https://analytics.mcp.bitmovin.comReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
11 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 analytics over a period (e.g. 'last week', 'last 30 days', 'yesterday'). Bucket size is chosen automatically from start/end; there is no interval field to set. For a single aggregated number (one total/average over the whole period, NO chart), use the separate
| Parameter | Type | Required | Notes |
|---|---|---|---|
| licenseKey | string | yes | license key (uuid) to query |
| metric | string | yes | the metric to query. before setting a value, resolve the keyword with the searchMetrics tool |
| start | string | yes | start date/time in ISO 8601 format (e.g., '2025-10-01T00:00:00') |
| end | string | yes | end date/time in ISO 8601 format (e.g., '2025-10-02T00:00:00') |
| aggregation | string | no | aggregation method: 'average', 'median', or 'percentile'. If not specified, uses the metric's default aggregation method |
| percentile | number | no | percentile value (0-100) - required when aggregation is 'percentile' |
| filters | array | no | optional filters to apply to the query |
query metric grouped by categories. Queries resolve against API metric keywords, which can differ from a metric's common name — 'plays', for example, is 'impression_id'. The 'searchMetrics' tool resolves a keyword cheaply; 'getAvailableMetrics' returns the full catalog. Every query needs a licenseKey; peekAllLicenses lists the ones available. AD ANALYTICS: ad metrics use 'ad_'-prefixed keywords
| Parameter | Type | Required | Notes |
|---|---|---|---|
| licenseKey | string | yes | license key (uuid) to query |
| metric | string | yes | the metric to query. before setting a value, resolve the keyword with the searchMetrics tool |
| start | string | yes | start date/time in ISO 8601 format (e.g., '2025-10-01T00:00:00') |
| end | string | yes | end date/time in ISO 8601 format (e.g., '2025-10-02T00:00:00') |
| groupBy | yes | category (or array of categories) to group results by — e.g. Case-insensitive: ['BROWSER', 'COUNTRY'] or just 'BROWSER'. Prefer an array even for a single value. Use the searchFilters tool (pass the | |
| aggregation | string | no | aggregation method: 'average', 'median', or 'percentile'. If not specified, uses the metric's default aggregation method |
| percentile | number | no | percentile value (0-100) - required when aggregation is 'percentile' |
| filters | array | no | optional filters to apply to the query |
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: pass an array to metric to get one value per metric (e.g. the ad completion funnel), instead of calling this tool repeatedly. Use ONLY when the user asks for totals/averages/median/p95 over a whole period (e.g. 'total plays last month', 'average startup time y
| Parameter | Type | Required | Notes |
|---|---|---|---|
| licenseKey | string | yes | license key (uuid) to query |
| metric | yes | the metric to query: a single keyword, or an array of up to 6 keywords resolved together in one call, which returns one value per metric. A multi-metric ask such as the ad completion funnel is one arr | |
| start | string | yes | start date/time in ISO 8601 format (e.g., '2025-10-01T00:00:00') |
| end | string | yes | end date/time in ISO 8601 format (e.g., '2025-10-02T00:00:00') |
| aggregation | string | no | aggregation method: 'average', 'median', or 'percentile'. If not specified, uses the metric's default aggregation method |
| percentile | number | no | percentile value (0-100) - required when aggregation is 'percentile' |
| filters | array | no | optional filters to apply to the query |
View a summary of all available licenses with their recent play counts and percentage distribution. Use this to understand what licenses exist and their relative usage. When a user asks about licenses by ranking (e.g., 'biggest', 'most active', 'first'), use this to identify which license matches that criteria before querying.
No parameter schema on file.
Inspect a SINGLE playback session identified by a specific impressionId. Returns that one session's static properties (device, location, player) and its aggregated metrics (total played time, buffering, video quality). REQUIRES an impressionId. Do NOT use this for license-wide metrics, totals, trends, or any time-range ('last week', start/end) analysis — this tool does not accept start/end. For me
| Parameter | Type | Required | Notes |
|---|---|---|---|
| impressionId | string | yes | Impression ID |
| licenseKey | string | yes | license key (uuid) to query |
Deep-dive analysis of a SINGLE playback session identified by a specific impressionId: static properties, aggregated metrics, state-transition timeline, and an AI-powered interpretation of session quality. Use for detailed single-session troubleshooting. REQUIRES an impressionId. Do NOT use this for license-wide metrics, totals, trends, or any time-range ('last week', start/end) analysis — this to
| Parameter | Type | Required | Notes |
|---|---|---|---|
| impressionId | string | yes | Impression ID |
| licenseKey | string | yes | license key (uuid) to query |
List the impression ids (individual playback session ids) for a license over a time range, optionally narrowed by filters. Returns the ids themselves — NOT counts, totals, or trends. Use this to enumerate sessions before drilling into specific ones with getImpressionOverview or analyzeImpression. Typical uses: 'give me impression ids from yesterday', 'list sessions on Safari that errored last
| Parameter | Type | Required | Notes |
|---|---|---|---|
| licenseKey | string | yes | license key (uuid) to query |
| start | string | yes | start date/time in ISO 8601 format (e.g., '2025-10-01T00:00:00') |
| end | string | yes | end date/time in ISO 8601 format (e.g., '2025-10-02T00:00:00') |
| filters | array | no | optional filters to apply to the query |
| limit | integer | no | maximum number of impression ids to return (1-200, default 100) |
List the full catalog of metrics with their supported aggregation methods. Prefer searchMetrics to resolve a single keyword; use this only when you need every metric.
No parameter schema on file.
List the full catalog of filter attributes with their supported operators. Prefer searchFilters to resolve a single attribute; use this only when you need every filter.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| licenseKey | string | no | license key (uuid) to query |
Find the exact metric keyword for a topic or question (e.g. 'buffering', 'how many errors'). Preferred way to resolve a metric keyword; use getAvailableMetrics only to list the full catalog.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | free-text term or question describing the metric/filter you want (e.g., 'buffering', 'browser', 'how many errors') |
| limit | integer | no | maximum number of results to return (default 5) |
Find 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; use 'licenseKey' to resolve custom namings of attributes; use getAvailableFilters only to list the full static catalog.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | free-text term or question describing the metric/filter you want (e.g., 'buffering', 'browser', 'how many errors') |
| limit | integer | no | maximum number of results to return (default 5) |
| licenseKey | string | no | license key (uuid) to query |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Bitmovin Observability or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.0.1.
0.0.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Bitmovin Observability can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.