/ Verzeichnis / Playground / mcp-gsc
← Alle Server ↗ GitHub
● Community AminForou ⚡ Sofort

mcp-gsc

von 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).

▶ Demo ansehen 📦 Installieren 💡 Anwendungsfälle

Warum nutzen

Hauptfunktionen

Live-Demo

In der Praxis

gsc.replay ▶ bereit
0/0

Installieren

Wählen Sie Ihren Client

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

Öffne Claude Desktop → Settings → Developer → Edit Config. Nach dem Speichern neu starten.

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

Cursor nutzt das gleiche mcpServers-Schema wie Claude Desktop. Projektkonfiguration schlägt die globale.

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

Klicken Sie auf das MCP-Servers-Symbol in der Cline-Seitenleiste, dann "Edit Configuration".

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

Gleiche Struktur wie Claude Desktop. Windsurf neu starten zum Übernehmen.

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

Continue nutzt ein Array von Serverobjekten statt einer Map.

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

In context_servers hinzufügen. Zed lädt beim Speichern neu.

claude mcp add gsc -- uvx mcp-gsc

Einzeiler. Prüfen mit claude mcp list. Entfernen mit claude mcp remove.

Anwendungsfälle

Praxisnahe Nutzung: mcp-gsc

Generate a weekly SEO report with mcp-gsc

👤 SEO managers, content teams ⏱ ~15 min beginner

Wann einsetzen: Monday morning — you want last week's performance summary before standup.

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

Ergebnis: Monday report in 10 minutes.

Kombinieren mit: google-sheets

Audit indexing issues across your site

👤 Technical SEOs ⏱ ~30 min intermediate

Wann einsetzen: Traffic dipped and you want to know if Google is still indexing what it should.

Ablauf
  1. Sample top pages
    From top 50 landing pages last month, inspect each URL's indexing status via inspect_url_enhanced.✓ Kopiert
    → 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?✓ Kopiert
    → Diagnosis by cluster

Ergebnis: Prioritized fix list tied to real GSC verdicts.

Verify sitemap health and submission status

👤 Anyone launching new pages ⏱ ~10 min beginner

Wann einsetzen: You just launched new pages — check Google picked up the sitemap.

Ablauf
  1. List sitemaps
    get_sitemaps for acme.com. Show last-read dates and error counts.✓ Kopiert
    → Sitemap health list
  2. Resubmit stale ones
    For sitemaps not read in 7 days, resubmit.✓ Kopiert
    → Submitted

Ergebnis: Confidence that Google sees the new content.

Mine GSC for ranking opportunities

👤 Growth-stage SEOs ⏱ ~40 min intermediate

Wann einsetzen: You want queries where you rank 11-20 and are close to page 1.

Ablauf
  1. Find near-miss queries
    Queries last 90 days with avg position between 11 and 20 AND >100 impressions. Return with the landing page.✓ Kopiert
    → 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.✓ Kopiert
    → Effort-weighted opportunity list

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

Kombinieren mit: firecrawl

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

gsc + google-sheets

Automated weekly SEO report dropped into a shared sheet

Every Monday, run my weekly SEO report and append to 'SEO Weekly' sheet.✓ Kopiert
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.✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

WerkzeugEingabenWann aufrufenKosten
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

Kosten & Limits

Was der Betrieb kostet

API-Kontingent
GSC API: 1200 QPM per project, 6000 QPD per site
Tokens pro Aufruf
Analytics results up to 25k rows per call — chunk before dumping
Kosten in €
Free
Tipp
Use row_limit and filters; dumping top-10k queries ruins context for agents

Sicherheit

Rechte, Secrets, Reichweite

Minimale Scopes: https://www.googleapis.com/auth/webmasters.readonly
Credential-Speicherung: GSC_OAUTH_CLIENT_SECRETS_FILE or GSC_CREDENTIALS_PATH in env
Datenabfluss: searchconsole.googleapis.com
Niemals gewähren: webmasters (full)

Fehlerbehebung

Häufige Fehler und Lösungen

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)

Alternativen

mcp-gsc vs. andere

AlternativeWann stattdessenKompromiss
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

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen