Google Search Console MCP

Name: Google Search Console MCP
Author: A1-x-Tech

by A1-x-Techversion 1.3.2i★ –iRuns on your computer

Registry nameio.github.A1-x-Tech/mcp-google-search-console

Install

Overview

Description from the maker (original English)

MCP server for the Google Search Console API: search analytics, sitemaps, URL inspection, sites.

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: GOOGLE_SEARCH_CONSOLE_CLIENT_SECRET, GOOGLE_SEARCH_CONSOLE_REFRESH_TOKEN, GOOGLE_SEARCH_CONSOLE_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: GOOGLE_SEARCH_CONSOLE_CLIENT_ID, GOOGLE_SEARCH_CONSOLE_CLIENT_SECRET, GOOGLE_SEARCH_CONSOLE_REFRESH_TOKEN, GOOGLE_SEARCH_CONSOLE_ACCESS_TOKEN, GOOGLE_SEARCH_CONSOLE_OAUTH_PORT, GOOGLE_SEARCH_CONSOLE_API_BASE, GOOGLE_SEARCH_CONSOLE_TIMEOUT_MS, GOOGLE_SEARCH_CONSOLE_MAX_RETRIES

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",
        "mcp-google-search-console"
      ],
      "env": {
        "GOOGLE_SEARCH_CONSOLE_CLIENT_ID": "your-value",
        "GOOGLE_SEARCH_CONSOLE_CLIENT_SECRET": "your-value",
        "GOOGLE_SEARCH_CONSOLE_REFRESH_TOKEN": "your-value",
        "GOOGLE_SEARCH_CONSOLE_ACCESS_TOKEN": "your-value",
        "GOOGLE_SEARCH_CONSOLE_OAUTH_PORT": "your-value",
        "GOOGLE_SEARCH_CONSOLE_API_BASE": "your-value",
        "GOOGLE_SEARCH_CONSOLE_TIMEOUT_MS": "your-value",
        "GOOGLE_SEARCH_CONSOLE_MAX_RETRIES": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add google-search-console --env GOOGLE_SEARCH_CONSOLE_CLIENT_ID=your-value --env GOOGLE_SEARCH_CONSOLE_CLIENT_SECRET=your-value --env GOOGLE_SEARCH_CONSOLE_REFRESH_TOKEN=your-value --env GOOGLE_SEARCH_CONSOLE_ACCESS_TOKEN=your-value --env GOOGLE_SEARCH_CONSOLE_OAUTH_PORT=your-value --env GOOGLE_SEARCH_CONSOLE_API_BASE=your-value --env GOOGLE_SEARCH_CONSOLE_TIMEOUT_MS=your-value --env GOOGLE_SEARCH_CONSOLE_MAX_RETRIES=your-value -- npx -y mcp-google-search-console

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",
        "mcp-google-search-console"
      ],
      "env": {
        "GOOGLE_SEARCH_CONSOLE_CLIENT_ID": "your-value",
        "GOOGLE_SEARCH_CONSOLE_CLIENT_SECRET": "your-value",
        "GOOGLE_SEARCH_CONSOLE_REFRESH_TOKEN": "your-value",
        "GOOGLE_SEARCH_CONSOLE_ACCESS_TOKEN": "your-value",
        "GOOGLE_SEARCH_CONSOLE_OAUTH_PORT": "your-value",
        "GOOGLE_SEARCH_CONSOLE_API_BASE": "your-value",
        "GOOGLE_SEARCH_CONSOLE_TIMEOUT_MS": "your-value",
        "GOOGLE_SEARCH_CONSOLE_MAX_RETRIES": "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",
        "mcp-google-search-console"
      ],
      "env": {
        "GOOGLE_SEARCH_CONSOLE_CLIENT_ID": "your-value",
        "GOOGLE_SEARCH_CONSOLE_CLIENT_SECRET": "your-value",
        "GOOGLE_SEARCH_CONSOLE_REFRESH_TOKEN": "your-value",
        "GOOGLE_SEARCH_CONSOLE_ACCESS_TOKEN": "your-value",
        "GOOGLE_SEARCH_CONSOLE_OAUTH_PORT": "your-value",
        "GOOGLE_SEARCH_CONSOLE_API_BASE": "your-value",
        "GOOGLE_SEARCH_CONSOLE_TIMEOUT_MS": "your-value",
        "GOOGLE_SEARCH_CONSOLE_MAX_RETRIES": "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

GOOGLE_SEARCH_CONSOLE_CLIENT_ID env
Google OAuth2 client id (refresh-token flow).
GOOGLE_SEARCH_CONSOLE_CLIENT_SECRET secret env
Google OAuth2 client secret (refresh-token flow). Treat it as a secret.
GOOGLE_SEARCH_CONSOLE_REFRESH_TOKEN secret env
Google OAuth2 refresh token, exchanged for access tokens automatically. Treat it as a secret.
GOOGLE_SEARCH_CONSOLE_ACCESS_TOKEN secret env
Static OAuth2 access token (~1h lifetime) — alternative to the refresh-token trio, mostly for testing.
GOOGLE_SEARCH_CONSOLE_OAUTH_PORT env
Fixed port for the loopback listener of the in-chat login (127.0.0.1 + PKCE). Set it when the client runs over SSH port forwarding; otherwise a free port is picked per login.
GOOGLE_SEARCH_CONSOLE_API_BASE env
API root override.
GOOGLE_SEARCH_CONSOLE_TIMEOUT_MS env
Per-request timeout in milliseconds.
GOOGLE_SEARCH_CONSOLE_MAX_RETRIES env
Retries on transient errors (429 always; 5xx/network for reads).

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 8, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account A1-x-Tech, which owns the repo
… 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 5670 servers in this category
Published to the registry more recently than 93% of the other 5670 servers in this category
Basic checks equal to or better than 100% of the other 5670 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 MCP 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: GOOGLE_SEARCH_CONSOLE_CLIENT_SECRET, GOOGLE_SEARCH_CONSOLE_REFRESH_TOKEN, GOOGLE_SEARCH_CONSOLE_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 (1.3.2) reached the registry 3 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 2 months ago

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

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.

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.

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

Codex

<<<<<<< Updated upstream In the app: open Settings → MCP servers, select Add server, choose STDIO, enter the command npx -y mcp-google-search-console@latest and environment variables GOOGLE_SEARCH_CONSOLE_CLIENT_ID, GOOGLE_SEARCH_CONSOLE_CLIENT_SECRET, GOOGLE_SEARCH_CONSOLE_REFRESH_TOKEN, then select Save and Restart. ||||||| Stash base In the app: open Settings → Plugins → MCP servers, choose Add server, then add npx -y mcp-google-search-console@latest with GOOGLE_SEARCH_CONSOLE_CLIENT_ID, GOOGLE_SEARCH_CONSOLE_CLIENT_SECRET and GOOGLE_SEARCH_CONSOLE_REFRESH_TOKEN. ======= In the app: open Settings → Plugins → MCP servers, choose Add server, then add npx -y mcp-google-search-console@latest.

>>>>>> Stashed changes

codex mcp add google-search-console \

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

Codex MCP documentation

Claude Code

claude mcp add \

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

Claude Code MCP documentation

Claude Desktop

The current official path is Settings → Extensions. For a custom desktop extension, open Advanced settings → Extension Developer → Install Extension…, select a .mcpb file and follow the prompts.

This repository currently publishes an npm stdio package and does not contain a .mcpb bundle. For Claude Desktop builds that still support local configuration, use the following JSON stdio configuration as a fallback:

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

In those builds, save it to ~/Library/Application Support/Claude/claude_desktop_config.json on macOS or %APPDATA%\Claude\claude_desktop_config.json on Windows.

Claude Desktop MCP documentation

Cursor

Add to ~/.cursor/mcp.json on macOS/Linux or %USERPROFILE%\.cursor\mcp.json on Windows:

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

Cursor MCP documentation

VS Code

Run MCP: Open User Configuration and add:

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

Check it with MCP: List Servers. VS Code MCP documentation

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

Operation	What happens	Confirmation boundary
List properties, analytics, sitemaps and URL status	Reads Search Console data	No change
Add a property	Adds a property entry; does not verify it	Changes account access
Submit or resubmit a sitemap	Requests processing of a sitemap	Changes Search Console state
Delete a property	Unlinks the property from the account; Google data is not deleted	Destructive
Delete a sitemap	Removes a submitted sitemap	Destructive
Raw API request	May call a write or delete endpoint	Potentially destructive

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:

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.
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.
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.
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)

Create or select a Google Cloud project and enable Google Search Console API.
Configure the OAuth consent screen and create a Desktop app OAuth client.
Use the OAuth 2.0 Playground with Use your own OAuth credentials to authorize the Google account that can access the properties and obtain a refresh token.
Use https://www.googleapis.com/auth/webmasters to include sitemaps and property changes. Use https://www.googleapis.com/auth/webmasters.readonly only if you intentionally need read-only access.

Testing-mode refresh tokens can expire after seven days. Publish the OAuth app, or use an Internal Workspace app, for long-lived access. Treat the client secret and refresh token as passwords.

Configuration

Every variable is optional — with none of them the server connects from the chat.

Variable	Required	Description
`GOOGLE_SEARCH_CONSOLE_CLIENT_ID`	No*	OAuth client ID.
`GOOGLE_SEARCH_CONSOLE_CLIENT_SECRET`	No*	OAuth client secret.
`GOOGLE_SEARCH_CONSOLE_REFRESH_TOKEN`	No*	OAuth refresh token.
`GOOGLE_SEARCH_CONSOLE_ACCESS_TOKEN`	No*	Short-lived alternative to the OAuth trio.
`GOOGLE_SEARCH_CONSOLE_OAUTH_PORT`	No	Fixed loopback port for the in-chat login; useful over SSH port forwarding.
`GOOGLE_SEARCH_CONSOLE_API_BASE`	No	API base URL override.
`GOOGLE_SEARCH_CONSOLE_TIMEOUT_MS`	No	Per-request timeout; default `60000` ms.
`GOOGLE_SEARCH_CONSOLE_MAX_RETRIES`	No	Temporary-error retries; default `3`.

\* Provide either the OAuth trio or an access token.

Data, limits and background work

Privacy. The local server calls Google and sends anonymous telemetry with an installation ID, versions and tool names — never OAuth tokens, property data, tool arguments or prompts. For each tool call it also sends the outcome and, on failure, an excerpt of the error text with e-mails, addresses, tokens, numb

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

Google Search Console MCP

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

See it work in a minute

Contents

Quick start

What you can ask it to do

Find search opportunities

Check index status and sitemaps

Manage properties carefully

How Search Console properties work

What can change

Getting access

Connect from the chat (recommended)

Environment variables (CI, unattended installs)

Configuration

Data, limits and background work