Model Context Protocol server for Rollbar
Analytics 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.
What it does
The statistical analyst in your AI chat — validated, citable, re-runnable analysis of your data.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http analytics-mcp https://api.mcpanalytics.ai/mcp/api-key
# 2 — ask your agent for something these tools do
# account_link, about, agent_advisor and 14 more
Analytics costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
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.
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 analytics-mcp https://api.mcpanalytics.ai/mcp/api-keyReconnect, or start a new session, and the tools appear in the model’s tool list.
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.
17 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.
Direct link to the right account page for anything not doable in chat: billing, browser upload, report management. Hand the user the link and guide them.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| section | string | no | Where to send the user |
Platform documentation and info: how it works, tiers, usage.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | yes | Topic: platform, manual, connectors, or a docs section |
AI help desk: which analysis fits your question, interpreting results, fixing errors. Multi-turn.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| message | string | yes | Your question or request |
Get your data in. Pass data as an array of row objects to create the dataset immediately and get a dataset_ref ready for create_analysis; omit it to get an upload link for a file only the user can reach. Add replace_ref (uuid://ID:KEY) with data to REFRESH an existing dataset in place; schedules and tools holding that reference read the new data on their next run.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| data | array | no | Rows as an array of flat objects — creates the dataset in one call |
| replace_ref | string | no | uuid://ID:KEY of an existing dataset to overwrite in place with data (the push/refresh mode) |
| expires_in | integer | no | Token expiration in seconds |
List and search your uploaded datasets, with fuzzy matching on name, description, and tags. Returns each dataset's uuid:// reference for use in create_analysis and run_analysis.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| search | string | no | Search by name, description, or tags |
| limit | integer | no | Max results |
Browse the analyses you can run: the ones you commissioned plus the platform Standard Library (prebuilt tools; each result tagged source:'own' or 'standard_library'). Plain-language match; no query lists everything, your own first. Nothing fits? Commission it with create_analysis.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Plain-language search over your library + the Standard Library; omit to list everything |
Get an analysis's parameter schema. ALWAYS call before run_analysis.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tool_name | string | yes | Name of the analysis |
Run an analysis on your data. Returns a shareable interactive report URL with validated statistics you can cite, re-run, and share.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tool_name | string | yes | Name of the analysis to run |
| taskList | object | yes | Execution inputs. Call tools_schema first for the analysis-specific fields. |
Commission a NEW analysis built for your question. tier is REQUIRED. The user picks. Easiest: fuzzy_request (plain language) + dataset_ref + tier. Snapshot = instant automated report (~2-10 min). JSON = a fast computed answer, numbers + method, re-runnable tool you own (~5 min). Brief = the computed answer on a one-page report: chart, numbers, method (~7 min). Deck = commissioned deep analysis, a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fuzzy_request | string | no | Plain-language description of the analysis you want |
| dataset_ref | string | no | Single-dataset URI: 'uuid://UUID:KEY' |
| datasets_refs | object | no | Multi-dataset URIs keyed by role |
| tier | string | no | snapshot = instant report (~2-10 min); json = fast computed answer (~5 min, default); brief = one-page report of the answer (~7 min); deck = commissioned re-runnable module (30-45 min) |
| specification | object | no | Full 11-field spec (legacy path — prefer fuzzy_request) |
| column_mapping | object | no | Optional semantic-to-real column map (hint only) |
| notes | string | no | Optional context for the build — constraints, definitions, or preferences the analyst agents should honor |
Modify an EXISTING analysis into a new version: reword the question, swap the method, or add a variable. Pass tool_name + changes (plain language). Rebuilds on the analysis's own dataset by default; the original stays put. Returns pipeline tracking. Follow with build_status.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tool_name | string | yes | The analysis to modify (from discover_tools or your library) |
| changes | string | yes | What to change, in plain language, e.g. 'also break it down by region' or 'use a random forest instead' |
| tier | string | no | Optional — change the depth of the new version |
| dataset_ref | string | no | Optional — rebuild against a different dataset ('uuid://UUID:KEY') |
Check a commissioned build in-chat: stage progress, queue position, rejection reason if the data didn't match the objective, honest ETA, report link when delivered.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| pipeline_id | integer | no | pipeline_id from create_analysis |
| track_token | string | no | Token from the tracking URL |
Ask a question across all your delivered analyses: a synthesized answer with citations back to specific reports.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | Plain-language question to answer from your report library |
Your report library: every analysis delivered, with status and links. Pass semantic_query to search report content in plain language.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| semantic_query | string | no | Natural-language search over your reports' content |
| limit | integer | no | Max results |
Query your org's data warehouse free: browse the catalog (tables with column roles + computed metrics), semantically find data, plain-language ask, or named templates. Requires warehouse enablement (business plans).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| action | string | yes | — |
| question | string | no | — |
| query | string | no | — |
| params | object | no | — |
Standing re-runs of analyses you own: action='create' (weekly/monthly against a re-runnable data reference, connector:// or an https:// link; report emailed after each run), 'list', or 'cancel'.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| action | string | yes | What to do |
| tool_name | string | no | create: the analysis to schedule |
| dataset_ref | string | no | create: re-runnable reference (connector:// or https://) |
| cadence | string | no | — |
| column_mapping | object | no | — |
| schedule_id | integer | no | cancel: from action='list' |
Get a shareable browser link for a report, viewable without authentication.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| processing_id | string | yes | Processing ID from run_analysis / reports_list |
Browse a delivered report's individual cards (charts, tables, insights) inline in chat.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| processing_id | string | yes | The report's processing id, returned by run_analysis or build_status |
- 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 Analytics or to call it, at any volume.
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 1.0.5.
No release note was published with this version.
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.
Any signed-in account that does not publish Analytics can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.