# mcp-gsc [Health: Active]

**Category:** 🎯 Marketing  
**Repository:** https://github.com/AminForou/mcp-gsc  
**GitHub Stars:** 2174  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/mcp-gsc-2

## Description
Google Search Console Insights with Claude AI for SEOs

## Tools
Capabilities this server exposes over MCP:

- **get_capabilities** — Lists all tools and shows auth status — call this first if unsure
- **list_properties** — Shows all your GSC properties
- **get_site_details** — Details about a specific site
- **get_search_analytics** — Top queries and pages with clicks, impressions, CTR, position
- **get_performance_overview** — Summary of site performance
- **compare_search_periods** — Compare performance between two time periods
- **get_search_by_page_query** — Search terms driving traffic to a specific page
- **get_advanced_search_analytics** — Analytics with filters by country, device, query, page
- **inspect_url_enhanced** — Detailed crawl/index status for a URL
- **batch_url_inspection** — Inspect up to 10 URLs at once
- **check_indexing_issues** — Check multiple URLs for indexing problems
- **get_sitemaps** — Lists all sitemaps for a site
- **list_sitemaps_enhanced** — Detailed sitemap info including errors and warnings
- **manage_sitemaps** — Submit or delete sitemaps
- **reauthenticate** — Re-run the OAuth browser login (switch accounts)

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "mcp-gsc": {
    "command": "uvx",
    "args": ["method"],
    "env": {
      "GSC_OAUTH_CLIENT_SECRETS_FILE": "",
      "GSC_CREDENTIALS_PATH": "",
      "GSC_SKIP_OAUTH": "",
      "GSC_ALLOW_DESTRUCTIVE": ""
    }
  }
}
```

**Requires environment variables:** `GSC_OAUTH_CLIENT_SECRETS_FILE`, `GSC_CREDENTIALS_PATH`, `GSC_SKIP_OAUTH`, `GSC_ALLOW_DESTRUCTIVE` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What mcp-gsc does

mcp-gsc exposes Google Search Console data and account operations as MCP tools for AI assistants. It covers four main areas:

- Property administration, including listing properties, viewing site details, and adding or removing properties.
- Search analytics, including queries, pages, clicks, impressions, click-through rate, position, trends, date comparisons, and filtered analysis.
- URL inspection, including crawl and index status for individual URLs or groups of URLs.
- Sitemap operations, including listing sitemaps, reviewing warnings and errors, and submitting or deleting sitemaps.

The analytics tools can identify queries bringing traffic to a site, summarize performance for a date range, compare two periods, or focus on a particular page. The advanced analytics tool supports filters such as country, device, query, and page.

## How it works

The server communicates with an MCP client such as Claude Desktop, Cursor, Codex CLI, or Gemini CLI. You ask the assistant for a Search Console operation, and it selects the corresponding tool and parameters, such as a site URL, page URL, date range, action, or list of URLs.

Authentication uses either a Google OAuth desktop application or a Google service account. OAuth opens a browser for the initial sign-in, then saves a token for later sessions. Service-account use requires granting the service account’s email access to the relevant Search Console property.

Search Console API calls run in a worker thread, so a slow request does not block other tool calls. OAuth requests read-only access by default; destructive operations require enabling the related setting.

## Setup and configuration

Before configuring the MCP client, create or select a Google Cloud project and enable the Search Console API. For OAuth, create a desktop OAuth client, configure the consent screen, and save the downloaded client-secrets JSON file. For service-account authentication, create a service account, download its JSON key, and add its email to the property in Search Console with full access.

The recommended launcher is `uvx`, which downloads and runs the `mcp-search-console` package. Client configuration supplies the full path to `uvx`, passes `mcp-search-console` as its argument, and sets the relevant environment variables.

Use `GSC_OAUTH_CLIENT_SECRETS_FILE` with OAuth. Use `GSC_CREDENTIALS_PATH` together with `GSC_SKIP_OAUTH=true` for a service account. After changing credentials or switching Google accounts, the `reauthenticate` tool starts the browser login flow again.

## Tools and capabilities

Available operations include:

- `get_capabilities` to list tools and show authentication status.
- `list_properties` and `get_site_details` for property discovery and details.
- `get_search_analytics`, `get_performance_overview`, and `compare_search_periods` for reporting.
- `get_search_by_page_query` and `get_advanced_search_analytics` for page-specific and filtered analysis.
- `inspect_url_enhanced`, `batch_url_inspection`, and `check_indexing_issues` for indexing investigations.
- `get_sitemaps`, `list_sitemaps_enhanced`, and `manage_sitemaps` for sitemap review and management.
- `reauthenticate` to repeat OAuth browser authentication.

`batch_url_inspection` accepts up to 10 URLs at once. Advanced analytics supports pagination and caps requests at 25,000 rows per page.

## Limitations and notes

The service-account method requires property access to be granted separately in Search Console. Operations that submit or delete sitemaps, or otherwise require write access, should be used with care; destructive access is not enabled by default. The MCP client must support running a standard MCP server through a command such as `uvx`.

_Full upstream README: https://allmcps.com/mcp/mcp-gsc-2/readme_