MCP Analytics is answering right now. Last checked 2 min ago. It exposes 27 tools. Last commit 26 Oct 2026.
A statistical analyst in your AI chat: bring data and a question, get a citable, re-runnable report.
Uptime history
91 days of history · worst day 9%
91 days agonow
100.0%
Uptime 24h
183 of 183 checks
27
Tools
read from the server
656 ms
Response time
average over 24h
8
Stars
last commit 26 Oct 2026
What changed 66
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 24 August 2026. No other catalogue keeps this.
1 Nov
2 tools changed the parameters they ask for
path_answer, path_rerun
1 Nov
2 tool descriptions were rewritten
path_answer, path_rerun
25 Oct
4 tools changed the parameters they ask for
path_answer, path_estimate, path_reuse and 1 more
25 Oct
a tool description was rewritten
datasets_list
15 Oct
8 tools disappeared
answer_now, create_analysis, decide_path and 5 more
15 Oct
7 tools appeared
path_answer, path_bespoke, path_estimate and 4 more
15 Oct
a tool description was rewritten
about
10 Oct
a tool changed version
5 Oct
5 tool descriptions were rewritten
datasets_list, datasets_upload, discover_tools and 2 more
5 Oct
3 tools changed the parameters they ask for
build_status, report_cards, reports_view
and 32 more, back to 24 August 2026
MCP Analytics missed 2 checks this week
Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.
run in your terminal
claude mcp add analytics --transport http https://api.mcpanalytics.ai/auth0Settings → Connectors → Add custom connector, then paste this address
https://api.mcpanalytics.ai/auth0~/.codex/config.toml
[mcp_servers.analytics]
url = "https://api.mcpanalytics.ai/auth0".cursor/mcp.json
{
"mcpServers": {
"analytics": {
"url": "https://api.mcpanalytics.ai/auth0"
}
}
}.vscode/mcp.json
{
"servers": {
"analytics": {
"type": "http",
"url": "https://api.mcpanalytics.ai/auth0"
}
}
}This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.
This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.
Available tools 27
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
path
path_answer
A 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.
path_bespoke
Order 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.
path_estimate
A 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.
path_rerun
Run 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.
path_resolver
Which 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.
path_reuse
Hand back the report already delivered for this question on this data. Time: as path_resolver quotes.
path_tool_run
Run one or more tested library tools on this dataset, with charts and a written report. No custom build. Time: as path_resolver quotes.
datasets
datasets_list
List 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.
datasets_upload
Get 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.
reports
reports_list
Your report library: every analysis delivered, with status and links. Pass semantic_query to search report content in plain language.
reports_view
Get a shareable browser link for a report, viewable without authentication.
about
about
Platform documentation and info: how it works (Answer, Analytics, Custom Analytics), usage.
account
account_link
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.
adjust
adjust_estimate
Apply the user's layout wishes to the estimate's page through the layout agent; a new named arrangement, nothing overwritten, no number changes.
agent
agent_advisor
AI help desk: which analysis fits your question, interpreting results, fixing errors. Multi-turn.
ask
ask_library
Ask a question across all your delivered analyses: a synthesized answer with citations back to specific reports.
build
build_status
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.
discover
discover_tools
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 path_resolver.
objects
my_objects
List and search the objects you own across every question: the curated charts, tables and figures of each delivered package, grouped by objective.
package
package_status
Read an analytics package back: status, every run under it, the report link once delivered.
precedent
find_precedent
Before 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.
report
report_cards
Browse a delivered report's individual cards (charts, tables, insights) inline in chat.
review
review_estimate
The 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.
schedules
schedules
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'.
tool
check_tool_fit
Before 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.
tools
tools_schema
Get an analysis's parameter schema. ALWAYS call before path_tool_run.
warehouse
warehouse
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).
Tools removed
Tools this server used to expose. Anything built against them stopped working on the day they went.
answer_now
removed 15 Oct 2026
create_analysis
removed 15 Oct 2026
decide_path
removed 15 Oct 2026
modify_analysis
removed 15 Oct 2026
order_analytics_package
removed 15 Oct 2026
request_estimate
removed 15 Oct 2026
rerun_package
removed 15 Oct 2026
run_analysis
removed 15 Oct 2026
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://api.mcpanalytics.ai/auth0 | streamable-http | sign-in | 554 ms | 4 min ago |
| https://api.mcpanalytics.ai/mcp/api-key | streamable-http | answering | 582 ms | 2 min ago |
Alternatives to MCP Analytics
same job, measured the same wayPropick Integration MCP
by propick
Manage your real-estate stock on Propick (Dubai): bulk listing sync, lookups and run reports.
Maven
by metricmaven
Ask questions of your marketing data and build live reports.
Google Analytics
by codechap
MCP server for Google Analytics 4 — reports, realtime data, and admin
LLM Pulse
by llm-pulse
AI visibility analytics for brand mentions, citations, sentiment, and GEO reports
OVRSEA Shipments
by ovrsea-mcp
Query your OVRSEA freight: shipments, quotations, documents, tasks, and reporting analytics.
Ga4
by mharnett
Google Analytics 4 MCP: reports, realtime data, custom dimensions, data streams.
Invoices Invoicing
by theluckystrike
Invoices and invoicing from your AI chat: PDF generation, numbering, VAT, overdue reports.
Timesheets
by theluckystrike
Track billable time from your AI chat: timers, entries, reports, CSV export. All data stays local.
MCP Analytics — questions
Answers built from our own checks of this server.
What can MCP Analytics do?
It exposes 27 tools, read directly from the server on our last check. Among them: about, account_link, adjust_estimate, agent_advisor, ask_library, build_status and 21 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
What is MCP Analytics mostly used for?
Its tools cluster around path, reports and datasets. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is MCP Analytics working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 183 of 183 checks got a reply (100.0%), average response time 656 ms. The bar chart above shows every period we have measured.
Did MCP Analytics ever remove tools?
Yes. answer_now, create_analysis, decide_path, modify_analysis and 4 more are no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.
How do I connect MCP Analytics?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to MCP Analytics?
No API key is involved. MCP Analytics answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is MCP Analytics?
It answers our handshake in 656 ms on average, which is faster than 15% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is MCP Analytics open source?
The code is open source: it is published under the MIT licence, 8 stars on GitHub and 6 open issues. The licence covers the code in the repository, not the hosted service at api.mcpanalytics.ai, which runs on its operator's own terms.