SEO Perception MCP
Bring Search Console keywords and SEO possibilities into your MCP client so you can rewrite and optimize pages from real performance data—not guesses. SEO Perception MCP is a hosted SEO MCP server for Cursor, Claude, and other Model Context Protocol clients.
“Use SEO Perception to find the biggest losing keywords on
/page1/and suggest concrete content changes to recover them.”
Works with Cursor, Claude, and other MCP clients. Tools read stored weekly Search Console facts and crawl evidence that we have already collected. MCP never calls Google Search Console, URL Inspection, or another live Google API.
For the live tool catalog, Cursor configuration, and other MCP client setup, see
SEO Perception MCP. Create and revoke MCP personal access tokens in
Account → MCP. The endpoint is
/mcp.
Related reading: What is an SEO MCP server?, Live GSC MCP vs stored evidence, 7 SEO workflows from Cursor with MCP.
Prerequisites
- Paid plan — Starter, Pro, Business, or Enterprise. Free accounts cannot create MCP personal access tokens or call
POST /mcp. - Up to 5 active MCP personal access tokens per user; each expires after 90 days and can be revoked at any time.
-
Rate limits protect the service:
POST /mcpallows 60 requests per minute per IP before authentication and 120 per minute per authenticated token. Individual tool calls allow 30 per minute for each user, token, and site combination. - Creating MCP personal access tokens allows 5 attempts per user per hour.
Each token secret is shown once, then stored hashed at rest; we retain only a short display prefix. Prefer an environment variable such as SEOPERCEPTION_MCP_TOKEN over a committed config file. Create, copy, and revoke MCP personal access tokens under Account → MCP.
SEOPERCEPTION_MCP_TOKEN from its 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.
Account → MCP shows when each token was last used. That timestamp is written at most once every 15 minutes, so repeated tool calls may not update it immediately.
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:
- “Use SEO Perception to find the biggest losing keywords on
/page1/and suggest concrete content changes to recover them.” - “Show the highest-priority open SEO opportunities and explain the evidence.”
- “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 MCP personal access token under Account → MCP and update the environment variable.
- 403 paid_plan_required — upgrade to a paid plan, then create a token.
- 429 — the HTTP endpoint allows 60 requests per minute per IP before authentication and 120 per minute per authenticated token; tool calls allow 30 per minute for each user, token, and site combination. Wait for the retry time in the response.
- 406 — your MCP client must send
Accept: application/json, text/event-stream. Cursor does this automatically; include both values in custom clients and curl tests. - Empty lists usually mean no stored data yet — confirm Search Console collection and crawl finished.