Log inSubmit server
Gsc MCP logo

Gsc MCP

by mikusnuz

Manage Search Console properties, sitemaps, analytics, URL inspection, and eligible Indexing API notifications through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Gsc MCP

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": {
    "mikusnuz-gsc-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@mikusnuz/gsc-mcp"
      ],
      "env": {
        "GSC_CLIENT_ID": "YOUR_VALUE_HERE",
        "GSC_CLIENT_SECRET": "YOUR_VALUE_HERE",
        "GSC_REFRESH_TOKEN": "YOUR_VALUE_HERE",
        "GSC_SERVICE_ACCOUNT_KEY_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— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

mikusnuz/gsc-mcp connects MCP clients to the Google Search Console API and Google Indexing API through 13 tools. It manages properties and sitemaps, queries performance metrics, inspects URL indexing details, and sends single or batched indexing notifications. OAuth2 refresh tokens and Google service accounts are supported, with Node.js 20 or newer required. Reach for it when an agent needs to automate Search Console administration, SEO reporting, or indexing workflows.

Use cases

  • Query search performance by date, device, query, or page
  • Submit and manage Search Console sitemaps
  • Inspect URLs for indexing and crawl problems
  • Notify Google about eligible job or livestream URL changes
  • Batch indexing notifications for up to 100 URLs

Key features

  • Google Search Console property management
  • Sitemap listing, submission, and deletion
  • Filtered and grouped search analytics queries
  • URL index and crawl inspection
  • Single and batch Indexing API notifications
  • OAuth2 and service-account authentication

Tools13

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

Verified live~1.8k 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 3d ago

Recent health check succeeded.

4/4 checks healthy over the last 77d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 10d ago via OSV.dev · @mikusnuz/gsc-mcp (npm)

Adoption & maintenance

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

GitHub stars8Stargazers on the source repository.
npm downloads1.2kPackage downloads in the last 30 days.
Last commit7d agoMost recent push to the default branch.
Tools exposed13Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Gsc MCP works

What mikusnuz/gsc-mcp does

mikusnuz/gsc-mcp exposes Google Search Console and Google Indexing API operations as MCP tools. It covers property management, sitemap administration, search performance reporting, URL inspection, and indexing notifications.

The Search Console tools can list, inspect, add, and remove properties; list, inspect, submit, and delete sitemaps; query clicks, impressions, click-through rate, and position; and inspect a URL's index status, crawl information, rich results, and AMP details. Search analytics queries support filtering and grouping, including hourly data and device comparisons.

The Indexing API tools publish update or removal notifications for eligible URLs, retrieve notification metadata, and send up to 100 notifications in one batch request. Indexing notifications are limited to pages containing JobPosting structured data or livestream pages using BroadcastEvent within a VideoObject.

How it works

The package runs as an MCP process and can be launched with npx. An MCP client sends tool calls, while the server uses the configured Google credentials to call the relevant API. Search Console read and write operations require access to the target properties.

A successful Indexing API response confirms that Google received a notification; it does not confirm that the URL was indexed. Use url_inspection_inspect to check indexing status. The batch operation reduces the number of HTTP connections, but each URL still counts toward quota usage. Google's default limits listed for this integration are 200 publish requests per project per day, 180 metadata requests per minute, and 380 requests per minute across endpoints.

Setup and configuration

Node.js 20 or newer is required. The package can be added to an MCP client with a command configuration using npx -y @mikusnuz/gsc-mcp.

OAuth2 authentication uses GSC_CLIENT_ID, GSC_CLIENT_SECRET, and GSC_REFRESH_TOKEN. The OAuth credentials need the webmasters and indexing scopes. Alternatively, set GSC_SERVICE_ACCOUNT_KEY_PATH to a service-account JSON key file.

Before making API calls, enable the Google Search Console API and Google Indexing API in a Google Cloud project. For service-account access, grant the account appropriate Search Console permissions. Indexing API calls require the service account to be a delegated owner of the property, rather than only a user-level account.

Tools and capabilities

  • sites_list, sites_get, sites_add, and sites_delete manage Search Console properties.
  • sitemaps_list, sitemaps_get, sitemaps_submit, and sitemaps_delete manage submitted sitemaps.
  • search_analytics_query returns performance data with filtering and grouping options.
  • url_inspection_inspect reports URL indexing and crawl information.
  • indexing_publish sends an update or removal notification for one eligible URL.
  • indexing_get_metadata retrieves the latest notification timestamps for an eligible URL.
  • indexing_batch_publish sends notifications for up to 100 eligible URLs and reports each embedded request status.

Limitations and notes

Google's Indexing API eligibility rules apply to publishing and metadata operations. Callers must identify the supported content type. A notification is not a guarantee of indexing, and batching does not increase the daily request allowance. The deprecated mobile-usability field may be absent from URL inspection responses.

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 Gsc MCP

mikusnuz/gsc-mcp is an MCP server that connects AI agents to Google Search Console and Google Indexing APIs. Its 13 tools manage properties and sitemaps, query search analytics, inspect URL indexing details, and publish single or batched indexing notifications. Authentication uses OAuth2 refresh tokens or a Google service account.

Install it through an MCP client by running `npx -y @mikusnuz/gsc-mcp`. Node.js 20 or newer is required. Add either the OAuth2 variables `GSC_CLIENT_ID`, `GSC_CLIENT_SECRET`, and `GSC_REFRESH_TOKEN`, or `GSC_SERVICE_ACCOUNT_KEY_PATH` for service-account authentication.

Configure either OAuth2 credentials or a service-account key path. OAuth2 requires the `webmasters` and `indexing` scopes. Service accounts need suitable Search Console access, and Indexing API operations require delegated-owner status for the property.

Yes, `indexing_batch_publish` accepts up to 100 eligible URLs in one HTTP request and reports the status of each embedded request. Each URL still consumes one Indexing API request against the project's quota.

It can notify Google about eligible job-posting and livestream URLs. Job pages need `JobPosting` structured data, while livestream pages need `BroadcastEvent` embedded in a `VideoObject`; a successful notification does not guarantee indexing.

Related MCP servers

All in Search & Data Extraction 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 PreviewGsc MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mikusnuz-gsc-mcp?style=directory)](https://allmcps.com/mcp/mikusnuz-gsc-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/mikusnuz-gsc-mcp"><img src="https://allmcps.com/api/badge/mikusnuz-gsc-mcp?style=directory" alt="Gsc MCP on AllMCPs" /></a>