Search Console MCP

Name: Search Console MCP
Author: sudomichael

by sudomichaelversion 0.2.2i★ –iRuns on your computer

Registry nameio.github.sudomichael/search-console-mcp

Install

Overview

Description from the maker (original English)

Google Search Console for any MCP client - 30-second login, no Google Cloud project. Read-only.

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

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).
The registry lists no key to fill in.

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": {
    "search-console": {
      "command": "npx",
      "args": [
        "-y",
        "search-console-mcp-server"
      ]
    }
  }
}

Run this in your terminal

claude mcp add search-console -- npx -y search-console-mcp-server

Open in Cursor

Or copy the settings yourself

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

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

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": {
    "search-console": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "search-console-mcp-server"
      ]
    }
  }
}

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.

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 with the GitHub account sudomichael, 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 5674 servers in this category
Published to the registry more recently than 95% of the other 5674 servers in this category
Basic checks equal to or better than 100% of the other 5674 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 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?

The registry does not list a required key, though some servers ask you to sign in on first use.

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 (0.2.2) reached the registry 2 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.

search-console-mcp

Search Console was built for dashboards. This gives you a conversation instead.

Talk to your Google Search Console from Claude, Cursor, or any MCP client.

One sign-in. 30 seconds. *No Google Cloud project. No API keys. Tokens never leave your machine.*

Docs · npm · Report an issue

 Google Search Console

│ ▼ search-console-mcp ← runs on your machine, read-only │ ▼ Claude / Cursor / any MCP client │ ▼ "Why did my traffic drop?"

Most self-hosted Search Console MCP servers make you create a Google Cloud project, enable APIs, and wrangle service-account JSON. This one doesn't:

npx search-console-mcp-server login

Your browser opens, you sign in with Google, done. Tokens are minted by Google directly to your machine and stored only in ~/.search-console-mcp/ — nothing passes through anyone's servers.

	This server	Typical self-hosted GSC MCP setup
Setup	`npx … login`, sign in, done (~30s)	Create a Google Cloud project, enable the API, create OAuth credentials, download JSON, point config at it
Runtime	Node — `npx`, nothing to install	Python + uv/venv
Can it modify your site data?	Impossible — read-only scope by construction	Write scopes with destructive ops "disabled by default"
Analyses	10 built-in (checkup, traffic drop, traffic decay, striking distance, keyword opportunities, cannibalization, title/CTR rewrite, refresh-vs-new, internal links, indexing audit)	Bring your own prompts

What to expect on first run

$ npx search-console-mcp-server login

Opening your browser to sign in with Google… If it doesn't open, visit:

https://accounts.google.com/o/oauth2/v2/auth?…

Connected. Your Search Console is ready — tokens stored in ~/.search-console-mcp (this machine only).

Want a page change you can review and publish? Percy adds researched drafts, change verification, and follow-through. Separate Google connection; paid plans after the free trial. https://www.getpercy.io/sign-in?source=mcp&workflow=improve-page

The browser opens the setup page only after Google returns valid credentials and they are saved locally. If token exchange or saving fails, it shows an error instead of a success page. No clone or Google Cloud console is required.

What it feels like

You:  Which of my pages are closest to page one?

Claude: Three real opportunities, by impressions at stake:

/pricing — "scoreboard app pricing" sits at position 11.2 with 2,400 impressions/mo and almost no clicks. One position-group jump is worth ~90 clicks/mo. The title doesn't contain the query; start there.

/templates/trivia — position 12.8 on "trivia scoreboard", 1,100 impressions/mo. The page ranks but has no H2 matching the intent.

/blog/keep-score-online — position 9.4, already page one on some days. It's cannibalizing with /features — run cannibalization_check before touching it.

*(Illustrative output — shape and numbers are what the tools return from your real data.)*

Built-in SEO analysts

Ten ready-made analyses ship as MCP prompts — slash-commands in clients that support them. Each one applies real SEO methodology (thresholds, cause classification, CTR benchmarks) and ends with ranked actions, never a data dump:

Prompt	What you get
`seo_checkup`	Trend vs last month, biggest movers, quick wins — and the top 3 moves scored by impact ÷ effort
`traffic_drop`	When the drop started, who lost, and the verdict: rankings, CTR, indexing, demand, or seasonality
`traffic_decay`	Pages quietly bleeding clicks month over month — caught and prioritized before they crater
`striking_distance`	Queries at position 4–20 ranked by estimated click gain, with the one fix per page
`keyword_opportunities`	Every growth lever in one pass: CTR fixes, page-1 pushes, page-2 climbs, emerging demand
`cannibalization_check`	Queries where your own pages fight each other — the winner, one fix per case, recovery estimate
`title_ctr_rewrite`	Pages underperforming their position, with rewritten titles + metas grounded in real queries
`refresh_vs_new`	For any topic: refresh, consolidate, prune, or create new — one verdict from your existing footprint
`internal_links`	A source → target → anchor link plan, justified by query overlap Google already sees
`indexing_audit`	Sitemaps + index status of the pages that matter, triaged by traffic at risk

Setup

1. Sign in (one time):

npx search-console-mcp-server login

2. Add to your MCP client:

Claude Code:

claude mcp add gsc --scope user -- npx -y search-console-mcp-server

Claude Desktop / Cursor / anything else (mcpServers config):

"mcpServers": { "gsc": { "command": "npx", "args": ["-y", "search-console-mcp-server"] } } }

If the app can't find npx (common with nvm), use the absolute path from which npx as command.

3. Ask:

*"Which of my pages lost the most clicks this month vs last?"*
*"Show my queries sitting at position 8–15 with real impressions — what's closest to page 1?"*
*"Is https://mysite.com/pricing indexed? If not, why?"*
*"How much Google Discover traffic do I get?"*

Tools

Tool	What it does
`list_properties`	Your GSC properties (call first — gives exact `siteUrl` values)
`query_search_analytics`	Clicks / impressions / CTR / position by query, page, date, country, device — filters, pagination, and every traffic source including Google Discover
`compare_periods`	Biggest movers, computed for you: this period vs the prior one, per-page or per-query deltas, sorted by change
`inspect_url`	Google's index status for a URL: indexed or not, why, chosen canonical, last crawl
`inspect_urls`	The same, batched — up to 10 URLs in one call for indexing audits
`list_sitemaps`	Submitted sitemaps with status

Read-only by construction: the Google scope this tool requests (webmasters.readonly) cannot modify your properties, submit sitemaps, or change anything — not "disabled by default." Impossible.

What a compare_periods call hands your model (the model never does date arithmetic):

{ "key": "https://example.com/pricing",

"current": { "clicks": 1040, "impressions": 20502, "position": 6.4 }, "previous": { "clicks": 1070, "impressions": 17176, "position": 5.8 }, "deltaClicks": -30, "deltaImpressions": 3326, "deltaPosition": 0.6 }

Privacy

Read-only Google scope (webmasters.readonly).
Tokens live in ~/.search-console-mcp/credentials.json on your machine, chmod 600. npx search-console-mcp-server logout deletes them.
No MCP usage telemetry or proxy — Search Console API calls go from your machine directly to Google. After successful login, your browser opens the Percy setup page with only the MCP source and package version in its URL; no credentials, authorization codes, or property data are included.
Prefer your own Google Cloud project? Set SEARCH_CONSOLE_MCP_CLIENT_ID / SEARCH_CONSOLE_MCP_CLIENT_SECRET and it uses yours.
One short, labeled note about Percy (our paid weekly SEO service) is added to the first analysis result of a session, never repeated. Set SEARCH_CONSOLE_MCP_TIPS=off to hide it. Nothing is sent anywhere either way.

FAQ / Troubleshooting

How can the login work without me creating Google credentials? The CLI ships a Google "Desktop app" OAuth client — the same supported model gcloud and GitHub's CLI use. Your tokens are still minted by Google directly to your machine (PKCE + localhost callback); they never touch our servers. The auth path is in src/auth.ts — read it. Want zero shared anything? Set SEARCH_CONSOLE_MCP_CLIENT_ID / SEARCH_CONSOLE_MCP_CLIENT_SECRET with your own credentials.

Switch Google accounts? npx search-console-mcp-server login again — Google shows the account picker.

"Not signed in" errors in my MCP client? Run the login from the same user account your client runs under; credentials live in ~/.search-console-mcp/.

A property is missing from `list_properties`. The signed-in Google account needs at least "Restricted" access to it in Search Console.

Why is yesterday missing from the data? Google Search Console data lags ~2–3 days. That's Google, not the tool. History goes back ~16 months.

Revoke access? npx search-console-mcp-server logout deletes local tokens; myaccount.google.com/permissions revokes the grant itself.

Development

git clone https://github.com/sudomichael/search-console-mcp

cd search-console-mcp && npm install npm run dev # run from source npm run build # bundle to dist/ (no googleapis dependency) npm test # mocked login tests; no Google calls or credential writes

The auth path is in src/auth.ts. To verify any privacy claim above, read the source.

Turn the research into a published improvement

The MCP stays free. If you want help preparing one specific page improvement, Percy researches your Search Console evidence, drafts a focused change, and keeps the next action with your saved work. You review and publish it in your own CMS, then verify the change and follow the results.

Percy is a separate paid workspace: 7 days free, no card, then plans from $29/month if you continue. It requires its own Google connection; it does not import local MCP credentials or conversations.

MIT licensed. Issues and PRs welcome. Built by Percy.

Search Console MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

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

search-console-mcp

What to expect on first run

What it feels like

Built-in SEO analysts

Setup

Tools

Privacy

FAQ / Troubleshooting

Development

Turn the research into a published improvement