Skip to main content
MCP server CX Codex

Google Search Console MCP — Claude Code MCP server: what it does

A read-only MCP server for Google Search Console: properties, Search Analytics, sitemaps, URL inspection. Useful when your agent should read search data inside the project.

Install into Claude Code · Platform CLI All methods and platforms ↓
claude mcp add --env GOOGLE_APPLICATION_CREDENTIALS=<GOOGLE_APPLICATION_CREDENTIALS> --env GSC_LOG_LEVEL=<GSC_LOG_LEVEL> --transport stdio google-search-console-mcp -- uvx scalably-gsc-mcp
Open on GitHub

What Google Search Console MCP does

Five tools ship with it. gsc_list_sites shows the properties your service account can read. gsc_query_search_analytics pulls Search Analytics with filters and hourly breakdowns. gsc_list_sitemaps fetches sitemaps, gsc_inspect_url reports the index status of one address, and gsc_batch_inspect_urls walks through a list while throttling requests on the client side.

Every reply is JSON carrying status, operation, summary, target, result, proof, warnings and recovery. A partial status with proof.nextStartRow tells you to resume from that row. That is how the 25,000-row ceiling on a single Search Analytics call gets handled: the server keeps paging up to max_rows on its own.

Setup has to happen in Google Cloud first. Turn on the Search Console API there, create a service account, download its JSON key. Then add the account's email as a user on every property you plan to query, with full or restricted permission, both read fine. The key path goes into GOOGLE_APPLICATION_CREDENTIALS; without it the server returns nothing. URL inspection carries Google's own caps of 600 requests per minute and 2,000 a day per property, and daily usage is counted only within a single batch call, so track it yourself.

What it helps with

  • check which search queries send traffic to a site
  • pull Search Analytics data past the 25,000-row cap
  • confirm whether a page is indexed
  • inspect many URLs without hitting the rate limit
  • list sitemaps for a property

Example prompts for the agent

  • Query last week's search analytics for this property, filtered by page
  • Batch-inspect the URLs in urls.txt

How to install Google Search Console MCP

Platform CLI

claude mcp add --env GOOGLE_APPLICATION_CREDENTIALS=<GOOGLE_APPLICATION_CREDENTIALS> --env GSC_LOG_LEVEL=<GSC_LOG_LEVEL> --transport stdio google-search-console-mcp -- uvx scalably-gsc-mcp

Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from scalably-gsc-mcp <command>

Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more

Questions about Google Search Console MCP

How do I install Google Search Console MCP in Claude Code?

Run claude mcp add gsc-mcp -e GOOGLE_APPLICATION_CREDENTIALS=<GOOGLE_APPLICATION_CREDENTIALS> -- uvx scalably-gsc-mcp, replacing the placeholder with the path to your service-account JSON key.

What does Google Search Console MCP do?

It gives an agent read access to Search Console: properties, Search Analytics, sitemaps, inspection of one URL or a batch. Nothing is written back to the account.

What do I need before it works?

Enable the Search Console API in a Google Cloud project, create a service account and download its JSON key. Share each property with that account's email as a user.

Similar MCP servers

Everything for SEO and GEO →

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor