MCP Analytics
ai.mcpanalytics/analyticsVersion 1.0.8A statistical analyst in your AI chat: bring data and a question, get a citable, re-runnable report.
Status
Responds582 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 13:31 UTC
- Latency
- 582 ms
- Remotes responding
- 1 of 1
- Sign-in
- API key
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 21:12 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://api.mcpanalytics.ai/mcp/api-keyResponds582 msNo sign-in
Claude Code
claude mcp add --transport http analytics https://api.mcpanalytics.ai/mcp/api-key --header 'X-API-Key: <YOUR_X_API_KEY>'Replace <YOUR_X_API_KEY> before running.
Claude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: analytics
Remote MCP server URL: https://api.mcpanalytics.ai/mcp/api-key
This server expects the header X-API-Key.Cursor
{
"mcpServers": {
"analytics": {
"url": "https://api.mcpanalytics.ai/mcp/api-key",
"headers": {
"X-API-Key": "<YOUR_X_API_KEY>"
}
}
}
}Replace <YOUR_X_API_KEY> before running.
VS Code
code --add-mcp '{"name":"analytics","type":"http","url":"https://api.mcpanalytics.ai/mcp/api-key","headers":{"X-API-Key":"<YOUR_X_API_KEY>"}}'Replace <YOUR_X_API_KEY> before running.
Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
27 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
aboutPlatform documentation and info: how it works (Answer, Analytics, Custom Analytics), usage. | No | Yes | Yes | No |
account_linkDirect 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. | No | Yes | Yes | No |
adjust_estimateApply the user's layout wishes to the estimate's page through the layout agent; a new named arrangement, nothing overwritten, no number changes. | No | No | No | No |
agent_advisorAI help desk: which analysis fits your question, interpreting results, fixing errors. Multi-turn. | No | Yes | Yes | No |
ask_libraryAsk a question across all your delivered analyses: a synthesized answer with citations back to specific reports. | No | Yes | Yes | No |
build_statusCheck 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. | No | Yes | Yes | No |
check_tool_fitBefore naming a library tool: does it fit THIS dataset for THIS question? Column mapping, missing required inputs, method-fit verdict, the places it delivers. Read-only. | No | Yes | Yes | No |
datasets_listList and search your uploaded datasets, with fuzzy matching on name, description, and tags. Returns each dataset's uuid:// reference (the `usage` field) for use as dataset_ref in path_resolver and path_tool_run. The id alone ('uuid://dsv2_...') also works for your own datasets and the platform sample; `dataset_key` may be null for the sample, which is normal. | No | Yes | Yes | No |
datasets_uploadGet your data in. Pass `data` as an array of row objects to create the dataset immediately and get a dataset_ref ready for path_resolver; 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. | No | No | No | No |
discover_toolsBrowse 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 path_resolver. | No | Yes | Yes | No |
find_precedentBefore estimating: how did we answer this objective before, on this data or any data? Prior packages and library runs with their tools, mappings, bespoke module names, method and verdicts. Platform-wide, read-only. | No | Yes | Yes | No |
my_objectsList and search the objects you own across every question: the curated charts, tables and figures of each delivered package, grouped by objective. | No | Yes | Yes | No |
package_statusRead an analytics package back: status, every run under it, the report link once delivered. | No | Yes | Yes | No |
path_answerA read of the data (a total, an average, a count, the top group), computed on every row, in this response. When the question is not a read it says so and names the next step. Time: as path_resolver quotes.
No key yet? Call it with objective and data (a small table, up to 200 rows): a read of that table comes back now, nothing stored. Sign-in is needed to save, re-run, or ask for more than a read. | No | Yes | Yes | No |
path_bespokeOrder a custom analysis built for this data from a confirmed estimate, optionally with library tools alongside. Needs the person's yes and an idempotency key; a retry returns the first order. Time: as path_resolver quotes. | No | No | No | No |
path_estimateA rough answer over a sample and the layout of the full report, for the person to confirm before anything is ordered. Time: as path_resolver quotes. | No | No | No | No |
path_rerunRun a delivered analysis again, on its own dataset or a new one: the same tools and mappings, no rebuild. package_id may also be the person's own report link (a /rpt/ link or its rpt_ token) or estimate id (est_); it reruns their newest delivered package for it. Time: as path_resolver quotes. | No | No | No | No |
path_resolverWhich path a question about data should take (reuse, rerun, answer, tool_run, estimate, bespoke, ask or none), with the reason, every path's score and time, and the ready input for the path it picks. Executes nothing and charges nothing. | No | Yes | Yes | No |
path_reuseHand back the report already delivered for this question on this data. Time: as path_resolver quotes. | No | Yes | Yes | No |
path_tool_runRun one or more tested library tools on this dataset, with charts and a written report. No custom build. Time: as path_resolver quotes. | No | No | No | No |
report_cardsBrowse a delivered report's individual cards (charts, tables, insights) inline in chat. | No | Yes | Yes | No |
reports_listYour report library: every analysis delivered, with status and links. Pass semantic_query to search report content in plain language. | No | Yes | Yes | No |
reports_viewGet a shareable browser link for a report, viewable without authentication. | No | Yes | Yes | No |
review_estimateThe estimate as you review it WITH the user: the question as understood, the estimated answer (sample, marked), every place and its question, the page link, a review checklist. Before path_bespoke. | No | Yes | Yes | No |
schedulesStanding 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'. | Yes | No | No | No |
tools_schemaGet an analysis's parameter schema. ALWAYS call before path_tool_run. | No | Yes | Yes | No |
warehouseQuery 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). | No | Yes | Yes | No |
Details
- Registry status
- Active
- Published
- Oct 15, 2026
- Updated
- Oct 15, 2026
- Categories (suggested)
- Data and analyticsSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared