Google Search Console

Name: Google Search Console
Author: sarahpark

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

注册名称io.github.sarahpark/google-search-console

安装

概览

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

Google Search Console MCP server — search analytics, URL inspection, and sitemaps

PopNx MCP 的三大支柱

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

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

它能帮你做什么

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

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

安装

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

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： GOOGLE_APPLICATION_CREDENTIALS

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

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

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

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

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

{
  "mcpServers": {
    "google-search-console": {
      "command": "npx",
      "args": [
        "-y",
        "@sarahpark/google-search-console-mcp"
      ],
      "env": {
        "GOOGLE_APPLICATION_CREDENTIALS": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add google-search-console --env GOOGLE_APPLICATION_CREDENTIALS=your-value -- npx -y @sarahpark/google-search-console-mcp

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

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

{
  "mcpServers": {
    "google-search-console": {
      "command": "npx",
      "args": [
        "-y",
        "@sarahpark/google-search-console-mcp"
      ],
      "env": {
        "GOOGLE_APPLICATION_CREDENTIALS": "your-value"
      }
    }
  }
}

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

在 VS Code 中打开

或者自己复制设置

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

{
  "servers": {
    "google-search-console": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@sarahpark/google-search-console-mcp"
      ],
      "env": {
        "GOOGLE_APPLICATION_CREDENTIALS": "your-value"
      }
    }
  }
}

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

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

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

需要你填写的值

GOOGLE_APPLICATION_CREDENTIALS 机密 env
Optional path to a service account JSON key; omit to use local Application Default Credentials

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

它能做什么

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

基础检查i

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

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

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

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

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

常见问题

Google Search Console 安全吗？

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

它需要哪些密钥或代码？

你需要填写：GOOGLE_APPLICATION_CREDENTIALS

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

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

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（1.1.0）于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,213MIT2个月前更新

安装

作者的 README

打开 README

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

Google Search Console MCP Server

A minimal MCP server for Google Search Console.

Give Codex, Claude Code, or Claude Desktop read-only access to your search analytics, URL indexing information, and sitemap status. Runs locally; cannot change your site or Search Console settings.

Once connected, ask your agent:

"Which queries had the most impressions but few clicks over the last 28 days?"
"Compare mobile vs desktop search performance this month."
"Check the indexing status of https://example.com/blog/my-post."

Setup · Tools · Limitations · Troubleshooting

Setup

You need Node.js and npm, an MCP client, and access to a Search Console property. To sign in as yourself, also install the Google Cloud CLI. Server startup and tool discovery were checked with Node.js 22.

1. Enable the Google API

Create or select a project in Google Cloud Console, then enable the Search Console API. Note the project ID for the next step.

2. Authenticate

Recommended for new users: sign in as yourself. Application Default Credentials (ADC) use your existing Search Console permissions, so you don't need to add another user to your properties.

Run both commands, replacing YOUR_PROJECT_ID with the project you enabled above:

gcloud auth application-default login \

--scopes=https://www.googleapis.com/auth/webmasters.readonly,https://www.googleapis.com/auth/cloud-platform gcloud auth application-default set-quota-project YOUR_PROJECT_ID

The quota project is required. For permission or scope errors, see troubleshooting.

Alternative: use a service account key

In Google Cloud Console, go to APIs & Services → Credentials → Create Credentials → Service account. Name it and finish creation; you can skip the optional role/access steps.
Open the service account, then Keys → Add Key → Create new key → JSON to download a key.
In Search Console, open each property's Settings → Users and permissions → Add user. Add the service account email with Restricted access.

[!CAUTION]

Store the key outside your repo and never commit it. Use its absolute path in your client's configuration below.

If Search Console rejects the email with "Failed to add user: email not found," sign in as yourself instead; see troubleshooting.

The server checks GOOGLE_APPLICATION_CREDENTIALS before local ADC. If switching to ADC, remove an old key-path setting from your client configuration and environment.

3. Install the server

The npx commands in the next step download and run version 1.1.0 for you. Both authentication methods work with the npm package; no clone or build is required.

Optional: build from source

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

cd google-search-console-mcp npm install npm run build

In the client commands below, replace npx -y @sarahpark/google-search-console-mcp@1.1.0 with node "/absolute/path/to/google-search-console-mcp/build/index.js". In Claude Desktop, set command to node and args to an array containing that absolute path. Run npm test for offline authentication checks.

Let Codex or Claude Code handle installation and configuration

After completing authentication, paste this into your agent:

Add npx -y @sarahpark/google-search-console-mcp@1.1.0 as gsc in this client's user-level MCP config, preserving existing servers. Use my local Application Default Credentials. Tell me when setup is complete and whether I need to restart the client.

For a service account, replace "Use my local Application Default Credentials" with "Set GOOGLE_APPLICATION_CREDENTIALS to /path/to/service-account-key.json" and use your actual file location.

Once configured, skip to step 5.

4. Connect your client

Choose your client and run the command for your authentication method. Replace placeholder paths with your actual absolute paths; keep quotes around paths containing spaces. Preserve any existing server entries.

Codex

Sign in as yourself (ADC):

codex mcp add gsc -- npx -y @sarahpark/google-search-console-mcp@1.1.0

npm package with a service account:

codex mcp add gsc \

--env "GOOGLE_APPLICATION_CREDENTIALS=/absolute/path/to/service-account-key.json" \ -- npx -y @sarahpark/google-search-console-mcp@1.1.0

For manual configuration in ~/.codex/config.toml, see the Codex MCP documentation.

Claude Code

Sign in as yourself (ADC):

claude mcp add gsc --scope user -- npx -y @sarahpark/google-search-console-mcp@1.1.0

npm package with a service account:

claude mcp add gsc --scope user \

--env "GOOGLE_APPLICATION_CREDENTIALS=/absolute/path/to/service-account-key.json" \ -- npx -y @sarahpark/google-search-console-mcp@1.1.0

--scope user makes the server available across your projects. Use --scope project to share configuration through the project's .mcp.json instead.

Claude Desktop

Add the appropriate entry to claude_desktop_config.json, merging it into any existing mcpServers object.

Sign in as yourself (ADC):

"mcpServers": { "gsc": { "command": "npx", "args": ["-y", "@sarahpark/google-search-console-mcp@1.1.0"] } } }

npm package with a service account:

"mcpServers": { "gsc": { "command": "npx", "args": ["-y", "@sarahpark/google-search-console-mcp@1.1.0"], "env": { "GOOGLE_APPLICATION_CREDENTIALS": "/absolute/path/to/service-account-key.json" } } } }

5. Verify the connection

Restart your client or start a new session, then ask:

Use the gsc MCP server to list my Search Console properties.

A successful list_sites call verifies both the connection and Google access. Use the exact property URL it returns in later requests, such as sc-domain:example.com or https://example.com/.

Tools

List your properties — list_sites

List all sites (properties) you have access to in Google Search Console.

No parameters required.

Query search performance — search_analytics

Query search analytics data — clicks, impressions, CTR, and position.

Parameter	Type	Required	Description
`siteUrl`	string	Yes	Site URL as it appears in Search Console (e.g. `https://example.com/` or `sc-domain:example.com`)
`startDate`	string	Yes	Start date in `YYYY-MM-DD` format
`endDate`	string	Yes	End date in `YYYY-MM-DD` format
`dimensions`	string	No	Comma-separated: `query`, `page`, `country`, `device`, `searchAppearance`, `date`
`rowLimit`	number	No	Max rows to return (default 100, max 25000)
`searchType`	string	No	`web`, `image`, `video`, `news`, `discover`, or `googleNews` (default `web`)
`queryFilter`	string	No	Filter by query. Prefix with `regex:` for regex matching
`pageFilter`	string	No	Filter by page URL. Prefix with `regex:` for regex matching
`countryFilter`	string	No	ISO 3166-1 alpha-3 country code (e.g. `USA`, `GBR`)
`deviceFilter`	string	No	`DESKTOP`, `MOBILE`, or `TABLET`

Inspect a URL — inspect_url

Check indexing status, crawl info, and mobile usability for a URL.

Parameter	Type	Required	Description
`siteUrl`	string	Yes	Site URL as it appears in Search Console
`inspectionUrl`	string	Yes	The full URL to inspect (must belong to the site)

Check sitemap status — list_sitemaps

List all submitted sitemaps and their status for a site.

Parameter	Type	Required	Description
`siteUrl`	string	Yes	Site URL as it appears in Search Console

Limitations

Search analytics returns at most 25,000 rows per call, without pagination. Results may omit pages or queries, and recent data may be incomplete.
URL inspection checks one URL at a time; it does not export a site's full indexing coverage report.
Your agent performs comparisons and opportunity analysis using the returned data. This is a local STDIO server, not a hosted ChatGPT web integration.

License

MIT

Troubleshooting

403 error: missing quota project or permission

If the error says the API "requires a quota project," rerun:

gcloud auth application-default set-quota-project YOUR_PROJECT_ID

Your account needs serviceusage.services.use on that project. If permission is denied, ask a project administrator to grant it or use a project where you have it, with the Search Console API enabled.

Login attempts to attach your configured project automatically but can skip it when you lack permission. Setting it explicitly makes that failure visible. The cloud-platform scope in the setup command allows the quota project to be attached.

gcloud won't grant the Search Console scope

The built-in gcloud client was confirmed to grant webmasters.readonly with Google Cloud SDK 557.0.0. If it doesn't work in your version, follow the gcloud guidance for additional scopes to create your own OAuth client, then sign in with its downloaded client file:

gcloud auth application-default login \

--client-id-file=client_id.json \ --scopes=https://www.googleapis.com/auth/webmasters.readonly,https://www.googleapis.com/auth/cloud-platform gcloud auth application-default set-quota-project YOUR_PROJECT_ID

Keep credential files outside your repo.

Search Console says "Failed to add user: email not found"

This has been reported when adding newly created service accounts and motivated the ADC option. Sign in as yourself, or use an existing service account that already has access to the property.

Missing credentials or no properties returned

Using npm 1.0.1 or earlier: update your client command to version 1.1.0 or later to use local gcloud ADC.
Using ADC: ensure an old GOOGLE_APPLICATION_CREDENTIALS setting isn't overriding your login. The signed-in Google account must have access to the property.
Using a service account: set GOOGLE_APPLICATION_CREDENTIALS to the key's absolute path and confirm its email was added to each property you want to read.

Google Search Console

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

需要你填写的值

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

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

常见问题

替代选择

Context7

Codebase Memory

Exa

作者的 README

Google Search Console MCP Server

Setup

1. Enable the Google API

2. Authenticate

3. Install the server

4. Connect your client

5. Verify the connection

Tools

Limitations

License

Troubleshooting