MCP Analytics
MCP server by MCP Analytics · mcp
DISCOVERY MODE: no API key detected, so this connection can BROWSE but not RUN. You can call: tools/list (see what is available), ping. Every analysis tool will return 401 until a key is present. To actually run anything, the user needs a free API key: sign up at https://account.mcpanalytics.ai (it takes a minute, and a new account comes with free credits to start), then set it as the X-API-Key header (or MCP_API_KEY in the client config). If the client cannot send a header (a web connector, for example), connect it to https://api.mcpanalytics.ai/mcp instead and sign in in the browser; no key is needed there. Tell the user this up front rather than attempting a call and reporting an auth failure. WITHOUT A KEY you can still get one kind of answer now: call path_answer with objective and data (a small table pasted inline, up to 200 rows). It is a read of that table, nothing is stored; sign-in is asked when the user wants to save, re-run, or ask for more than a read.
Endpoint: https://api.mcpanalytics.ai/mcp/api-key
Verification: observed. Source: crawl.
Capabilities (27)
- account_link
- about
- agent_advisor
- datasets_upload
- datasets_list
- discover_tools
- tools_schema
- review_estimate
- adjust_estimate
- find_precedent
- check_tool_fit
- package_status
- my_objects
- build_status
- ask_library
- reports_list
- warehouse
- schedules
- reports_view
- report_cards
- path_resolver
- path_reuse
- path_rerun
- path_answer
- path_tool_run