seo

Google Search Console MCP Server

Google Search Console MCP for Claude: ask about queries, clicks, CTR and indexing in plain English. Free, open source, runs on your own Google credentials.

Pricing
free
GitHub stars
1,631
Last commit
2026-09-15
Page updated

Free and open source. The Search Console API and the Google Cloud project it needs don't cost anything.

View on GitHub
uvx mcp-search-console
Website

Google doesn't ship an official Search Console MCP. The community filled the gap, and the one most SEOs use is AminForou/mcp-gsc, with 1,600+ GitHub stars and releases as recent as September 2026. It installs with one uvx mcp-search-console command and gives Claude about 20 tools covering search analytics, URL inspection and sitemaps.

Pick it if you want Search Console data in Claude and you're fine creating a Google Cloud OAuth client once. OAuth uses your own Google account, so Claude sees exactly the properties you do. Use a service account instead if you're setting this up for a team or a scheduled job.

The prompt I run most: "show me queries in positions 8-20 with over 1,000 impressions and CTR under 2% in the last 28 days." Those are pages Google already likes. A better title tag or a content refresh often pushes them onto page one. Combine it with the Google Analytics MCP to see whether those clicks convert.

Write access is off by default. Adding or removing properties and deleting sitemaps only works if you set GSC_ALLOW_DESTRUCTIVE=true, and I'd leave it off. Search Console API limits still apply, and URL inspection is capped per property per day, so batch-inspecting a big site takes a few days.

What you can ask it

  • “Show me queries in positions 8-20 with more than 1,000 impressions and CTR under 2% over the last 28 days. Suggest a new title for each page.”
  • “Compare clicks and impressions for the last 28 days vs the previous 28 days and list the 10 pages that lost the most clicks.”
  • “Which search queries send traffic to /blog/email-marketing-guide, and are any of them a better fit for another page on my site?”
  • “Check these 10 URLs for indexing problems and tell me which ones Google hasn't indexed and why.”
  • “Find queries where two or more of my pages compete, and tell me which page should win.”
  • “List my sitemaps and flag any with errors or warnings.”

Features

  • `get_search_analytics` and `get_advanced_search_analytics`: queries and pages with clicks, impressions, CTR and position, filtered by country, device, query or page
  • `compare_search_periods`: period-over-period comparisons to spot drops and wins
  • `get_search_by_page_query`: the search terms sending traffic to one specific URL
  • `inspect_url_enhanced` and `batch_url_inspection`: index status, last crawl and rich-result issues for up to 10 URLs at once
  • `check_indexing_issues`: find indexing problems across a list of URLs
  • Sitemap tools: list sitemaps, see errors and warnings, submit new ones
  • Destructive actions (removing properties, deleting sitemaps) stay off unless you set `GSC_ALLOW_DESTRUCTIVE=true`

How to set up the Google Search Console MCP Server

Works with: Claude Desktop, Claude Code, Cursor, Codex CLI, Gemini CLI, Antigravity

1. In Google Cloud Console, create a project and enable the Search Console API. 2. Go to Credentials โ†’ Create Credentials โ†’ OAuth client ID, choose Desktop app and download the JSON (e.g. ~/Documents/client_secrets.json). For team or automated use, create a service account key instead and add its email as a user on your Search Console property. 3. Install uv (curl -LsSf https://astral.sh/uv/install.sh | sh) and find its full path with which uvx. 4. Claude Desktop: edit ~/Library/Application Support/Claude/claude_desktop_config.json:
{
  "mcpServers": {
    "gscServer": {
      "command": "/FULL/PATH/TO/uvx",
      "args": ["mcp-search-console"],
      "env": {
        "GSC_OAUTH_CLIENT_SECRETS_FILE": "/full/path/to/client_secrets.json"
      }
    }
  }
}
For a service account, swap the env for "GSC_CREDENTIALS_PATH": "/full/path/to/service_account.json" and "GSC_SKIP_OAUTH": "true". 5. Claude Code: the same server as a one-liner:
claude mcp add gscServer -e GSC_OAUTH_CLIENT_SECRETS_FILE=/full/path/to/client_secrets.json -- uvx mcp-search-console
6. Cursor: same JSON as step 4 in ~/.cursor/mcp.json, or install mcp-search-console from the Cursor Marketplace. 7. Fully quit and reopen the app. On first use a browser window opens for Google login. Test with "List my GSC properties".

Alternatives

ahonn/mcp-server-gsc

Node alternative that runs with `npx -y mcp-server-gsc` and a service account key. Handy if you'd rather not install Python tooling.

Suganthan's GSC MCP

OAuth-based server with extra audit tools plus `submit_url` and `submit_batch` for URL submission.

FAQ

Is there an official Google Search Console MCP?
No. Google has an official Google Analytics MCP and a Google Ads MCP, but Search Console only has community servers. AminForou/mcp-gsc is the most widely used.
How do I connect Google Search Console to Claude?
Enable the Search Console API in Google Cloud, create an OAuth desktop client, then add uvx mcp-search-console to Claude Desktop or Claude Code with GSC_OAUTH_CLIENT_SECRETS_FILE pointing at your client JSON.
Is the Google Search Console MCP safe?
It runs on your machine with your own Google credentials, so your data goes straight from Google to your client. Destructive actions are off unless you set GSC_ALLOW_DESTRUCTIVE=true.
Is it free?
Yes. The server is open source and the Search Console API is free to use.
Can it request indexing for my pages?
mcp-gsc focuses on URL inspection and sitemap submission. If you want to push individual URLs, Suganthan's GSC MCP has submit_url and submit_batch tools.

Added: 2026-09-22 ยท Last reviewed: 2026-09-22