Log inSubmit server
MCP Gsc logo

MCP Gsc

Connect AI assistants to Google Search Console for analytics, URL inspection, sitemap management, exports, and optional SEO reports.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install MCP Gsc

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "mcp-gsc": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-gsc"
      ],
      "env": {
        "GOOGLE_GSC_CREDENTIALS_PATH": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

mcp-gsc connects MCP-compatible AI clients to Google Search Console through OAuth or a service account. It covers property discovery, search analytics, sitemap details, URL inspection, CSV exports, and optional reporting and SEO analysis tools. Write operations such as submitting sitemaps or requesting indexing are disabled by default and can be enabled separately. Reach for it when an agent needs to investigate organic search performance or perform selected Search Console maintenance tasks.

Use cases

  • Query top search queries and pages for a property
  • Inspect batches of URLs for indexing and crawl issues
  • Compare search performance across date ranges
  • Export Search Analytics data to a local CSV
  • Review sitemap health and indexing coverage

Key features

  • Search Analytics queries with dimensions and filters
  • URL inspection for indexing, crawl, canonicals, and rich results
  • Sitemap status and content inspection
  • CSV export with automatic pagination
  • Optional SEO, reporting, and technical SEO analysis
  • Optional property, sitemap, and indexing write operations

Tools27

What MCP Gsc lets your agent do. Expand a tool for its parameters.

Self-reported~443 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

8/8 checks healthy over the last 49d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 16d ago via OSV.dev · mcp-gsc (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars3Stargazers on the source repository.
npm downloads3.1kPackage downloads in the last 30 days.
Last commit4d agoMost recent push to the default branch.
Tools exposed27Callable tools this server registers over MCP.

How MCP Gsc works

What mcp-gsc does

mcp-gsc exposes Google Search Console data and operations as MCP tools for AI assistants. The core set can list verified properties, show property permissions and verification details, query clicks, impressions, CTR, and position, inspect sitemap status, and check URL indexing information.

Search Analytics queries support dimensions such as query, page, country, device, date, search appearance, and hour, along with filters and brand segmentation. Supported search types include web, image, video, news, Discover, and Google News. Results can be exported to a local CSV file, with automatic pagination for larger datasets.

Optional tool groups add period comparisons, trend summaries, top movers, device and country breakdowns, quick-win detection, cannibalization analysis, position tracking, CTR anomaly detection, content-decay checks, indexing coverage, sitemap health, and a weekly SEO report. Separate write tools can add or remove properties, submit or delete sitemaps, request URL crawling, and retrieve indexing submission status.

How it works

The server runs over MCP using standard input/output and communicates with Google APIs after authentication. OAuth credentials are authorized through a browser during setup, which stores a refresh token and checks access to available properties. A Google service-account key can also be used when that account has been added as a user to the relevant Search Console properties.

A default property can be configured, while bare domains are resolved against matching verified properties. URL inspection supports batches of up to 10 URLs. Google Search Console URL Inspection requests are automatically tracked against limits of 600 requests per minute and 2,000 per day per site.

Setup and configuration

Create Google Cloud credentials, enable the Google Search Console API, configure the OAuth consent screen with the webmasters scope, and create a desktop OAuth client. Set GOOGLE_GSC_CREDENTIALS_PATH to the downloaded JSON file, then run npx mcp-gsc setup to authorize access. Node.js 22+ is required when using npx; Bun users can run the package with bunx.

The optional GOOGLE_GSC_TOKEN_PATH controls cached token storage. GOOGLE_GSC_PROPERTY sets a default property, and GOOGLE_GSC_ENV_FILE selects an environment file. Set GOOGLE_GSC_ENABLE_EXTENDED_TOOLS=true for reporting, SEO, and technical SEO tools. Set GOOGLE_GSC_ENABLE_WRITES=true to expose mutation and indexing tools. DEBUG enables debug logging.

Tools and capabilities

Core capabilities include:

  • Query search performance with dimensions, filters, and search-type selection.
  • Inspect individual URLs or batches and review crawl, canonical, rich-result, and indexing information.
  • Review sitemap errors, types, freshness, indexed counts, and content breakdowns.
  • Export up to 1 million analytics rows to CSV, fetching up to 25,000 rows per call.
  • Compare periods and identify traffic movements or potential SEO opportunities when extended tools are enabled.
  • Manage properties and sitemaps or request crawls when write tools are enabled.

Limitations and notes

Hourly Search Analytics data requires data_state="hourly_all" and is limited to the last 10 days. Search appearance cannot be combined with query or page dimensions, and country filters use ISO 3166-1 alpha-3 codes.

Indexing requests require the Indexing API, a newly authorized credential with the indexing scope, and verified owner access to the property. Google officially supports that API for pages containing JobPosting or BroadcastEvent structured data, with a default quota of 200 URLs per day. A crawl request does not guarantee indexing.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about MCP Gsc

mcp-gsc is an MCP server that connects AI assistants to Google Search Console through its APIs. Its main tools list properties, query search analytics, inspect URLs, review and manage sitemaps, export analytics to CSV, and optionally run reporting, SEO, indexing, and write operations.

Install it through `npx -y mcp-gsc@latest` or use `bunx mcp-gsc@latest`. Set `GOOGLE_GSC_CREDENTIALS_PATH` to a Google OAuth client JSON or service-account key, then run `npx mcp-gsc setup` before adding the server to your MCP client.

Authenticate with Google OAuth or a service account. OAuth requires enabling the Search Console API, configuring consent, creating a desktop OAuth client, and running the setup command; service accounts must be added as users to each applicable Search Console property.

Yes, mcp-gsc works with Cursor through its MCP server configuration. Add a server entry that runs `npx -y mcp-gsc@latest` and pass `GOOGLE_GSC_CREDENTIALS_PATH` in the environment.

Set `GOOGLE_GSC_ENABLE_EXTENDED_TOOLS=true` before starting the server. This exposes reporting, SEO, and technical SEO tools such as period comparisons, quick wins, content decay, indexing coverage, sitemap health, and weekly SEO reports.

Related MCP servers

All in Marketing All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMCP Gsc AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mcp-gsc?style=directory)](https://allmcps.com/mcp/mcp-gsc)
HTML Embed
<a href="https://allmcps.com/mcp/mcp-gsc"><img src="https://allmcps.com/api/badge/mcp-gsc?style=directory" alt="MCP Gsc on AllMCPs" /></a>