Google Search Console in Windsurf

Windsurf (by Codeium) is an AI-native IDE with MCP support through a global config file shared across all your projects. One setup covers every Windsurf window you open afterward.

Setup

  1. 1. Sign in to Google Search Console (once)
    npx search-console-mcp-server login
  2. 2. Open the Windsurf MCP config

    You can also get here from the UI: Windsurf Settings → Cascade → MCP Servers → "View raw config".

    macOS / Linux: ~/.codeium/windsurf/mcp_config.json
    Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json
  3. 3. Add the server block, then refresh

    In the MCP Servers panel, click the refresh icon next to the list — Windsurf doesn't always pick up file changes on its own.

    { "mcpServers": { "gsc": { "command": "npx", "args": ["-y", "search-console-mcp-server"] } } }

Prompts to try first

  • Which of my pages lost the most clicks this month vs last?
  • Is /pricing indexed? If not, why not?
  • Show queries at position 8–15 with real impressions

Troubleshooting

gsc doesn't show up in the MCP Servers panel

Hit refresh in the panel, or fully quit and reopen Windsurf. The config file is only read on that refresh/restart, not live.

"command not found: npx"

Windsurf runs the server with your system PATH, not a shell profile. If you installed Node via nvm, launch Windsurf from a terminal where `npx` already works, or use the full path to npx in the config.

Config file doesn't exist yet

Create the `.codeium/windsurf/` folder and the file yourself with the JSON above — Windsurf creates it lazily on first MCP use in some versions.

Frequently asked

Is it free?

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.

Do I need a Google Cloud project?

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.

Where are my tokens stored?

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.

What data can it read?

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.

Is it open source?

Yes, MIT licensed, on GitHub at sudomichael/search-console-mcp. Read the code, fork it, or self-host your own build.

The MCP answers when you ask. Percy watches every week and emails you what to change.

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.

Meet Percy