Google Search Console in Cursor
Cursor is the AI-first code editor built on VS Code, and it supports MCP servers either through a project-level config file or the Settings UI. For a repo you're doing SEO work in, wiring GSC in at the project level means anyone who clones the repo gets the same server.
Setup
- 1. Sign in to Google Search Console (once)
npx search-console-mcp-server login - 2. Create the project config
Or skip the file: open Settings → MCP → Add new MCP server, and paste the same command/args.
Project root:.cursor/mcp.json - 3. Add the server block
{ "mcpServers": { "gsc": { "command": "npx", "args": ["-y", "search-console-mcp-server"] } } } - 4. Reload Cursor
Cmd/Ctrl+Shift+P → "Reload Window". The MCP panel in Settings should show gsc as connected.
Prompts to try first
- “Which new queries started showing up in the last 28 days?”
- “Do any queries have two of my pages competing? Which should win?”
- “Are my top 10 pages all indexed, with the canonicals I expect?”
Troubleshooting
Click it to expand the error. Almost always either `npx` isn't on Cursor's PATH (restart Cursor after installing Node) or the login step was never run.
Confirm it's at the project root, not inside .cursor/rules or a subfolder, and that it's valid JSON — Cursor silently ignores a file it can't parse.
That's expected if you used the project-level `.cursor/mcp.json` — it's scoped per repo. Copy the same block into each project, or add it globally via Settings → MCP instead.
Frequently asked
Yes. search-console-mcp-server is MIT licensed and free to run. There's no usage fee, no paid tier, and no account required beyond your own Google sign-in.
No. The server ships with a shared OAuth client so `npx search-console-mcp-server login` works out of the box. If you'd rather use your own Google Cloud project, you can — set SEARCH_CONSOLE_MCP_CLIENT_ID and SEARCH_CONSOLE_MCP_CLIENT_SECRET — but it's optional.
Only on your machine, in ~/.search-console-mcp/. Google mints the tokens directly to you during login — nothing passes through a third-party server, and there's no telemetry.
Whatever your Google account already has access to in Search Console: properties, search analytics (clicks, impressions, position, every dimension including Google Discover), URL inspection, and sitemaps. The scope is read-only — it cannot change anything in your Search Console account.
Yes, MIT licensed, on GitHub at sudomichael/search-console-mcp. Read the code, fork it, or self-host your own build.
Percy is an AI Head of SEO: he checks your Search Console on his own schedule, tells you exactly what to change, then re-checks the live page to confirm it landed. Free for 7 days when you connect your site, no card.