Google Search Console

Name: Google Search Console
Author: get-mcp-ads

by get-mcp-adsversion 2.1.1i★ –iRuns on your computer

Registry namecom.getmcpads/google-search-console

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Search & AI memory
You need to fill in: GSC_CLIENT_SECRET, GSC_REFRESH_TOKEN, GSC_ACCESS_TOKEN

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: GSC_CLIENT_ID, GSC_CLIENT_SECRET, GSC_REFRESH_TOKEN, GSC_ACCESS_TOKEN, GSC_SITE_URL, GSC_SITE_URLS

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "google-search-console": {
      "command": "npx",
      "args": [
        "-y",
        "@getmcpads/google-search-console-mcp-server"
      ],
      "env": {
        "GSC_CLIENT_ID": "your-value",
        "GSC_CLIENT_SECRET": "your-value",
        "GSC_REFRESH_TOKEN": "your-value",
        "GSC_ACCESS_TOKEN": "your-value",
        "GSC_SITE_URL": "your-value",
        "GSC_SITE_URLS": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add google-search-console --env GSC_CLIENT_ID=your-value --env GSC_CLIENT_SECRET=your-value --env GSC_REFRESH_TOKEN=your-value --env GSC_ACCESS_TOKEN=your-value --env GSC_SITE_URL=your-value --env GSC_SITE_URLS=your-value -- npx -y @getmcpads/google-search-console-mcp-server

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "google-search-console": {
      "command": "npx",
      "args": [
        "-y",
        "@getmcpads/google-search-console-mcp-server"
      ],
      "env": {
        "GSC_CLIENT_ID": "your-value",
        "GSC_CLIENT_SECRET": "your-value",
        "GSC_REFRESH_TOKEN": "your-value",
        "GSC_ACCESS_TOKEN": "your-value",
        "GSC_SITE_URL": "your-value",
        "GSC_SITE_URLS": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "google-search-console": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@getmcpads/google-search-console-mcp-server"
      ],
      "env": {
        "GSC_CLIENT_ID": "your-value",
        "GSC_CLIENT_SECRET": "your-value",
        "GSC_REFRESH_TOKEN": "your-value",
        "GSC_ACCESS_TOKEN": "your-value",
        "GSC_SITE_URL": "your-value",
        "GSC_SITE_URLS": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

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

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified against the domain getmcpads.com (the registry checks domain ownership)
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Search & AI memoryi

More stars than 0% of the other 7270 servers in this category
Published to the registry more recently than 75% of the other 7270 servers in this category
Basic checks equal to or better than 100% of the other 7270 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Google Search Console safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: GSC_CLIENT_SECRET, GSC_REFRESH_TOKEN, GSC_ACCESS_TOKEN

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (2.1.1) reached the registry 11 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated yesterday

Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 21 days ago

Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated last month

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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](https://www.getmcpads.com/home/film/get-mcp-ads-brand-film-1080p.mp4)

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.1: Zod 4 security update](https://github.com/get-mcp-ads/google-search-console-mcp-server/releases/tag/v2.1.1) · October 26, 2026

Update zod to 4.6.7. Every Zod release before 4.6.6 is covered by the high-severity advisory GHSA-mrhx-c7xc-m3w5: validating an oversized constrained collection can exhaust memory, and no Zod 3 release carries the fix. npm audit --omit=dev reports no vulnerability again.
Keep the Zod 3 validation behaviour. A parameter default is still validated and completed before use, so an omitted object must still supply its required fields.
Keep each parameter's own description when the parameter is optional or has a default. Zod 4 stores a description on the wrapped schema only, so the shared fallback description could otherwise replace it.
Tool names, parameters and descriptions published over MCP are unchanged. server-card.json is regenerated with Zod 4's JSON Schema output, which spells some constraints differently.

Earlier releases

Version	Date	Highlights
2.1.0	October 23, 2026	Site allowlist and revoked-token handling
2.0.1	September 23, 2026	Public repository restored
2.0.0	September 20, 2026	Gateway sync and security fixes
1.1.0	September 13, 2026	Platform capability sync and quality contracts
1.0.2	August 30, 2026	Announce the package version over MCP.
1.0.1	August 30, 2026	Add `server.json` and `mcpName` for the official MCP Registry, under `com.getmcpads/google-search-console`.
1.0.0	August 29, 2026	First 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.1 --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 tools	Search Analytics, sites, sitemaps, URL Inspection, and analyses built on top of them
SEO analyses, not just an API wrapper	Cannibalisation detection, query clustering, wins and losses between periods, indexation watchlists, large-site sampling plans
7 resources	Live catalogues the model can read: metrics, dimensions, filters, compatibility rules, 8 workflow recipes, read-only playbooks
Quota guardrails	Every URL Inspection call is capped at 10 URLs, so one exploratory question cannot burn a day of quota
No writes at all	Not 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:

Tool	Question it answers
`gsc_detect_cannibalization`	Which pages compete for the same query
`gsc_find_losses_gains`	What we won and lost between two periods
`gsc_cluster_queries`	Which queries belong to the same intent
`gsc_compare_search_types`	How web, image, video and news differ
`gsc_analyze_search_appearance_trends`	How rich results evolve
`gsc_indexation_watchlist`	Which URLs changed indexing verdict
`gsc_plan_large_site_sampling`	Which 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 type	Value
URL-prefix	`https://example.com/` (the trailing slash matters)
Domain	`sc-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

Variable	Default	Meaning
`GSC_CLIENT_ID`	none	OAuth client ID
`GSC_CLIENT_SECRET`	none	OAuth client secret
`GSC_REFRESH_TOKEN`	none	From the consent flow
`GSC_ACCESS_TOKEN`	none	Alternative to the three above, expires within the hour
`GSC_SITE_URL`	none	Optional default property

| GSC_SITE_URLS | *unset* | Recommended. Comma-separated properties

Only the beginning is shown; read the rest in the repo

Google Search Console

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

Google Search Console MCP server

Bring your search performance into the conversation.

What's new

Upgrade notes

Install this release

What you get

What it does beyond fetching rows

One thing to know before you trust a number

Read-only, and why it stays that way

Getting credentials

1. OAuth client

2. Refresh token

3. Site URL, optional

Setup

Claude Desktop

Claude Code

Cursor

From source

Configuration