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 分