Google Search Console MCP server

How people find the site -- the half of the story analytics can't tell you.

Connect Google Search Console All connectors

Tools: 11
Read-only: 9
Write: 2; Off by default
Destructive: 1; Flagged distinctly

What it does

Google Search Console through an assistant

GA4 tells you what visitors did once they arrived. Search Console tells you how they got there: the actual search terms, which pages Google shows, where those pages rank, and whether Google has indexed them at all. An assistant can pull the queries driving clicks, compare pages by position, and answer "why isn't this page showing in Google" with Google's own index verdict rather than a guess. The tools push back on the API's biggest trap: Google deliberately hides rare queries, so the rows never sum to the real total, and every response says so rather than letting an assistant compute a confidently wrong percentage.

The search terms bringing clicks and impressions, with CTR and average position
Which pages earn search traffic, and where they rank
Complete, trustworthy totals over time -- daily, or hourly for recent days
Google's real index status for a URL: indexed or not, and why not
The canonical Google chose, versus the one the page declares
Sitemaps: what's registered, when Google last downloaded it, and its errors
Submit or remove a sitemap (opt-in)
A raw query escape hatch for breakdowns the presets don't cover

Ask your assistant

What people actually ask

Real questions, answered from live Google Search Console data.

“What are people searching to find us, and which pages do those searches land on?”

google_search_console_top_queriesgoogle_search_console_top_pages

“Why isn't this page showing up in Google?”

google_search_console_inspect_urlgoogle_search_console_list_sitemaps

“Has search traffic actually dropped this month, or does it just feel that way?”

google_search_console_performance_timeseriesgoogle_search_console_top_queries

Tool catalogue

11 Google Search Console tools

Grouped by what they touch. Every tool is individually toggleable — you expose only what you want.

All tools

11 tools9 read-only · 2 write

Showing 10 of 10 tools

google_search_console_delete_sitemap
Write
Destructive
Remove a sitemap from this property's Sitemaps report. This does NOT stop Google crawling or indexing the URLs it contained -- Google's own documentation is explicit about that -- and it is recoverable by submitting the same feedpath again. What is lost is the reporting history for that sitemap. Requires siteOwner or siteFullUser permission.
google_search_console_get_sitemap
Read-only
One sitemap's full record, including its per-content-type submitted and indexed counts. Prefer google_search_console_list_sitemaps unless the property has many sitemaps and you already know the exact feedpath.
google_search_console_inspect_url
Read-only
Google's current index status for one URL: whether it is indexed, the coverage state and why, when it was last crawled, which canonical Google chose versus the one the page declares, and any rich-result findings. This is the tool for "why isn't this page showing in Google?". Two things to understand: it reports Google's LAST KNOWN state rather than fetching the page now, so a change made minutes ago will not appear; and it is quota-critical -- Google allows only 2,000 inspections per day per property, so inspect specific URLs you have a reason to check rather than sweeping a site.
google_search_console_inspect_urls_batch
Read-only
Index status for up to 20 URLs in one call. This is a convenience wrapper around the single-URL inspection, not a bulk API -- Google has no batch endpoint, so it costs one inspection of the property's 2,000-per-day budget per URL. The cap is enforced, not advisory. Do NOT use this to sweep a whole site or sitemap: on any real site that exhausts the day's quota for the entire property, including the customer's own use of Search Console tooling, and cannot finish. Inspect a considered shortlist instead. Failures are returned per URL rather than aborting the batch.
google_search_console_list_sitemaps
Read-only
Sitemaps registered for a property, with when each was last submitted and last downloaded by Google, and its error and warning counts. Note that `submitted` in contents is how many URLs the sitemap declares, not how many Google indexed -- indexing status per URL comes from google_search_console_inspect_url. A sitemap Google has never downloaded shows isPending: true.
google_search_console_list_sites
Read-only
Every Search Console property this connection is authorized for, with the caller's permission level on each. Call this FIRST and copy the siteUrl verbatim -- every other tool needs it to match exactly, and there is no fuzzy matching or lookup by domain. A URL-prefix property ("https://example.com/", with the trailing slash) and a domain property ("sc-domain:example.com") are different properties covering different things, and guessing the wrong one returns a permission error rather than a helpful one. permissionLevel matters too: siteUnverifiedUser and siteRestrictedUser cannot submit or delete sitemaps, so check it before attempting a write.
google_search_console_performance_timeseries
Read-only
Clicks, impressions, CTR and average position over time for the whole property. Unlike the query and page tools, this grouping is COMPLETE -- Google returns all of it -- so this is the tool to use for real totals, for trend questions, and as the denominator whenever a percentage is wanted. Set granularity to hourly for the most recent period; hourly data only covers about the last 10 days and is unavailable further back. Data lags roughly 1-2 days, and the most recent rows may still change (see the freshness field).
google_search_console_search_analytics_query
Read-only
The raw Search Analytics call, for questions the preset tools cannot express -- multi-dimension breakdowns like query-by-country, or several filters at once. Prefer google_search_console_top_queries, _top_pages or _performance_timeseries unless you need this. Constraints Google enforces: there is NO OR operator (filter groups AND together, and so do filters within a group); grouping by HOUR requires granularity handled by the timeseries tool instead; and any grouping that includes QUERY or PAGE returns deliberately incomplete rows.
google_search_console_submit_sitemap
Write
Register a sitemap with Google for this property, or re-notify Google about an existing one after it changes. Requires siteOwner or siteFullUser permission -- check with google_search_console_list_sites first, since a restricted user's call just fails. Submitting does not make Google crawl immediately and does not guarantee indexing; it queues the sitemap for discovery. The sitemap must be hosted on the property itself, which this tool enforces.
google_search_console_top_pages
Read-only
Which pages of this property earn search clicks and impressions, with CTR and average position. The page here is the landing page Google showed, not the page a visitor ended on. Like top queries, these rows are deliberately incomplete and their sum is a lower bound rather than the property total.

+ 1 more all tools tool — see the full catalogue

Every tool name and description, machine-readable: /llms-full.txt

Access & safety

You decide what it can touch

The same model applies to every connector, and it defaults closed.

Authorize once

Connect Google Search Console through its own consent screen. Credentials are encrypted with AES-256-GCM and never returned by any API response or tool call.

Writes off by default

A new connection switches on a read-oriented default set only. Every write tool must be enabled deliberately before any client can call it.

Roles enforced server-side

READ, WRITE and ADMIN gate tool invocation on the server, not just in the UI. A READ member's token is refused any write tool.

Setup

Connect Google Search Console in minutes

No infrastructure to run. Copy one URL and one token into your client.

1Create a free workspace and connect Google Search Console.
2Choose which tools to expose — writes stay off until you enable them.
3Copy your MCP endpoint URL and bearer token.
4Paste them into Claude, Cursor, or any MCP client.

claude_desktop_config.json

{
  "mcpServers": {
    "serve-mcp": {
      "url": "https://servemcp.com/api/mcp/your-workspace",
      "transport": "http",
      "headers": {
        "Authorization": "Bearer smcp_..."
      }
    }
  }
}