mcp-gsc MCP — Cas d'usage, Installer & Démo en direct

Pourquoi l'utiliser

Fonctionnalités clés

20 tools across properties, analytics, URL inspection, sitemaps
Compare periods: week-over-week, query/page/country breakdowns
URL inspection for indexing and crawl issues
OAuth or service account — fits solo or team setups

Démo en direct

Aperçu en pratique

gsc.replay ▶ prêt

0/0

Installer

Choisissez votre 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
    }
  }
}

Ouvrez Claude Desktop → Settings → Developer → Edit Config. Redémarrez après avoir enregistré.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "gsc": {
      "command": "uvx",
      "args": [
        "mcp-gsc"
      ],
      "_inferred": true
    }
  }
}

Cursor utilise le même schéma mcpServers que Claude Desktop. La config projet l'emporte sur la globale.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "gsc": {
      "command": "uvx",
      "args": [
        "mcp-gsc"
      ],
      "_inferred": true
    }
  }
}

Cliquez sur l'icône MCP Servers dans la barre latérale Cline, puis "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "gsc": {
      "command": "uvx",
      "args": [
        "mcp-gsc"
      ],
      "_inferred": true
    }
  }
}

Même format que Claude Desktop. Redémarrez Windsurf pour appliquer.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "gsc",
      "command": "uvx",
      "args": [
        "mcp-gsc"
      ]
    }
  ]
}

Continue utilise un tableau d'objets serveur plutôt qu'une map.

~/.config/zed/settings.json

{
  "context_servers": {
    "gsc": {
      "command": {
        "path": "uvx",
        "args": [
          "mcp-gsc"
        ]
      }
    }
  }
}

Ajoutez dans context_servers. Zed recharge à chaud à la sauvegarde.

claude mcp add gsc -- uvx mcp-gsc

Une seule ligne. Vérifiez avec claude mcp list. Supprimez avec claude mcp remove.

Cas d'usage

Usages concrets : mcp-gsc

Generate a weekly SEO report with mcp-gsc

👤 SEO managers, content teams ⏱ ~15 min beginner

Quand l'utiliser : Monday morning — you want last week's performance summary before standup.

Prérequis

GSC access to the property — search.google.com/search-console
OAuth credentials or service account — console.cloud.google.com — enable Search Console API

Déroulement

Pull top queries + deltas

For acme.com, top 20 queries last week vs the previous week. Show clicks, CTR, position deltas.✓ Copié

→ Delta table
Pull top landing pages movers

Top 10 pages with the biggest clicks changes (up or down).✓ Copié

→ Winners + losers list
Draft the summary

Write a 5-bullet summary for the team meeting, with an action item for the biggest loser.✓ Copié

→ Ready-to-paste report

Résultat : Monday report in 10 minutes.

Combiner avec : google-sheets

Audit indexing issues across your site

👤 Technical SEOs ⏱ ~30 min intermediate

Quand l'utiliser : Traffic dipped and you want to know if Google is still indexing what it should.

Déroulement

Sample top pages

From top 50 landing pages last month, inspect each URL's indexing status via inspect_url_enhanced.✓ Copié

→ Per-URL status: indexed/crawled-not-indexed/excluded
Cluster issues

Group by issue type. For 'crawled but not indexed', what's the common pattern?✓ Copié

→ Diagnosis by cluster

Résultat : Prioritized fix list tied to real GSC verdicts.

Verify sitemap health and submission status

👤 Anyone launching new pages ⏱ ~10 min beginner

Quand l'utiliser : You just launched new pages — check Google picked up the sitemap.

Déroulement

List sitemaps

get_sitemaps for acme.com. Show last-read dates and error counts.✓ Copié

→ Sitemap health list
Resubmit stale ones

For sitemaps not read in 7 days, resubmit.✓ Copié

→ Submitted

Résultat : Confidence that Google sees the new content.

Mine GSC for ranking opportunities

👤 Growth-stage SEOs ⏱ ~40 min intermediate

Quand l'utiliser : You want queries where you rank 11-20 and are close to page 1.

Déroulement

Find near-miss queries

Queries last 90 days with avg position between 11 and 20 AND >100 impressions. Return with the landing page.✓ Copié

→ Target list
Prioritize by effort

For top 20, check the landing page — is it already optimized for the query? If not, suggest on-page changes.✓ Copié

→ Effort-weighted opportunity list

Résultat : A prioritized SEO backlog grounded in your real GSC data.

Combiner avec : firecrawl

Combinaisons

Associez-le à d'autres MCPs pour un effet X10

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.✓ Copié

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.✓ Copié

Outils

Ce que ce MCP expose

Outil	Entrées	Quand appeler	Coût
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

Coût et limites

Coût d'exécution

Quota d'API: GSC API: 1200 QPM per project, 6000 QPD per site
Tokens par appel: Analytics results up to 25k rows per call — chunk before dumping
Monétaire: Free
Astuce: Use row_limit and filters; dumping top-10k queries ruins context for agents

Sécurité

Permissions, secrets, portée

Portées minimales : https://www.googleapis.com/auth/webmasters.readonly

Stockage des identifiants : GSC_OAUTH_CLIENT_SECRETS_FILE or GSC_CREDENTIALS_PATH in env

Sortie de données : searchconsole.googleapis.com

Ne jamais accorder : webmasters (full)

Dépannage

Erreurs courantes et correctifs

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)

Alternatives

mcp-gsc vs autres

Alternative	Quand l'utiliser	Compromis
GSC web UI	Ad hoc manual work	No automation, no reporting loop
Ahrefs/SEMrush APIs	You want third-party rank tracking, not Google's own data	Paid; different dataset

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills