What it does
The server gives one MCP interface to Google Search Console data for several sites or clients, without restarting the server. Its tools cover account inspection and default switching, property listing with permissions, search-performance queries (including period comparison and per-page breakdowns), URL inspection, batch inspection, indexing-issue checks, and sitemap listing, retrieval, submission and deletion. Search Console calls are retried on transient API failures.
It suits an operator who manages Search Console data across multiple properties or client accounts and wants them reachable from a single MCP client. The publisher's documentation covers connecting it to Claude, Codex or Cursor.
Running it involves installing the Python package, creating an accounts configuration file (an example file is included), and registering the server in the MCP client. Authentication is set per account, using either OAuth or a service account. Sitemap submission and deletion are gated behind a destructive flag described in the setup documentation.
Limitations and requirements
Beta release. Each account needs authentication configured in the accounts file, using OAuth or a service account. Sitemap submit and delete tools are gated behind a destructive flag documented in the setup guide.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
MCP Search Console
Multi-account Google Search Console MCP: analytics, URL inspection, sitemaps across named accounts.
v0.1.3As shown on registry.modelcontextprotocol.io when we last read it