MCP.Market

Gsc MCP server

by pijusz·io.github.pijusz/mcp-gsc·v0.1.7·2 stars
No reviews yet

Google Search Console MCP server — query performance, sitemaps, indexing & more

B80/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B80/100

full report

Adoption
New

2 stars

Reviews

Write one

Nobody has reviewed Gsc yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Gsc tools (25, 3 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • add_site

    Add a new site to Google Search Console. The site must be verified separately after adding.

  • batch_inspect_urls

    Inspect up to 10 URLs simultaneously. Returns categorized results (indexed, not indexed, issues). Each URL counts against the daily 2,000 and per-minute 600 URL Inspection limits.

  • cannibalization

    Detect keyword cannibalization — multiple pages ranking for the same query. Uses query + page dimensions to find overlap.

  • compare_periods

    Compare two date ranges with delta calculations (absolute change + percentage change) for each dimension value. Makes 2 API calls.

  • content_decay

    Detect pages/queries where impressions have dropped significantly compared to their historical peak within the 16-month API window.

  • ctr_anomalies

    Detect queries/pages with abnormally low or high CTR relative to their position. Uses expected CTR curves per position bucket and flags deviations.

  • delete_sitewrite action

    Remove a site from Google Search Console. This does not affect the site itself, only removes it from your GSC account.

  • delete_sitemapwrite action

    Remove/unsubmit a sitemap from a property. This does not delete the sitemap file itself.

  • device_country_breakdown

    Performance breakdown by device type and/or country.

  • export_csv

    Export search analytics data to a CSV file. Auto-paginates internally (25K rows per API call) to write the full dataset, bypassing the tool response row cap. IMPORTANT: The GSC API has an absolute ceiling of 25,000 rows per query (sorted by impressions descending). For very large sites, this means the export will contain the top 25K query/page combinations, not the complete long tail. This is a Go

  • get_property_details

    Get verification info, ownership, and permissions for a specific Google Search Console property.

  • get_sitemap

    Get detailed info for a specific sitemap including content breakdown by type (web, image, video, etc.).

  • indexing_coverage

    Batch-inspect user-provided URLs and categorize by indexing status: indexed, not indexed, canonical mismatch, robots blocked, fetch error, other. Respects URL Inspection rate limits.

  • inspect_url

    Inspect a URL's indexing status, crawl info, rich results, mobile usability, and canonical URLs. Counts against the daily 2,000 and per-minute 600 URL Inspection limits.

  • list_properties

    List all Google Search Console properties you have access to, with permission levels and verification status.

  • list_sitemaps

    List all sitemaps for a property with status, type, indexed URL counts, errors/warnings.

  • opportunity_finder

    Find queries with improving impressions but low clicks, new emerging queries, and declining performers. Makes 2 API calls to compare periods.

  • performance_overview

    Aggregate metrics (total clicks, impressions, avg CTR, avg position) plus a daily trend breakdown for a property. Single API call.

  • position_tracking

    Track position changes for specific queries or pages over time. Uses date dimension with query/page filters. Returns daily or weekly averages.

  • quick_wins

    Find high-impression, low-CTR queries in striking distance (position 4-20). These are opportunities to improve rankings and CTR with small content or SEO tweaks.

  • search_analytics

    Query Google Search Console search performance data (clicks, impressions, CTR, position) with filtering and grouping. DIMENSIONS: query, page, country, device, date, searchAppearance, hour - "hour" requires data_state="hourly_all" and is limited to the last 10 days - "searchAppearance" CANNOT be combined with "query" or "page" (API restriction) TYPE: web (default), image, video, news, discover, go

  • sitemap_health

    Analyze all sitemaps: error/warning patterns, submission freshness (days since last submitted), indexed vs submitted ratio per sitemap.

  • submit_sitemapwrite action

    Submit a new sitemap URL for a property. The sitemap must be accessible at the provided URL.

  • top_movers

    Biggest gains and drops in clicks/impressions/position between two periods. Period A = start_date to end_date. Period B = the comparison_days before start_date.

  • weekly_seo_report

    All-in-one SEO report: runs performance overview + quick wins + top movers + indexing issues summary. Returns a combined markdown report.

Public scan report

scanner v0.1.10 · 2026-09-27 · same rubric, same numbers if you re-run it

1 medium
  • Code scan2 source files scanned20/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 58 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Findings (1)

  • mediumeval / new Function usedexec.eval
    dist/index.js: …eCode, sch); const makeValidate = new Function(`${names_1.default.self}`, `${names_1.de…
Overall 80/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Gsc compares

Against every graded SEO MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
80/100
higher than 60% of 769 SEO servers
Tools
25
the typical SEO server has 6
Tools that change things
12%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
2
more than 75% of 405 SEO servers

What its tools let an agent do: 21 read · 1 create · 1 change · 2 delete

Install Gsc in Claude Code, Cursor or VS Code

Runs npx -y mcp-gsc on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add mcp-gsc -- npx -y mcp-gsc
Add to Cursor

What the publisher says

From the Gsc repository's README, as published. We do not edit it. Read it on GitHub

mcp-gsc

Google Search Console MCP server — query search analytics, inspect URLs, manage sitemaps & more via natural language. Built with Bun + TypeScript. Works with Claude, Cursor, and any MCP client.

Quick Start

1. Get Credentials

You need OAuth client credentials from Google Cloud Console.

  1. Go to Google Cloud Console
  2. Create a project (or select existing)
  3. Enable the Google Search Console API:
  • APIs & Services → Library → search "Google Search Console API" → Enable
  1. Configure OAuth consent screen (if not done):
  • APIs & Services → OAuth consent screen → External
  • Fill in app name + your email, add scope https://www.googleapis.com/auth/webmasters
  1. Create credentials:
  • APIs & Services → Credentials → Create Credentials → OAuth client ID
  • Application type: Desktop app (allows localhost redirects automatically)
  • Download the JSON file
  1. Set the credentials path:
export GOOGLE_GSC_CREDENTIALS_PATH=/path/to/credentials.json
  1. Run setup to authorize:
npx mcp-gsc setup

This opens your browser for OAuth consent, saves a refresh token, verifies access to your GSC properties, and prints config snippets for your MCP client.

2. Add to Claude Code

claude mcp add gsc --scope user --transport stdio \
  -e GOOGLE_GSC_CREDENTIALS_PATH=/path/to/credentials.json \
  -- npx -y mcp-gsc@latest

That's it. Restart Claude Code and the tools are available.

Also works with bunx mcp-gsc@latest if you have Bun.

Requires Node 22+ when running via npx.

Claude Desktop / Cursor

Add to your claudedesktopconfig.json:

{
  "mcpServers": {
    "gsc": {
      "command": "npx",
      "args": ["-y", "mcp-gsc@latest"],
      "env": {
        "GOOGLE_GSC_CREDENTIALS_PATH": "/path/to/credentials.json"
      }
    }
  }
}

Codex CLI

Add to ~/.codex/config.toml (TOML, not JSON):

[mcp_servers.gsc]
command = "npx"
args = ["-y", "mcp-gsc@latest"]
startup_timeout_sec = 30
env = { GOOGLE_GSC_CREDENTIALS_PATH = "/path/to/credentials.json" }

Codex defaults to a 10s startup timeout, which is often too short for a cold npx fetch. Bump startuptimeoutsec (30 is safe) or install the package globally (npm i -g mcp-gsc) and use command = "mcp-gsc" instead.

Service Account (alternative)

For server-to-server auth without browser-based OAuth:

  1. Create a service account in Google Cloud Console
  2. Download the JSON key file
  3. In Google Search Console, add the service account email as a user for each property
  4. Point GOOGLEGSCCREDENTIALS_PATH to the key file — auth type is auto-detected

Tools (25)

Core Tools (always available)

Sites

Search Analytics

Dimensions: query, page, country, device, date, searchAppearance, hour

Types: web, image, video, news, discover, googleNews

Note: searchAppearance cannot combine with query or page. hour requires datastate="hourlyall" (last 10 days only). Country codes are ISO 3166-1 alpha-3 (usa, gbr, deu).

Sitemaps

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Gsc: common questions

Is Gsc MCP server safe?
Mostly: it is graded B (80/100). Read the Gsc safety report
How do I install Gsc?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Gsc need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Gsc maintained?
The last commit was 96 days ago (2026-07-31). The latest release is v0.1.7.
What can I use instead of Gsc?
Servers from other publishers that do the same job: SEO Skill MCP server, Google Search Console MCP server and SEO Tools: Google Search Console MCP server.
How does Gsc compare with other SEO MCP servers?
safety score 80/100 (higher than 60% of 769 SEO servers); tools 25 (the typical SEO server has 6); tools that change things 12% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Gsc

Same job from other publishers: the closest match first, then the best rated.

  • SEO Skill
    Free Google Search Console MCP: your real GSC, Google Analytics and keyword data for AI agents.
    A
  • Google Search Console
    Google Search Console: SEO audits, performance queries, URL inspection, indexing checks.
    B
  • SEO Tools: Google Search Console
    Google Search Console: Search Analytics, URL Inspection, sitemaps (read-only, OAuth/service acct).
    More from antohins →
    B
  • Google Search Console
    Google Search Console MCP for analytics, indexing, sitemaps, and SEO diagnostics.
    B
  • Google Search Console
    Google Search Console MCP server — search analytics, URL inspection, and sitemaps
    B

More from pijusz →