Search Console MCP

Name: Search Console MCP
Author: sudomichael

作者：sudomichael版本 0.2.2i★ –i在你的电脑上运行

注册名称io.github.sudomichael/search-console-mcp

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 搜索与 AI 记忆

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
注册中心没有列出需要填写的密钥。

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

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

在终端中运行这条命令

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

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 sudomichael 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“搜索与 AI 记忆”中的其他服务器比较i

星标数多于此分类中其他 5652 个服务器的 0%
发布到注册中心的时间比此分类中其他 5652 个服务器的 95% 更新
基础检查结果等于或优于此分类中其他 5652 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Search Console MCP 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.2.2）于前天进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它？

同一分类中有：Context7, Codebase Memory, Exa

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Context7

作者：upstash

Up-to-date docs for AI agents

电脑或云端★ 64,224MIT昨天更新

安装

Codebase Memory

作者：DeusData

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

在你的电脑上运行★ 48,148MIT21天前更新

安装

Exa

作者：exa-labs

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

在云端运行★ 5,213MIT上个月更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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.