mcp-gsc MCP — Casos de uso, Instalar & Demo ao vivo

Por que usar

Principais recursos

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

Demo ao vivo

Como fica na prática

gsc.replay ▶ pronto

0/0

Instalar

Escolha seu cliente

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

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

Abra Claude Desktop → Settings → Developer → Edit Config. Reinicie após salvar.

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

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

Cursor usa o mesmo esquema mcpServers que o Claude Desktop. Config de projeto vence a global.

VS Code → Cline → MCP Servers → Edit

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

Clique no ícone MCP Servers na barra lateral do Cline, depois "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

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

Mesmo formato do Claude Desktop. Reinicie o Windsurf para aplicar.

~/.continue/config.json

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

O Continue usa um array de objetos de servidor em vez de um map.

~/.config/zed/settings.json

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

Adicione em context_servers. Zed recarrega automaticamente ao salvar.

claude mcp add gsc -- uvx mcp-gsc

Uma linha só. Verifique com claude mcp list. Remova com claude mcp remove.

Casos de uso

Usos do mundo real: mcp-gsc

Generate a weekly SEO report with mcp-gsc

👤 SEO managers, content teams ⏱ ~15 min beginner

Quando usar: Monday morning — you want last week's performance summary before standup.

Pré-requisitos

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

Fluxo

Pull top queries + deltas

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

→ Delta table
Pull top landing pages movers

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

→ Winners + losers list
Draft the summary

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

→ Ready-to-paste report

Resultado: Monday report in 10 minutes.

Combine com: google-sheets

Audit indexing issues across your site

👤 Technical SEOs ⏱ ~30 min intermediate

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

Fluxo

Sample top pages

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

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

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

→ Diagnosis by cluster

Resultado: Prioritized fix list tied to real GSC verdicts.

Verify sitemap health and submission status

👤 Anyone launching new pages ⏱ ~10 min beginner

Quando usar: You just launched new pages — check Google picked up the sitemap.

Fluxo

List sitemaps

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

→ Sitemap health list
Resubmit stale ones

For sitemaps not read in 7 days, resubmit.✓ Copiado

→ Submitted

Resultado: Confidence that Google sees the new content.

Mine GSC for ranking opportunities

👤 Growth-stage SEOs ⏱ ~40 min intermediate

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

Fluxo

Find near-miss queries

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

→ 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.✓ Copiado

→ Effort-weighted opportunity list

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

Combine com: firecrawl

Combinações

Combine com outros MCPs para 10× de alavancagem

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.✓ Copiado

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.✓ Copiado

Ferramentas

O que este MCP expõe

Ferramenta	Entradas	Quando chamar	Custo
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

Custo e limites

O que custa rodar

Cota de API: GSC API: 1200 QPM per project, 6000 QPD per site
Tokens por chamada: Analytics results up to 25k rows per call — chunk before dumping
Monetário: Free
Dica: Use row_limit and filters; dumping top-10k queries ruins context for agents

Segurança

Permissões, segredos, alcance

Escopos mínimos: https://www.googleapis.com/auth/webmasters.readonly

Armazenamento de credenciais: GSC_OAUTH_CLIENT_SECRETS_FILE or GSC_CREDENTIALS_PATH in env

Saída de dados: searchconsole.googleapis.com

Nunca conceda: webmasters (full)

Solução de problemas

Erros comuns e correções

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)

Alternativas

mcp-gsc vs. outros

Alternativa	Quando usar	Troca
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

Mais

Recursos

📖 Leia o README oficial no GitHub

🐙 Ver issues abertas

🔍 Ver todos os 400+ servidores MCP e Skills