mcpbeat Sign in

Analytics MCP Server

by mcpanalytics Your server? Claim it
answering

Analytics is answering right now. Last checked 15 min ago. It exposes 26 tools. Last commit 7 Sep 2026.

The statistical analyst in your AI chat — validated, citable, re-runnable analysis of your data.

Uptime history 47 days of history · worst day 97%
47 days agonow
98.4%
Uptime 24h
179 of 182 checks
26
Tools
read from the server
699 ms
Response time
average over 24h
7
Stars
last commit 7 Sep 2026

What changed 29

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 24 August 2026. No other catalogue keeps this.

18 Sep a tool appeared find_precedent
13 Sep 2 tools appeared my_objects, rerun_package
11 Sep 6 tools appeared adjust_estimate, check_tool_fit, order_analytics_package and 3 more
10 Sep a tool changed the parameters it asks for run_analysis
4 Sep 4 tools changed the parameters they ask for create_analysis, datasets_upload, modify_analysis and 1 more
4 Sep a tool description was rewritten run_analysis
24 Aug 14 tool descriptions were rewritten about, account_link, agent_advisor and 11 more

Analytics does not always answer

Over the last week it answered 99.1% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

run in your terminal
claude mcp add analytics --transport http https://api.mcpanalytics.ai/auth0
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "analytics": {
      "url": "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
{
  "mcpServers": {
    "analytics": {
      "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 26

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

analysis
create_analysis
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 durable re-runnable module you own (30-45 min). Failed builds are never billed.
run_analysis
Run an analysis on your data. Returns a shareable interactive report URL with statistics you can cite, re-run and share, and the method named.
datasets
datasets_list
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.
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 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.
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, tiers, 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 create_analysis.
modify
modify_analysis
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.
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.
order
order_analytics_package
Order what the estimate promised after reviewing it: library tools that fit, a bespoke build, or both, computed on the whole dataset; one reviewed page delivered. Credits per tool run; failed runs never billed.
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.
request
request_estimate
START HERE for a new question: free, ~30 s. A rough answer over a sample plus the layout of the complete package, every place named with the question it will answer, and a page link. Then review_estimate with the user.
rerun
rerun_package
Run a delivered package again, on its own data or new data: the same tools, the same curated objects, the same layout, as a new package with its own link.
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 order_analytics_package.
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 run_analysis.
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).

Endpoints

URLTransportStateLatencyChecked
https://api.mcpanalytics.ai/auth0 streamable-http sign-in 622 ms 15 min ago
https://api.mcpanalytics.ai/mcp/api-key streamable-http answering 599 ms 15 min ago

Alternatives to Analytics

same job, measured the same way
Time Tracking
by theluckystrike

Track billable time from your AI chat: timers, entries, reports, CSV export. All data stays local.

local only
Timesheets
by theluckystrike

Track billable time from your AI chat: timers, entries, reports, CSV export. All data stays local.

local only
Time Tracker Timesheet Billable Hours
by theluckystrike

Track billable time from your AI chat: timers, entries, reports, CSV export. All data stays local.

14 tools answering
Dot - AI Data Analyst
by zurferr

Ask data questions in natural language. Get SQL, insights, and charts from your databases.

answering
Helm MCP
by kubedoll-heavy-industries

Give your AI assistant access to real Helm chart data. No more hallucinated values.yaml files.

5 tools answering
INSSIST
by inssist

Drive your own logged-in Instagram session via the INSSIST extension: read, publish, DMs, analytics.

510 installs/wk local only
iFood
by mcp-dir

Insights for your iFood store right in your AI assistant's chat. Generate charts of sales and payout

13 tools answering
Telemost MCP Server
by telemost

Telegram channel analytics and statistics for AI agents, pay-per-call in USDC via x402.

56 installs/wk 20 tools answering

Analytics — questions

Answers built from our own checks of this server.

What can Analytics do?
It exposes 26 tools, read directly from the server on our last check. Among them: about, account_link, adjust_estimate, agent_advisor, ask_library, build_status and 20 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 Analytics mostly used for?
Its tools cluster around reports, analysis 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 Analytics working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 179 of 182 checks got a reply (98.4%), average response time 699 ms. The bar chart above shows every period we have measured.
How do I connect Analytics?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path 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 Analytics?
No API key is involved. 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 Analytics?
It answers our handshake in 699 ms on average, which is faster than 17% 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 Analytics open source?
Yes — it is published under the MIT licence, written in JavaScript, 7 stars on GitHub and 3 open issues. The source link is on this page, so you can read exactly what it does with your data before you connect it.