Labsco
MCP SERVER

MCP Search Console

by apexradius

Google Search Console across several sites or clients from one server — switch accounts without restarting, with sitemap writes behind a flag.

SEO, Web & Product Analytics
Summary
Multi-account without a restart, and the destructive tools stay off.

Agencies end up running one server per client and reconnecting to switch. Here the account is resolved per call from a config file, so the workflow stays continuous — which matters more than it sounds when the task is comparing two clients' data in one sitting. The safety choice is the right one too: submitting or deleting a sitemap is a real change to how Google crawls a site, and it takes an explicit environment flag rather than a confirmation the model can talk itself past.

What it is

A Search Console MCP server built for operators who manage more than one property. Accounts are declared in a config file and resolved per call, so one running server addresses many Search Console accounts and switching between them does not mean restarting anything.

What you get
  • Account routing as first-class behaviour: inspect the configured accounts, change the default, and refresh authentication in place — `list_accounts`, `set_default_account`, `reauthenticate`
  • Property inventory: which properties an account can reach and what permissions it has on them — `list_properties`, `get_site_details`
  • Search analytics five ways — a straight query, a performance overview, a period comparison, an advanced query and a per-page breakdown — `get_search_analytics`, `get_performance_overview`, `compare_periods`, `get_advanced_search_analytics`, `get_search_by_page`
  • Indexing inspection, singly and in batch, plus an indexing-issues check — `inspect_url`, `batch_inspect_urls`, `check_indexing_issues`
  • Sitemap management: list, read, submit and delete — with the two write operations held behind a destructive flag — `list_sitemaps`, `get_sitemap`, `submit_sitemap`, `delete_sitemap`
  • Transient Search Console API failures retried with backoff rather than surfacing as errors you have to re-ask about
Requirements

Google Search Console access per account, authenticated either through the OAuth desktop flow or a service account. Configuration is file-driven: copy `accounts.example.json` to `~/.config/mcp-search-console/accounts.json` and point `GSC_ACCOUNTS_CONFIG` at it. `GSC_ALLOW_DESTRUCTIVE` must be set to `true` before sitemap submit and delete will run at all. Install with `python -m pip install mcp-search-console-multi` or launch with `uvx mcp-search-console-multi`; the package is `mcp-search-console-multi` (0.1.3 in pyproject) over stdio, with `MCP_TRANSPORT` switchable to SSE for remote hosting. The README describes this as a beta package.

Setup effort

Build from source — clone the repository and build it, then point your client at the binary