Google Search Console

Official registry Search and web

Google Search Console MCP server: 20 read tools, no write tools.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package @getmcpads/google-search-console-mcp-server
Claude Code
claude mcp add google-search-console -e 'GSC_CLIENT_ID=<GSC_CLIENT_ID>' -e 'GSC_CLIENT_SECRET=<your gsc_client_secret>' -e 'GSC_REFRESH_TOKEN=<your gsc_refresh_token>' -e 'GSC_ACCESS_TOKEN=<your gsc_access_token>' -e 'GSC_SITE_URL=<GSC_SITE_URL>' -e 'GSC_SITE_URLS=<GSC_SITE_URLS>' -- npx -y @getmcpads/google-search-console-mcp-server@2.1.1
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "google-search-console": {
            "command": "npx",
            "args": [
                "-y",
                "@getmcpads/google-search-console-mcp-server@2.1.1"
            ],
            "env": {
                "GSC_CLIENT_ID": "<GSC_CLIENT_ID>",
                "GSC_CLIENT_SECRET": "<your gsc_client_secret>",
                "GSC_REFRESH_TOKEN": "<your gsc_refresh_token>",
                "GSC_ACCESS_TOKEN": "<your gsc_access_token>",
                "GSC_SITE_URL": "<GSC_SITE_URL>",
                "GSC_SITE_URLS": "<GSC_SITE_URLS>"
            }
        }
    }
}

Environment variables

  • GSC_CLIENT_ID OAuth client ID.
  • GSC_CLIENT_SECRET secret OAuth client secret.
  • GSC_REFRESH_TOKEN secret OAuth refresh token, webmasters.readonly scope.
  • GSC_ACCESS_TOKEN secret Short-lived access token, alternative to the three values above.
  • GSC_SITE_URL Default property, https://example.com/ or sc-domain:example.com.
  • GSC_SITE_URLS Comma-separated Search Console properties every tool is limited to. Optional in 2.x, required in 3.0.0.

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Google Search Console MCP server
  2. What's new
  3. Install this release
  4. What you get
  5. One thing to know before you trust a number
  6. Read-only, and why it stays that way
  7. Getting credentials
  8. Setup
  9. Tools
  10. Security
  11. Looking for a managed, multi-platform version?
  12. Contributing
  13. Licence
  14. MCP contracts and desktop bundle
  15. More from getmcpads

Google Search Console MCP server

Bring your search performance into the conversation.

Investigate queries, pages, indexing and sitemaps through a read-only MCP server.

Watch the film · What's new · Install · Tool reference · Try hosted getmcpads

Play the 45-second film

The film shows hosted getmcpads with sample data. Its MCP Apps, from creative galleries and alerts to Google Sheets exports and bulk launches, belong to the hosted product. This repository provides the standalone native API tools.

20 read tools · Read-only by design.

Run locally with your own platform credentials and a client that supports stdio MCP, such as Claude Desktop, Claude Code or Cursor. Your requests go directly to the platform. For managed connections, including supported ChatGPT setups, use the hosted option.

What's new

v2.1.0: Site allowlist and revoked-token handling · October 23, 2026

  • Add the optional GSC_SITE_URLS allowlist, checked before every request, including URL Inspection where the property travels in the body. gsc_list_sites and gsc_health_check list only the allowed properties. Unset, the server prints a recommendation on stderr. It becomes required in 3.0.0.
  • Refuse a GSC_SITE_URL outside GSC_SITE_URLS at startup, when both are set.
  • Port the gateway's handling of a refused refresh token (invalid_grant, admin_policy_enforced): one re-authorization message naming GSC_REFRESH_TOKEN, and no further token requests until restart. A static GSC_ACCESS_TOKEN keeps working as before.
  • Remove the unused authorization-code helpers. The server never ran an OAuth browser flow, and accounts.google.com is no longer in the source.
  • Give the token request a deadline and bound every response body. Pagination limits are unchanged.
  • Require Node.js ^22.23.4 || ^24.22.1 || >=26.12.1, warn on stderr at startup and in npm run doctor on older releases, and test Node 22, 24 and 26 in CI.
  • Update @modelcontextprotocol/sdk to 1.32.1 and regenerate the lockfile.
  • Publish from version tags with release.yml, which replaces publish-mcp.yml. Add Dependabot.
  • No tool is added or removed: 20 read tools, no write tools.

Earlier releases

VersionDateHighlights
2.0.1September 23, 2026Public repository restored
2.0.0September 20, 2026Gateway sync and security fixes
1.1.0September 13, 2026Platform capability sync and quality contracts
1.0.2August 30, 2026Announce the package version over MCP.
1.0.1August 30, 2026Add server.json and mcpName for the official MCP Registry, under com.getmcpads/google-search-console.
1.0.0August 29, 2026First open-source release

Full changelog · All releases

Source synchronization: SOURCE_SYNC.md.

Upgrade notes

Requires Node.js 22.23.4, 24.22.1 or 26.12.1, or a newer release of one of these lines. Older releases lack the October 2026 security fixes, and the server prints a warning on stderr when it starts on one. CI covers Node 22, 24 and 26.

This release makes no breaking change to the configuration. One change is announced for 3.0.0: GSC_SITE_URLS is optional in 2.x and becomes required. When set, every tool is limited to the listed properties, and GSC_SITE_URL must be one of them. When unset, the server starts as before and prints one line on stderr recommending it. The 20 tools, their schemas and the bounded reporting limits are unchanged.

Install this release

This is a GitHub source release. npm and MCP Registry versions are published separately. The commands below select this exact version; unpinned npx examples later in this document select the version currently available on npm.

git clone --branch v2.1.0 --depth 1 https://github.com/get-mcp-ads/google-search-console-mcp-server.git
cd google-search-console-mcp-server
npm ci
npm run build

Configure your MCP client to run node with the absolute path to dist/cli.js and the platform credentials documented below.

Prefer a managed connection? Use Google Search Console with hosted getmcpads. Connect your account, select the data your assistant may access and use the hosted MCP connection. See the site for current features and plans.

What you get

20 read toolsSearch Analytics, sites, sitemaps, URL Inspection, and analyses built on top of them
SEO analyses, not just an API wrapperCannibalisation detection, query clustering, wins and losses between periods, indexation watchlists, large-site sampling plans
7 resourcesLive catalogues the model can read: metrics, dimensions, filters, compatibility rules, 8 workflow recipes, read-only playbooks
Quota guardrailsEvery URL Inspection call is capped at 10 URLs, so one exploratory question cannot burn a day of quota
No writes at allNot a flag, a property of the code. See below
What it does beyond fetching rows

Search Console answers questions about rows. Most real questions are about change: which queries did we lose, which pages compete for the same term, is indexing drifting.

These tools do that work rather than leaving it to the model:

ToolQuestion it answers
gsc_detect_cannibalizationWhich pages compete for the same query
gsc_find_losses_gainsWhat we won and lost between two periods
gsc_cluster_queriesWhich queries belong to the same intent
gsc_compare_search_typesHow web, image, video and news differ
gsc_analyze_search_appearance_trendsHow rich results evolve
gsc_indexation_watchlistWhich URLs changed indexing verdict
gsc_plan_large_site_samplingWhich URLs to inspect, when you cannot inspect them all

One thing to know before you trust a number

Search Console returns a top N, not a site total.

When you query with a dimension such as query or page, the API returns the highest ranked rows up to your row limit, ordered by clicks. Summing the clicks of those rows does not give you the site total: the long tail is missing, and on a large site it can be most of the traffic.

To get a real total, query without dimensions. To compare periods, compare like with like: same dimensions, same row limit, same search type.

gsc_query_search_analytics reports what it actually returned, and gsc_validate_query checks a combination before it runs. But the arithmetic mistake is yours to avoid, and it is the most common one in Search Console analysis.

Two other limits worth carrying in your head:

  • Roughly 16 months of history. Anything older is gone, not slow.
  • Data settles over about three days. gsc_get_data_freshness tells you what is final.

Read-only, and why it stays that way

There are no write tools, and no environment variable that adds any. The Search Console API can submit and delete sitemaps, add and remove properties, and request indexing. This server exposes none of that.

The scope it asks for reflects that: webmasters.readonly, not webmasters. Even if the model tried, the token cannot write.

Our ad platform servers, where writes make sense, do have them, guarded by a mandatory preview: Meta Ads · Google Ads · TikTok Ads

The hosted version at getmcpads.com keeps the same rule: Search Console stays read-only there too.


Getting credentials

Three values, obtained once.

1. OAuth client

In a Google Cloud project, enable the Google Search Console API, then create an OAuth client under APIs & Services → Credentials. Choose Desktop app for local use. Note the client ID and client secret.

2. Refresh token

Run the OAuth consent flow once, signed in as a Google account that owns or can read your properties, and keep the refresh token. Request webmasters.readonly and nothing more.

📖 Google OAuth for installed apps

The refresh token does not expire. Use an OAuth client dedicated to this server so you can revoke it on its own.

For a quick trial you can set GSC_ACCESS_TOKEN to a short-lived token instead, but it expires within the hour and is useless for daily work.

If setting up an OAuth client is more than you want to do for one property, getmcpads.com handles the consent flow for you and gives you the same tools behind a hosted endpoint.

3. Site URL, optional

Set GSC_SITE_URL to avoid passing it on every call. Both property forms work:

Property typeValue
URL-prefixhttps://example.com/ (the trailing slash matters)
Domainsc-domain:example.com

List what you can reach with gsc_list_sites, and run gsc_health_check as your first call. It verifies the credentials without printing any secret.


Setup

Claude Desktop

~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "search-console": {
      "command": "npx",
      "args": ["-y", "@getmcpads/google-search-console-mcp-server"],
      "env": {
        "GSC_CLIENT_ID": "your-client-id",
        "GSC_CLIENT_SECRET": "your-client-secret",
        "GSC_REFRESH_TOKEN": "your-refresh-token",
        "GSC_SITE_URLS": "sc-domain:example.com"
      }
    }
  }
}

Restart Claude Desktop. Ask it: "which queries did we lose last month?".

Claude Code
claude mcp add search-console --env GSC_CLIENT_ID=... --env GSC_CLIENT_SECRET=... --env GSC_REFRESH_TOKEN=... -- npx -y @getmcpads/google-search-console-mcp-server
Cursor

.cursor/mcp.json in your project, same shape as the Claude Desktop config above.

From source
git clone https://github.com/get-mcp-ads/google-search-console-mcp-server.git
cd google-search-console-mcp-server
npm install && npm run build
cp .env.example .env   # then fill in your credentials
npm start
Configuration
VariableDefaultMeaning
GSC_CLIENT_IDnoneOAuth client ID
GSC_CLIENT_SECRETnoneOAuth client secret
GSC_REFRESH_TOKENnoneFrom the consent flow
GSC_ACCESS_TOKENnoneAlternative to the three above, expires within the hour
GSC_SITE_URLnoneOptional default property
GSC_SITE_URLSunsetRecommended. Comma-separated properties every tool is limited to, written exactly as Search Console shows them. Unset, every property the credentials reach is available. Required in 3.0.0
LOG_LEVELinfodebug, info, warn, error

Either the three OAuth values, or GSC_ACCESS_TOKEN. The server refuses to start with neither.

npm run doctor

Tools

Every tool is listed below. See server-card.json for complete parameter and output schemas.

20 read tools

ToolPurpose
gsc_list_sitesList all Google Search Console properties accessible with the current credentials.
gsc_get_siteGet one Search Console property and its exact permission level (read-only sites.get).
gsc_health_checkVerify Google Search Console read-only authentication, visible properties, configured default site, and permission levels without exposing tokens.
gsc_query_search_analyticsQuery Google Search Console Search Analytics.
gsc_inspect_urlInspect a URL for Google indexing status, crawl info, mobile usability, AMP, and rich results.
gsc_bulk_inspect_urlsInspect multiple URLs with a conservative sequential limit and normalized URL Inspection results.
gsc_list_sitemapsList sitemaps submitted for a Search Console property, including processing status and submitted/indexed counts.
gsc_get_sitemapGet one submitted sitemap by full feed path, including type, fetch state, warnings/errors, and submitted/indexed content totals.
gsc_get_sitemap_healthReturn an enriched read-only sitemap health summary with status totals, submitted/indexed content counts, warnings, and errors.
gsc_compare_search_typesCompare performance across Search Console search types: web, image, video, news, discover, and Google News.
gsc_get_data_freshnessDetect the most recent date with Search Analytics data by querying recent daily rows.
gsc_monitor_indexation_freshnessRead-only monitoring snapshot for Search Analytics freshness, sitemap indexation totals, and an optional small URL Inspection sample.
gsc_track_sitemap_deltasRead-only sitemap delta tracker.
gsc_analyze_search_appearance_trendsAnalyze structured data and rich-result trend signals via the Search Analytics searchAppearance dimension when GSC exposes it.
gsc_plan_large_site_samplingBuild a read-only URL Inspection sampling plan for large sites from sitemap risk signals and Search Analytics page performance.
gsc_indexation_watchlistRead-only URL Inspection watchlist for critical URLs.
gsc_find_losses_gainsCompare two periods for query or page performance and return click/impression/CTR/position deltas.
gsc_cluster_queriesCluster Search Console queries by simple tokens and intent signals: brand/non-brand, question, category, and topic tokens.
gsc_detect_cannibalizationDetect queries where multiple pages compete for clicks/impressions in Search Analytics query-page rows.
gsc_validate_queryValidate a Search Console metric/dimension/search type combination before executing it.

7 resources

URIContents
gsc://manifestWhat this server exposes, and which tool to run first
gsc://metricsThe 8 Search Analytics metrics, raw and derived
gsc://dimensionsThe 7 dimensions and where they are valid
gsc://filtersThe 5 filter operators and their accepted values
gsc://compatibilityWhich dimensions work with which search types and data states
gsc://recipes8 step-by-step workflows
gsc://p2-readonly-playbooksMonitoring playbooks and their invariants

Security

  • The client secret and refresh token are never logged, at any log level, or written to disk.
  • A revoked refresh token is reported once. When Google answers invalid_grant, every later call returns the same message with the steps to authorize again, and the server stops asking Google for a token until it restarts.
  • Properties can be limited. With GSC_SITE_URLS set, a call naming another property is refused before any request, and gsc_list_sites lists only the allowed properties.
  • Three hosts are contacted, and only three: searchconsole.googleapis.com and www.googleapis.com for the API, oauth2.googleapis.com for the token refresh. A test fails the build if a fourth host appears in the source.
  • No fetch follows a redirect. Every outbound call sets redirect: "error", so a redirect cannot forward a bearer token or client secret to another host. A test fails the build if any fetch omits this.
  • The scope is webmasters.readonly. The token itself cannot write.
  • No telemetry. The server makes no network call other than to Google.

Full policy: SECURITY.md.


Looking for a managed, multi-platform version?

Try hosted Search Console if you want to use this source without operating a local server. getmcpads also connects advertising, Search Console and GA4 through one MCP URL. Source availability and plan limits are listed on the site; connecting an account is still required.

  1. Follow the Search Console connection guide.
  2. Select the account or property your assistant may read.
  3. Connect Claude, ChatGPT or Codex.
  4. Try a read-only review: “Find which pages and queries account for a change in organic clicks. State missing data and do not change anything.”

See the current hosted tool catalogue and pricing before choosing a paid plan. This Apache 2.0 adapter remains independently useful with your own credentials.


Contributing

Issues and pull requests are welcome. See CONTRIBUTING.md. Please read SECURITY.md before reporting anything security-related.

Licence

Apache License 2.0. See also NOTICE.

Google and Google Search Console are trademarks of Google LLC. This project is not affiliated with, endorsed by, or sponsored by Google LLC. It is an independent client of a public API.

MCP contracts and desktop bundle

Every tool declares read/write annotations, parameter descriptions and a structured output schema. Successful calls expose the payload as structuredContent.result; errors retain isError: true. The generated server card contains definitions only.

Run npm run bundle -- /path/to/output to build a .mcpb desktop bundle from the current catalog. Credentials are entered locally during installation. This server remains read-only.

More from getmcpads

Meta Ads · Google Ads · Google Analytics 4 · TikTok Ads · Pinterest Ads · X Ads

Maintained by Emmanuel at getmcpads. Questions: hello@getmcpads.com.

Frequently asked questions

What is Google Search Console?

Google Search Console MCP server: 20 read tools, no write tools.

How do I install Google Search Console?

It runs on your machine. In Claude Code: claude mcp add google-search-console -e 'GSC_CLIENT_ID=<GSC_CLIENT_ID>' -e 'GSC_CLIENT_SECRET=<your gsc_client_secret>' -e 'GSC_REFRESH_TOKEN=<your gsc_refresh_token>' -e 'GSC_ACCESS_TOKEN=<your gsc_access_token>' -e 'GSC_SITE_URL=<GSC_SITE_URL>' -e 'GSC_SITE_URLS=<GSC_SITE_URLS>' -- npx -y @getmcpads/google-search-console-mcp-server@2.1.1. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Google Search Console need an API key?

Yes. It expects GSC_CLIENT_SECRET, GSC_REFRESH_TOKEN, GSC_ACCESS_TOKEN, which you set in its configuration.

Is Google Search Console open source?

Yes. Its code is on GitHub under the Apache-2.0 license.

Who maintains Google Search Console?

It is published by get-mcp-ads. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.