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.
section
ai.mcpanalytics由 mcpanalytics.ai 发布官方发布者v1.0.8更新于 Oct 24, 2026
A statistical analyst in your AI chat: bring data and a question, get a citable, re-runnable report.
远程 MCP 服务器,充当统计分析助手:上传数据、提出业务问题,获得可引用、可复跑的报告。
Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。
把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。
阅读 https://sourceweft.com/mcp/ai.mcpanalytics%2Fanalytics/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。把它添加到你客户端的 mcpServers 配置中。
{
"mcpServers": {
"analytics": {
"type": "http",
"url": "https://api.mcpanalytics.ai/mcp/api-key",
"headers": {
"X-API-Key": "<YOUR_API_KEY>"
}
}
}
}A statistical analyst in your AI chat. Bring a dataset and a question, get back a citable, re-runnable report with its method named.
MCP Analytics is a Model Context Protocol server that answers business and statistical questions about your data, as deep as each question needs:
Intelligent routing picks the depth: you describe the question, and the server says which path answers it and why. Analytics is repeatable: same data, same numbers. Every report names its method and the code that ran it, and runs again on new data.
It is for business and statistical questions about data, not a general-purpose assistant.
Website: mcpanalytics.ai · Free tools you can try in the browser: mcpanalytics.ai/free
Endpoint: https://api.mcpanalytics.ai/mcp/api-key (Streamable HTTP, JSON-RPC)
Authentication: an API key in the X-API-Key header. Create an account at mcpanalytics.ai and copy your key from your account settings.
Claude Code:
Browse before you sign up. Without a key the server answers in discovery mode: you can connect and list the tools, but not run anything.
Ask your AI assistant a question about your data, for example:
The first call is the resolver: it reads your question and your data, executes nothing and charges nothing, and names the path that answers it (an answer, a library analysis, or a custom build) with the reason. Then it runs that path.
Your uploaded data is used only to answer your questions. See the privacy policy for what we keep and for how long. Security issues: see SECURITY.md.
See LICENSE.
来源:README.md,提交 33a3580
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.
sectionPlatform documentation and info: how it works (Answer, Analytics, Custom Analytics), usage.
topic必填AI help desk: which analysis fits your question, interpreting results, fixing errors. Multi-turn.
message必填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.
dataexpires_inreplace_refList and search your uploaded datasets, with fuzzy matching on name, description, and tags. Returns each dataset's uuid:// reference for use in path_resolver and path_tool_run.
limitsearchBrowse 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.
queryGet an analysis's parameter schema. ALWAYS call before path_tool_run.
tool_name必填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.
estimate_id必填Apply the user's layout wishes to the estimate's page through the layout agent; a new named arrangement, nothing overwritten, no number changes.
estimate_id必填instructions必填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.
kobjective必填dataset_refBefore 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.
objectivetool_name必填dataset_ref必填Read an analytics package back: status, every run under it, the report link once delivered.
package_id必填List and search the objects you own across every question: the curated charts, tables and figures of each delivered package, grouped by objective.
limitqueryinclude_droppedCheck 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.
pipeline_idtrack_tokenAsk a question across all your delivered analyses: a synthesized answer with citations back to specific reports.
question必填Your report library: every analysis delivered, with status and links. Pass semantic_query to search report content in plain language.
limitsemantic_queryQuery 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).
queryaction必填paramsquestionStanding 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'.
action必填cadencetool_namedataset_refschedule_idcolumn_mappingGet a shareable browser link for a report, viewable without authentication.
processing_id必填Browse a delivered report's individual cards (charts, tables, insights) inline in chat.
processing_id必填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.
doormetaobjective必填dataset_refHand back the report already delivered for this question on this data. Time: as path_resolver quotes.
objective必填dataset_ref必填resolution_idRun a delivered analysis again, on its own dataset or a new one: the same tools and mappings, no rebuild. Time: as path_resolver quotes.
package_id必填dataset_refresolution_idA 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.
objective必填dataset_ref必填resolution_idRun one or more tested library tools on this dataset, with charts and a written report. No custom build. Time: as path_resolver quotes.
objective必填tool_names必填dataset_ref必填estimate_idresolution_idcolumn_mappingidempotency_keymodule_parametersA 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.
objective必填tool_namesdataset_ref必填completenessresolution_idlayout_objectiveOrder 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.
tool_namesestimate_id必填resolution_ididempotency_key必填layout_objective已满足适用检查项的 100%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
{ "mcpServers": { "mcpanalytics": { "url": "https://api.mcpanalytics.ai/mcp/api-key", "headers": { "X-API-Key": "mcp_your_key_here" } } }}claude mcp add --transport http mcpanalytics https://api.mcpanalytics.ai/mcp/api-key --header "X-API-Key: mcp_your_key_here"curl -X POST https://api.mcpanalytics.ai/mcp/api-key \ -H 'Content-Type: application/json' \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'