Google Search Console

sarahpark/google-search-console-mcp

Connects Claude to Google Search Console via a service account. Exposes read-only access to search analytics (clicks, impressions, CTR, position) with filtering by query, page, country, device, and date range. Also includes URL inspection for indexing status and mobile usability checks, plus sitemap verification. Useful when you're debugging SEO issues, tracking keyword performance trends, or want Claude to spot high-impression, low-click opportunities without switching to the web console. Requires setting up a service account in Google Cloud and adding it as a restricted user to each Search Console property you want to query.

GitHub stars: 9
tools: 4
auth: Secret needed
transport: STDIO
env var: 1
last updated: Sep 19, 2026

View on GitHub

Tools

4 tools

Public tool metadata for what this MCP can expose to an agent.

list_sitesList all sites (properties) you have access to in Google Search Console.

List all sites (properties) you have access to in Google Search Console.

No parameter schema in public metadata yet.

search_analyticsQuery search analytics data — clicks, impressions, CTR, and position.

Query search analytics data — clicks, impressions, CTR, and position.

No parameter schema in public metadata yet.

inspect_urlCheck indexing status, crawl info, and mobile usability for a URL.

Check indexing status, crawl info, and mobile usability for a URL.

No parameter schema in public metadata yet.

list_sitemapsList all submitted sitemaps and their status for a site.

List all submitted sitemaps and their status for a site.

No parameter schema in public metadata yet.

Configuration

GOOGLE_APPLICATION_CREDENTIALSsecret

Optional path to a service account JSON key; omit to use local Application Default Credentials

Readme

Google Search Console MCP Server

A minimal MCP server for Google Search Console.

Give Codex, Claude Code, or Claude Desktop read-only access to your search analytics, URL indexing information, and sitemap status. Runs locally; cannot change your site or Search Console settings.

Once connected, ask your agent:

"Which queries had the most impressions but few clicks over the last 28 days?"
"Compare mobile vs desktop search performance this month."
"Check the indexing status of https://example.com/blog/my-post."

Setup · Tools · Limitations · Troubleshooting

Setup

You need Node.js and npm, an MCP client, and access to a Search Console property. To sign in as yourself, also install the Google Cloud CLI. Server startup and tool discovery were checked with Node.js 22.

1. Enable the Google API

Create or select a project in Google Cloud Console, then enable the Search Console API. Note the project ID for the next step.

2. Authenticate

View the full README on GitHub

Details

Repository: github.com/sarahpark/google-search-console-mcp
Categories: Search & Web Crawling, Monitoring & Observability
Package: @sarahpark/google-search-console-mcp
Transport: STDIO
Auth: Required
Registry: MCP registry, active

Related Search & Web Crawling MCP servers

View all

MCP Google Search Consolecrunchtools/mcp-google-search-consoleSecure MCP server for Google Search Console analytics, sitemaps, and URL inspection0stars

Brave Search Mcp Serverbrave/brave-search-mcp-serverBrave Search MCP Server: web results, images, videos, rich results, AI summaries, and more.1.6Kstars

Google Search Console MCP Server and API by Cotletcotlet-connect/google-search-console-mcpGoogle Search Console website search performance monitoring MCP server: request indexing.0stars

Firecrawl MCP Serverfirecrawl/firecrawl-mcp-serverFirecrawl, the context API for AI agents: search, scrape, interact with the web, plus paper search.7.8Kstars

Exa Searchpollinations/pollinationsSearch the live web and fetch clean content from source pages.5.3Kstars

ShadowCrawldevshero/shadowcrawlStealth scraping & search. Bypasses Cloudflare, DataDome & LinkedIn via Cyborg HITL approach.66stars