MCP for Cursor
SEO Perception exposes a remote Model Context Protocol (MCP) server so Cursor and other Streamable HTTP clients can read your stored Search Console and crawl evidence. Tools answer from data we already collected. They never call Google Search Console, URL Inspection, or other live Google APIs.
Product overview and Cursor config:
MCP integration. Create and revoke tokens in
Account → MCP. Machine endpoint (POST only):
/mcp.
Prerequisites
- Paid plan — Starter, Pro, Business, or Enterprise. Free accounts cannot create tokens or call
POST /mcp. - Up to 5 active personal tokens per user; each expires after 90 days (revoke anytime).
- Tool calls are rate-limited to about 30 requests per minute per token.
Secrets are hashed at rest. We store only a short display prefix. Prefer an environment variable such as SEOPERCEPTION_MCP_TOKEN over pasting the secret into committed config files. Create, copy, and revoke tokens under Account → MCP.
SEOPERCEPTION_MCP_TOKEN from your environment.
Privacy promise
- MCP reads stored weekly Search Console facts and crawl/issue evidence only.
- MCP does not refresh Google data, submit sitemaps, recrawl pages, or mutate issues.
- Your MCP client may still send tool results to a model provider. Treat returned evidence as sensitive site analytics.
Practical use
Available tools cover site listing, overview, query search, opportunities, cannibalization, content gaps, internal-link ideas, and page diagnostics. Planned and excluded tools are labeled on the MCP page—trust that catalog over any static list here.
tools/list. Planned tools are roadmap-only; live Google calls and mutations are excluded.
Example prompts that work well once a token is connected:
- “List my SEO Perception sites and tell me which data is freshest.”
- “Find keyword cannibalization and recommend which page should be preferred.”
- “Find non-branded queries in positions 5–20 that are missing from their landing page.”
- “Diagnose this page using its crawl state, titles, indexability, queries, and opportunities.”
Pass siteId as the website’s public UUID from SEO Perception. Responses include provenance that marks stored-data reads and confirms no live Google request was made.
Troubleshooting
- 401 — missing, invalid, or expired token. Create a new token under Account → MCP and update the env var.
- 403 paid_plan_required — upgrade to a paid plan, then create a token.
- 429 — about 30 tool calls per minute; wait for the retry time in the response.
- Empty lists usually mean no stored data yet — confirm Search Console collection and crawl finished.