gsc-mcp

Purpose

gsc-mcp is an MCP (Model Context Protocol) server used to connect to the Google Search Console API and the Google Indexing API. Its goal is to provide AI agents or automation tools with complete access to these two Google APIs. Unlike other GSC MCP servers that only wrap searchAnalytics.query, this project claims to expose all available endpoints in the Google Search Console and Indexing APIs, containing a total of 13 tools.

Main Capabilities

According to the project description, the server covers the following functional areas:

• Search Analytics: Provides search analytics-related endpoints.
• Sitemaps: Provides sitemap-related endpoints.
• URL Inspection: Provides URL inspection-related endpoints, among which url_inspection_inspect can be used to check indexing status.
• Batch Indexing (Indexing API): Provides Indexing API-related endpoints.

The project emphasizes that its difference from other GSC MCP servers that only wrap searchAnalytics.query lies in complete API coverage.

Usage

Authentication

The project supports two authentication methods:

Option 1: OAuth2 refresh token

Required OAuth2 scopes:

• https://www.googleapis.com/auth/webmasters
• https://www.googleapis.com/auth/indexing

Option 2: Service account

For Search Console read/write tools, the service account needs to be added as an owner or a user with sufficient permissions. For Indexing API tools, Google requires the service account to be added as a delegated owner of the property; user-level access permissions are insufficient.

OAuth2 setup steps

1. Go to Google Cloud Console
2. Create a project (or select an existing project)
3. Enable the Search Console API and Indexing API
4. Create OAuth 2.0 credentials (Desktop app type)
5. Use OAuth Playground to generate a refresh token, with the scope:https://www.googleapis.com/auth/webmasters https://www.googleapis.com/auth/indexing

Service account setup steps

1. Create a service account
2. Download the JSON key file
3. In Search Console, add the service account email as the owner of the website

For AI agents

The project provides llms.txt for AI agents to read a machine-readable summary. You can copy templates/CLAUDE.md or templates/AGENTS.md into the project to help agents understand this MCP.

Applicable scenarios

• Scenarios that require access to Google Search Console data through AI agents or automation tools.
• Scenarios that require performing URL inspection to confirm indexing status.
• Scenarios that require submitting indexing notifications to the Google Indexing API, but only for supported page types.

Limitations

• Indexing API eligibility restrictions: Google only supports this API for pages with JobPosting structured data, or BroadcastEvent live-stream pages embedded in VideoObject. The tool requires the caller to specify contentType to identify the applicable supported type.
• Indexing is not guaranteed: A successful API response only confirms that the notification was received, and does not guarantee that Google has indexed the URL. url_inspection_inspect must be used to check indexing status.
• Service account permission requirements: For Indexing API tools, the service account must be added as a delegated owner of the property; user-level access permissions are insufficient.

Other notes

Project name: gsc-mcp Repository address:https://github.com/mikusnuz/gsc-mcp

Regarding specific installation commands, dependencies, runtime environment requirements, charging model, price, platform support, actual results, or detailed usage steps, the current materials do not yet provide them.