mcp-gsc MCP — Use Cases, Install & Live Demo

Why use it

Key features

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

Live Demo

What it looks like in practice

gsc.replay ▶ ready

0/0

Install

Pick your 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
    }
  }
}

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

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

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

Cursor uses the same mcpServers schema as Claude Desktop. Project config wins over global.

VS Code → Cline → MCP Servers → Edit

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

Click the MCP Servers icon in the Cline sidebar, then "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

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

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

~/.continue/config.json

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

Continue uses an array of server objects rather than a map.

~/.config/zed/settings.json

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

Add to context_servers. Zed hot-reloads on save.

claude mcp add gsc -- uvx mcp-gsc

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use mcp-gsc

Generate a weekly SEO report with mcp-gsc

👤 SEO managers, content teams ⏱ ~15 min beginner

When to use: Monday morning — you want last week's performance summary before standup.

Prerequisites

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

Flow

Pull top queries + deltas

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

→ Delta table
Pull top landing pages movers

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

→ Winners + losers list
Draft the summary

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

→ Ready-to-paste report

Outcome: Monday report in 10 minutes.

Combine with: google-sheets

Audit indexing issues across your site

👤 Technical SEOs ⏱ ~30 min intermediate

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

Flow

Sample top pages

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

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

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

→ Diagnosis by cluster

Outcome: Prioritized fix list tied to real GSC verdicts.

Verify sitemap health and submission status

👤 Anyone launching new pages ⏱ ~10 min beginner

When to use: You just launched new pages — check Google picked up the sitemap.

Flow

List sitemaps

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

→ Sitemap health list
Resubmit stale ones

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

→ Submitted

Outcome: Confidence that Google sees the new content.

Mine GSC for ranking opportunities

👤 Growth-stage SEOs ⏱ ~40 min intermediate

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

Flow

Find near-miss queries

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

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

→ Effort-weighted opportunity list

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

Combine with: firecrawl

Combinations

Pair with other MCPs for X10 leverage

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

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

Tools

What this MCP exposes

Tool	Inputs	When to call	Cost
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

Cost & Limits

What this costs to run

API quota: GSC API: 1200 QPM per project, 6000 QPD per site
Tokens per call: Analytics results up to 25k rows per call — chunk before dumping
Monetary: Free
Tip: Use row_limit and filters; dumping top-10k queries ruins context for agents

Security

Permissions, secrets, blast radius

Minimum scopes: https://www.googleapis.com/auth/webmasters.readonly

Credential storage: GSC_OAUTH_CLIENT_SECRETS_FILE or GSC_CREDENTIALS_PATH in env

Data egress: searchconsole.googleapis.com

Never grant: webmasters (full)

Troubleshooting

Common errors and fixes

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 others

Alternative	When to use it instead	Tradeoff
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

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills