/ ディレクトリ / プレイグラウンド / mcp-gsc
● コミュニティ AminForou ⚡ 即起動

mcp-gsc

作者 AminForou · AminForou/mcp-gsc

Pull Google Search Console data into Claude — 20 tools for search analytics, URL inspection, sitemaps. Perfect for SEO triage and reporting.

mcp-gsc (AminForou) connects Google Search Console to AI assistants. 20 tools cover property management, search analytics with filtering/comparison, URL inspection (indexing status), and sitemap submission/monitoring. Auth via OAuth (personal) or service account (team).

なぜ使うのか

主な機能

ライブデモ

実際の動作

gsc.replay ▶ 準備完了
0/0

インストール

クライアントを選択

~/Library/Application Support/Claude/claude_desktop_config.json  · Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "gsc": {
      "command": "uvx",
      "args": [
        "mcp-gsc"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop → Settings → Developer → Edit Config を開く。保存後、アプリを再起動。

~/.cursor/mcp.json · .cursor/mcp.json
{
  "mcpServers": {
    "gsc": {
      "command": "uvx",
      "args": [
        "mcp-gsc"
      ],
      "_inferred": true
    }
  }
}

Cursor は Claude Desktop と同じ mcpServers スキーマを使用。プロジェクト設定はグローバルより優先。

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "gsc": {
      "command": "uvx",
      "args": [
        "mcp-gsc"
      ],
      "_inferred": true
    }
  }
}

Cline サイドバーの MCP Servers アイコンをクリックし、"Edit Configuration" を選択。

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "gsc": {
      "command": "uvx",
      "args": [
        "mcp-gsc"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop と同じ形式。Windsurf を再起動して反映。

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "gsc",
      "command": "uvx",
      "args": [
        "mcp-gsc"
      ]
    }
  ]
}

Continue はマップではなくサーバーオブジェクトの配列を使用。

~/.config/zed/settings.json
{
  "context_servers": {
    "gsc": {
      "command": {
        "path": "uvx",
        "args": [
          "mcp-gsc"
        ]
      }
    }
  }
}

context_servers に追加。保存時に Zed がホットリロード。

claude mcp add gsc -- uvx mcp-gsc

ワンライナー。claude mcp list で確認、claude mcp remove で削除。

ユースケース

実用的な使い方: mcp-gsc

Generate a weekly SEO report with mcp-gsc

👤 SEO managers, content teams ⏱ ~15 min beginner

使うタイミング: Monday morning — you want last week's performance summary before standup.

前提条件
  • GSC access to the property — search.google.com/search-console
  • OAuth credentials or service account — console.cloud.google.com — enable Search Console API
フロー
  1. Pull top queries + deltas
    For acme.com, top 20 queries last week vs the previous week. Show clicks, CTR, position deltas.✓ コピーしました
    → Delta table
  2. Pull top landing pages movers
    Top 10 pages with the biggest clicks changes (up or down).✓ コピーしました
    → Winners + losers list
  3. Draft the summary
    Write a 5-bullet summary for the team meeting, with an action item for the biggest loser.✓ コピーしました
    → Ready-to-paste report

結果: Monday report in 10 minutes.

組み合わせ: google-sheets

Audit indexing issues across your site

👤 Technical SEOs ⏱ ~30 min intermediate

使うタイミング: Traffic dipped and you want to know if Google is still indexing what it should.

フロー
  1. Sample top pages
    From top 50 landing pages last month, inspect each URL's indexing status via inspect_url_enhanced.✓ コピーしました
    → Per-URL status: indexed/crawled-not-indexed/excluded
  2. Cluster issues
    Group by issue type. For 'crawled but not indexed', what's the common pattern?✓ コピーしました
    → Diagnosis by cluster

結果: Prioritized fix list tied to real GSC verdicts.

Verify sitemap health and submission status

👤 Anyone launching new pages ⏱ ~10 min beginner

使うタイミング: You just launched new pages — check Google picked up the sitemap.

フロー
  1. List sitemaps
    get_sitemaps for acme.com. Show last-read dates and error counts.✓ コピーしました
    → Sitemap health list
  2. Resubmit stale ones
    For sitemaps not read in 7 days, resubmit.✓ コピーしました
    → Submitted

結果: Confidence that Google sees the new content.

Mine GSC for ranking opportunities

👤 Growth-stage SEOs ⏱ ~40 min intermediate

使うタイミング: You want queries where you rank 11-20 and are close to page 1.

フロー
  1. Find near-miss queries
    Queries last 90 days with avg position between 11 and 20 AND >100 impressions. Return with the landing page.✓ コピーしました
    → Target list
  2. Prioritize by effort
    For top 20, check the landing page — is it already optimized for the query? If not, suggest on-page changes.✓ コピーしました
    → Effort-weighted opportunity list

結果: A prioritized SEO backlog grounded in your real GSC data.

組み合わせ: firecrawl

組み合わせ

他のMCPと組み合わせて10倍の力を

Automated weekly SEO report dropped into a shared sheet

Every Monday, run my weekly SEO report and append to 'SEO Weekly' sheet.✓ コピーしました
gsc + firecrawl

Scrape competitor pages ranking for your target queries

For each near-miss query in GSC, find the top SERP pages (via firecrawl), and summarize why they outrank me.✓ コピーしました

ツール

このMCPが提供する機能

ツール入力呼び出すタイミングコスト
list_properties Discover what you have access to 1 API call
get_search_analytics site, start_date, end_date, dimensions[], filters?, row_limit? The workhorse query 1 API call
inspect_url_enhanced site, url Per-URL indexing debug 1 API call
get_sitemaps site Sitemap health 1 API call
submit_sitemap site, feedpath Nudge Google to recrawl 1 API call

コストと制限

運用コスト

APIクォータ
GSC API: 1200 QPM per project, 6000 QPD per site
呼び出しあたりのトークン
Analytics results up to 25k rows per call — chunk before dumping
金額
Free
ヒント
Use row_limit and filters; dumping top-10k queries ruins context for agents

セキュリティ

権限、シークレット、影響範囲

最小スコープ: https://www.googleapis.com/auth/webmasters.readonly
認証情報の保管: GSC_OAUTH_CLIENT_SECRETS_FILE or GSC_CREDENTIALS_PATH in env
データ送信先: searchconsole.googleapis.com
絶対に付与しない: webmasters (full)

トラブルシューティング

よくあるエラーと対処法

403 User does not have permission

OAuth'd account or service account must be verified user in GSC for that property. Add under Settings → Users

Empty analytics response

GSC has 2-3 day data lag; end_date > today - 3 may be empty. Also: 'Web' vs 'Discover' search types differ

OAuth flow loops

Redirect URI in client_secrets.json must match exactly (including http://localhost port)

代替案

mcp-gsc 他との比較

代替案代わりに使う場面トレードオフ
GSC web UIAd hoc manual workNo automation, no reporting loop
Ahrefs/SEMrush APIsYou want third-party rank tracking, not Google's own dataPaid; different dataset

その他

リソース

📖 GitHub の公式 README を読む

🐙 オープンな issue を見る

🔍 400以上のMCPサーバーとSkillsを見る