The Google Search Console MCP connects Claude to your own search data: clicks, impressions, CTR and positions per page and query, period comparisons, URL inspection and sitemaps. It's a community server by Amin Foroutan, MIT-licensed, and the most popular way to put Search Console in a chat. It's free, and it's where every SEO question should start.
Ask which pages dropped and Claude compares the periods, pulls the queries behind each drop and names a cause. Pair it with Google Analytics to see whether lost clicks also cost you sign-ups, or with Ahrefs to find competitor keywords you already rank 8 to 20 for.
A real run
We asked which paralect.com pages lost the most clicks in the last 28 days. Claude compared both periods, pulled the queries behind each drop and found a different cause for each page: one lost rankings, one lost clicks while ranking higher, one stopped matching what people search for.
Watch out
- Search Console data lags 2 to 3 days. Leave the last two days out of comparisons.
- Results are capped at 500 rows per request, so ask for top pages or queries, not everything.
- Tools that add or delete sites and sitemaps are off by default. Keep them off unless you need them (
GSC_ALLOW_DESTRUCTIVE).
Install
Create a Desktop OAuth client in Google Cloud, enable the Search Console API, download the client secrets JSON, then run:
Terminal
Loading editor...
claude mcp add gsc -e GSC_OAUTH_CLIENT_SECRETS_FILE=/path/client_secrets.json -- uvx mcp-search-console
A browser window asks you to sign in with Google on first use, then the token is cached. For team or automated use, a service account works too (
GSC_CREDENTIALS_PATH). In Cursor, search for mcp-search-console in the Marketplace. It runs locally, so it works in Claude Code and Claude Desktop but not on claude.ai.