Google Search Console MCP

English | Русский

A1 Google Search Console MCP connects an AI app to Google Search Console. Investigate search performance, check whether a URL is indexed, inspect sitemaps and deliberately submit or remove a sitemap when needed.

It works with the properties your Google account can access. The important detail is that it uses the exact Search Console property value — a domain property and a URL-prefix property are different objects.

• 18 tools. Seven tools read properties, search data, sitemaps and index status; two add a property or submit a sitemap; three can remove data or call an arbitrary API method.
• Connects from the conversation. Say "connect Google Search Console": the server walks you through the OAuth client, catches Google's redirect on 127.0.0.1 with PKCE and keeps the tokens itself — no config files, no restart.
• Exact property IDs. https://example.com/, https://www.example.com/ and sc-domain:example.com are distinct. list_sites shows the value to use.
• Search data with context. Query clicks, impressions, CTR and position by date, page, query, country, device or search appearance.
• Indexing, not publishing. URL inspection explains Google’s current status; it does not force a page into the index.

Start with a read-only question:

Show the top 20 search queries for my property over the last 28 days, with clicks and CTR.

Connect the server · Explore use cases · Open technical documentation

See it work in a minute

You: Is https://example.com/pricing indexed? If not, why?

Assistant: Inspects the URL and shows the index verdict, coverage, crawl information and canonical URLs. Nothing changes.

You: Check my submitted sitemaps and prepare a resubmission for the one with errors.

Assistant: Shows the sitemap, its warnings and errors, then asks for confirmation before submitting it again.

You: Confirm.

Assistant: Resubmits the selected sitemap. It does not change page content or guarantee indexing.

Contents

• Quick start
• What you can ask it to do
• How Search Console properties work
• What can change
• Getting access
• Configuration
• Data, limits and background work
• Technical documentation
• Support

Quick start

You need Node.js 20+ and a Google account. Credentials are not required at install time — the server connects from the conversation.

1. Add the server to your AI app.
2. Say "connect Google Search Console": the assistant walks you through creating the OAuth client and approving access without editing config files.
3. Start with the read-only question above.

codex mcp add google-search-console \
  -- npx -y mcp-google-search-console@latest
codex mcp list

claude mcp add \
  --transport stdio --scope user google-search-console \
  -- npx -y mcp-google-search-console@latest
claude mcp list

{"mcpServers":{"google-search-console":{"command":"npx","args":["-y","mcp-google-search-console@latest"]}}}

{"mcpServers":{"google-search-console":{"type":"stdio","command":"npx","args":["-y","mcp-google-search-console@latest"]}}}

{"servers":{"google-search-console":{"type":"stdio","command":"npx","args":["-y","mcp-google-search-console@latest"]}}}

What you can ask it to do

Find search opportunities

• Which queries and pages brought the most clicks this month?
• Which pages lost clicks compared with the previous period?
• Show queries containing mcp where average position is below 10.

Check index status and sitemaps

• Is this URL indexed? Show coverage, crawl and canonical information.
• Which submitted sitemaps have errors or warnings?
• Resubmit this sitemap after showing its current status.

Manage properties carefully

• List the Search Console properties I can access.
• Add this exact property value; I will verify ownership separately.
• Remove this property from my account after confirmation.

How Search Console properties work

A URL-prefix property must include its protocol and trailing slash, for example https://example.com/. A domain property is written as sc-domain:example.com. A near-match causes 403 or 404, so use the exact value returned by list_sites.

add_site only registers a property. Verification remains in the Search Console UI or Site Verification API. Search data uses Pacific Time; end_date is inclusive and final analytics data typically lags by two to three days. data_state: "all" can include fresher, still-changing rows.

What can change

The AI client controls confirmation prompts. The server marks reads, writes and destructive calls so the client can distinguish an inspection from a real change.

Getting access

Google Search Console requires OAuth 2.0; an API key is not enough. There are two ways in, and the first one needs no configuration files.

Connect from the chat (recommended)

Say "connect Google Search Console" and the assistant runs the flow with you:

1. setup_instructions prints the checklist: create or select a Google Cloud project, enable Google Search Console API, configure the consent screen and create a Desktop app OAuth client.
2. Download that client's JSON ("Download JSON") and give the assistant its path — set_client stores it owner-only. The secret never goes through the conversation.
3. start_login returns a Google consent link. Open it on this machine and approve; the code comes back to a one-shot listener on 127.0.0.1 (PKCE), never through the chat.
4. finish_login exchanges the code and saves the tokens to ~/.config/mcp-google-search-console/credentials.json (mode 0600) and verifies them with a real Google Search Console API call — so an API that is still switched off is caught right there.

The tokens are re-read on every call, so the connection works immediately — no restart of the AI app. auth_status shows what is connected, logout revokes and deletes it.

Environment variables (CI, unattended installs)