Search Console MCP/Claude Code

Google Search Console in Claude Code

Claude Code is Anthropic's terminal-based coding agent, and it has first-class MCP support built into the CLI — no config file to hand-edit. Add the Search Console server with one command and Claude Code can read your real ranking data while it works on your site's content and templates.

Setup

  1. 1. Sign in to Google Search Console (once)

    Opens your browser, you approve read-only access, tokens save to your machine.

    npx search-console-mcp-server login
  2. 2. Add the server

    Run this from any directory — Claude Code stores it as a user-level MCP server.

    claude mcp add gsc -- npx -y search-console-mcp-server
  3. 3. Verify it's connected

    Inside a Claude Code session, run the built-in MCP status command.

    /mcp

Prompts to try first

  • Which of my pages lost the most clicks in the last 28 days?
  • Run /gsc:seo_checkup and give me the top 3 moves
  • Is /pricing indexed? If not, why not?

Troubleshooting

`/mcp` doesn't list `gsc`

You likely ran `claude mcp add` in one terminal but launched Claude Code from a different user account or shell. Re-run the add command from the same terminal you start Claude Code in.

Login opens a browser but nothing happens after you approve

Check that no firewall or VPN is blocking the local OAuth loopback (usually `localhost:8765` or similar). Disable the VPN and re-run `npx search-console-mcp-server login`.

Tool calls return "no properties found"

The Google account you signed in with isn't a verified user on any Search Console property. Add it as a user in Search Console settings, then sign in again.

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