AI Assistant Connection (MCP)
Connect Claude, Cursor or any MCP-compatible assistant directly to your Metricstab data. Ask questions in plain English and get answers from your own Search Console and Analytics history — read-only, and available on every plan.
What your assistant can read
- Every report — all 59 reports are reachable through one tool, using the same numbers the dashboard shows.
- Your recommendations — the prioritised insight queue, and the evidence behind any one of them.
- Your A/B tests — which are running and what they concluded.
- The documentation — these pages are exposed as resources, so the assistant knows what Metricstab means by "striking distance" rather than guessing.
Setting it up
- Go to Account → API keys and create a key. Copy it — it's shown once and stored only as a hash.
- Add Metricstab as a custom MCP server in your assistant:
{
"mcpServers": {
"metricstab": {
"url": "https://metricstab.com/mcp/",
"headers": { "Authorization": "Bearer YOUR_KEY_HERE" }
}
}
}
Then ask things like "which pages lost the most clicks this month, and what does Metricstab recommend?" or "show me my striking-distance keywords and explain what's holding them back."
Available tools
| Tool | What it does |
|---|---|
list_sites | Sites this key can read |
list_reports | Every report slug, so the assistant can discover what to ask for |
get_report | Any report, optionally for a date range |
list_recommendations | Open insights, ranked by estimated impact |
get_recommendation_evidence | The data behind one recommendation |
list_tests | SEO A/B tests and their status |
get_test_results | Outcome and statistical significance for one test |
What it deliberately cannot do
Every tool is read-only. There is no tool that starts a test, edits an annotation, changes a setting, or touches your website. An assistant connected to Metricstab can look at your data and nothing else.
That is a deliberate limit rather than an oversight. An API key lives inside software you don't fully control, so the blast radius of a leaked key is capped at reading your own analytics. Write access will only arrive alongside an approval-and-audit workflow.
Access and limits
- Available on trials and all paid plans — the same gate as report access.
- 120 requests per minute per key.
- Keys are revocable at any time from Account → API keys, and revoking takes effect immediately.
- Separate from your Google connection: revoking an MCP key does not disturb Search Console or Analytics ingestion.
- A key only reaches sites its owner can already see in Metricstab.
Related
- AI Readiness Score — whether your pages are structured so an answer engine can quote them.
- LLM Traffic Pages — which pages AI engines already send you traffic from.
- Insights & Scenarios Reference — what the recommendation engine looks for.