Back to Browse

Google Search Console MCP Server

Developer ToolsModerate6.3MCP RegistryLocal
Free

Server data from the Official MCP Registry

Google Search Console: 20 read-only tools for Search Analytics, sitemaps and indexing.

About

Google Search Console: 20 read-only tools for Search Analytics, sitemaps and indexing.

Security Report

6.3
Moderate6.3Moderate Risk

Valid MCP server (1 strong, 2 medium validity signals). 5 known CVEs in dependencies (0 critical, 3 high severity) Package registry verified. Imported from the Official MCP Registry.

3 files analyzed · 6 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

What You'll Need

Set these up before or after installing:

OAuth client ID.Optional

Environment variable: GSC_CLIENT_ID

OAuth client secret.Required

Environment variable: GSC_CLIENT_SECRET

OAuth refresh token, webmasters.readonly scope.Required

Environment variable: GSC_REFRESH_TOKEN

Short-lived access token, alternative to the three values above.Required

Environment variable: GSC_ACCESS_TOKEN

Default property, https://example.com/ or sc-domain:example.com.Optional

Environment variable: GSC_SITE_URL

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "com-getmcpads-google-search-console": {
      "env": {
        "GSC_SITE_URL": "your-gsc-site-url-here",
        "GSC_CLIENT_ID": "your-gsc-client-id-here",
        "GSC_ACCESS_TOKEN": "your-gsc-access-token-here",
        "GSC_CLIENT_SECRET": "your-gsc-client-secret-here",
        "GSC_REFRESH_TOKEN": "your-gsc-refresh-token-here"
      },
      "args": [
        "-y",
        "@getmcpads/google-search-console-mcp-server"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

google-search-console-mcp-server

CI License: Apache 2.0 Node

An open-source Model Context Protocol server for Google Search Console. It lets Claude, ChatGPT, Cursor or any MCP client query your search performance, inspect indexing, and analyse sitemaps.

Read-only, with no way to turn that off. You run it, and your credentials stay on your machine.

npx -y @getmcpads/google-search-console-mcp-server

Also listed in the MCP Registry as com.getmcpads/google-search-console, so clients that read the registry can install it by name.

Prefer not to run it yourself? getmcpads.com is the hosted version of this server, with Search Console alongside Meta Ads, Google Ads, TikTok Ads, Pinterest Ads and Google Analytics behind a single endpoint, hosted OAuth, and cross-platform reporting. Same tools, same safety model, no setup.


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"
      }
    }
  }
}

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/getmcpads-com/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
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

Discovery and health

ToolPurpose
gsc_health_checkValidates credentials and reachable properties
gsc_list_sites / gsc_get_siteProperties you can reach, and their permission level
gsc_get_data_freshnessHow settled the most recent data is

Search Analytics

ToolPurpose
gsc_query_search_analyticsThe main reporting tool. Dimensions, filters, date ranges
gsc_validate_queryCheck a combination before running it
gsc_compare_search_typesWeb, image, video, news and discover side by side
gsc_analyze_search_appearance_trendsHow rich results evolve over time

SEO analysis

ToolPurpose
gsc_detect_cannibalizationPages competing for the same query
gsc_find_losses_gainsQueries and pages won or lost between two periods
gsc_cluster_queriesGroup queries by shared intent

Indexing

ToolPurpose
gsc_inspect_urlCrawl and index status for one URL
gsc_bulk_inspect_urlsUp to 10 URLs per call, to protect your quota
gsc_indexation_watchlistTrack URLs whose verdict changed
gsc_monitor_indexation_freshnessFreshness and indexation drift together
gsc_plan_large_site_samplingBuild an inspection sample when you cannot inspect everything

Sitemaps

ToolPurpose
gsc_list_sitemaps / gsc_get_sitemapSubmitted sitemaps and their status
gsc_get_sitemap_healthErrors, warnings and pending states
gsc_track_sitemap_deltasWhat changed against a baseline you supply
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.
  • Four hosts are contacted, and only four: searchconsole.googleapis.com and www.googleapis.com for the API, oauth2.googleapis.com and accounts.google.com for OAuth. A test fails the build if a fifth 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?

This server does one platform, on your machine, with your credentials. That is on purpose.

If you'd rather not run it yourself, or you need Search Console alongside Meta Ads, Google Ads, TikTok Ads, Pinterest Ads and Google Analytics behind one endpoint, with hosted OAuth and cross-platform reporting, that's what we build at getmcpads.com.

Same philosophy, less plumbing. This project stays open source and independently useful either way.


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.

Reviews

No reviews yet

Be the first to review this server!