Gsc

io.github.mikusnuz由 GitHub 账号 mikusnuz 发布v1.3.6更新于 Oct 26, 2026

MCP server for Google Search Console & Indexing API — search analytics, sitemaps, URL inspection

已验证STDIO仅桌面网页搜索与抓取数据与分析

概览

AI 生成的概览

本地 MCP 服务器，让助手访问 Google Search Console 与 Indexing API：搜索分析、站点地图、网址检查和索引通知。

可以做什么
  • 列出、查看、添加和移除 Search Console 资源
  • 列出、查看、提交和删除站点地图
  • 按筛选、分组和小时维度查询搜索表现数据（点击、展示、点击率、排名）
  • 检查网址的索引状态、抓取信息、富媒体搜索结果和 AMP
  • 为符合条件的招聘信息或直播网址发送 Indexing API 通知，支持最多 100 条批量提交
适用场景
适合希望助手直接回答网站搜索表现问题、查找索引出错的页面、管理站点地图，或就符合条件的招聘信息与直播网址通知 Google 的场景。
运行要求
通过 npx 以 npm 包 @mikusnuz/gsc-mcp 在本地运行，需要 Node.js 20 或更高版本。认证方式二选一：OAuth2（GSC_CLIENT_ID、GSC_CLIENT_SECRET、GSC_REFRESH_TOKEN，需 webmasters 与 indexing 权限范围），或服务账号密钥文件路径 GSC_SERVICE_ACCOUNT_KEY_PATH。需在 Google Cloud 项目中启用 Search Console API 与 Indexing API，账号需对相应资源拥有所有者或足够权限。
安装前请注意
需要 Google OAuth 凭据或服务账号私钥文件，可读写你的 Search Console 资源。多个工具会修改数据：添加或移除站点、提交或删除站点地图、发送索引通知。Indexing API 调用消耗每日配额（默认每天 200 次发布请求），成功响应仅表示已收到通知，并不代表已收录。使用 Indexing API 工具时服务账号需为委托所有者。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Gsc，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only，通过 STDIO。 STDIO 服务会启动本地进程，因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

gsc-mcp

[npm version]

English | 한국어

[MCP Badge]

MCP server for Google Search Console API and Google Indexing API — full API coverage.

Requires Node.js 20 or newer, matching the MCP SDK's installed runtime dependencies.

When to Use

TaskTool
"Check which queries my site ranks for"search_analytics_query
"Notify Google about an eligible job posting or livestream URL"indexing_publish
"Find pages with indexing errors"url_inspection_inspect
"Get search performance data for the last 30 days"search_analytics_query
"Compare click-through rates between mobile and desktop"search_analytics_query (group by device)
"Submit my sitemap to Google"sitemaps_submit
"Batch notify eligible job posting/livestream URLs"indexing_batch_publish

For AI agents: See llms.txt for a machine-readable summary. Copy templates/CLAUDE.md or templates/AGENTS.md into your project to teach your agent about this MCP.

Unlike other GSC MCP servers that only wrap searchAnalytics.query, this server exposes every endpoint available in the Google Search Console and Indexing APIs.

Tools (13)

Sites

ToolDescription
sites_listList all sites (properties) in your Search Console
sites_getGet details of a specific site
sites_addAdd a new site (property)
sites_deleteRemove a site

Sitemaps

ToolDescription
sitemaps_listList all submitted sitemaps for a site
sitemaps_getGet details of a specific sitemap
sitemaps_submitSubmit a sitemap
sitemaps_deleteDelete a sitemap

Search Analytics

ToolDescription
search_analytics_queryQuery search performance data (clicks, impressions, CTR, position) with filtering and grouping. Supports hourly data with the hour dimension.

URL Inspection

ToolDescription
url_inspection_inspectInspect a URL's index status, crawl info, rich results, and AMP (the deprecated mobile-usability field may be absent)

Indexing API

ToolDescription
indexing_publishNotify Google about an eligible JobPosting or BroadcastEvent URL update/removal
indexing_get_metadataGet latest notification metadata for an eligible URL (requires contentType; not index status)
indexing_batch_publishBatch notify up to 100 eligible URLs and report every embedded request status

Indexing API eligibility: Google supports this API only for pages with JobPosting structured data or livestream pages with BroadcastEvent embedded in a VideoObject. The tools require contentType so callers must identify which supported type applies. A successful API response confirms receipt of the notification; it does not guarantee that Google indexed the URL. Use url_inspection_inspect to check index status. See Google's Indexing API usage guide.

Indexing API quotas

Google's default per-project limits are 200 publish requests per day, 180 metadata requests per minute, and 380 requests per minute across endpoints. The daily limit resets at midnight Pacific Time. A batch of 100 URLs still consumes 100 requests; batching reduces connections, not quota usage. Check your project's actual quota before sending notifications. See the official quota reference.

Authentication

Two authentication methods are supported:

Option 1: OAuth2 Refresh Token

json
{  "mcpServers": {    "gsc-mcp": {      "command": "npx",      "args": ["-y", "@mikusnuz/gsc-mcp"],      "env": {        "GSC_CLIENT_ID": "your-client-id",        "GSC_CLIENT_SECRET": "your-client-secret",        "GSC_REFRESH_TOKEN": "your-refresh-token"      }    }  }}

Required OAuth2 scopes:

  • https://www.googleapis.com/auth/webmasters
  • https://www.googleapis.com/auth/indexing

Option 2: Service Account

json
{  "mcpServers": {    "gsc-mcp": {      "command": "npx",      "args": ["-y", "@mikusnuz/gsc-mcp"],      "env": {        "GSC_SERVICE_ACCOUNT_KEY_PATH": "/path/to/service-account-key.json"      }    }  }}

For Search Console read/write tools, add the service account as an owner or user with sufficient permission. For Indexing API tools, Google requires the service account to be added as a delegated owner of the property; user-level access is not sufficient.

Setup Guide

OAuth2 Setup

  1. Go to Google Cloud Console
  2. Create a project (or select existing)
  3. Enable Search Console API and Indexing API
  4. Create OAuth 2.0 credentials (Desktop app type)
  5. Use the OAuth Playground to generate a refresh token with scopes:
    • https://www.googleapis.com/auth/webmasters
    • https://www.googleapis.com/auth/indexing

Service Account Setup

  1. Go to Google Cloud Console
  2. Create a service account
  3. Download the JSON key file
  4. Enable Search Console API and Indexing API
  5. In Search Console, add the service account email as an owner for your sites

License

MIT

来源：README.md，提交 16a3f5a

工具

0
SourceWeft 尚未在沙箱中启动过该软件包，因此其工具未知。

版本历史

3
  1. v1.3.6最新Oct 19, 2026
  2. v1.3.4Oct 8, 2026
  3. v1.3.1Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手；SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头，或保持端点能够响应探测，以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分