Google Search Console MCP Intel Engine
# Google Search Console (GSC) MCP Server š
> **Model Context Protocol (MCP) server for Google Search Console: search performance analytics, keyword rankings, sitemap inspection, and indexing health for AI agents.**
[](https://github.com/surendranb/google-search-console-mcp/actions)
[](https://pypi.org/project/google-search-console-mcp/)
[](https://www.npmjs.com/package/@surendranb/google-search-console-mcp)
[](https://scorecard.dev/viewer/?site=github.com/surendranb/google-search-console-mcp)
[](LICENSE)
š **Live Documentation & Web Portal**: [https://gsc.builditwithai.xyz](https://gsc.builditwithai.xyz)
---
## ā” Quickstart
```bash
# 1-Line Universal Installer (Auto-configures Claude Desktop, Cursor, Claude Code, Antigravity, VS Code, Zed, Windsurf)
curl -fsSL "https://gsc.builditwithai.xyz/install" | bash
# Or run directly via your preferred runtime:
uvx google-search-console-mcp
npx -y @surendranb/google-search-console-mcp
```
---
---
## š¤ Client Setup
### A. Claude Code (CLI)
```bash
claude mcp add google-search-console -- uvx google-search-console-mcp
```
### B. Cursor & Google Antigravity (`mcp.json`)
```json
{
"mcpServers": {
"google-search-console": {
"command": "uvx",
"args": ["google-search-console-mcp"]
}
}
}
```
### C. Claude Desktop (`claude_desktop_config.json`)
```json
{
"mcpServers": {
"google-search-console": {
"command": "uvx",
"args": ["google-search-console-mcp"],
"env": {
"GSC_SITE_URL": "https://example.com/",
"GOOGLE_APPLICATION_CREDENTIALS": "/path/to/service_account.json"
}
}
}
}
```
### D. VS Code (Cline / Roo Code / Continue)
```json
{
"mcpServers": {
"google-search-console": {
"command": "npx",
"args": ["-y", "@surendranb/google-search-console-mcp"]
}
}
}
```
---
## š ļø Tools & Capabilities
| Tool Name | Parameters | Description | Return Type |
|---|---|---|---|
| `get_search_analytics` | `site_url` (string), `start_date` (string), `end_date` (string), `dimensions` (list), `row_limit` (int) | Queries organic search clicks, impressions, CTR, and average position grouped by query, page, country, device, and date. | `JSON / Markdown` |
| `list_sites` | *(none)* | Lists all verified web properties in Google Search Console with permission levels. | `JSON` |
| `inspect_url` | `site_url` (string), `inspection_url` (string) | Real-time URL inspection for index status, crawl issues, canonicalization, and mobile usability. | `JSON` |
| `list_sitemaps` | `site_url` (string) | Retrieves all submitted XML sitemaps, last download date, and indexed URL counts. | `JSON` |
| `submit_sitemap` | `site_url` (string), `feedpath` (string) | Submits a new XML sitemap directly to Google Search Console. | `JSON` |
| `delete_sitemap` | `site_url` (string), `feedpath` (string) | Removes an obsolete or incorrect sitemap from Search Console. | `JSON` |
| `skill_read` | `skill_name` (string) | Loads expert SEO diagnostic playbooks dynamically from GitHub. | `Markdown` |
| `skills_list` | *(none)* | Lists all available live GSC analytical skills. | `JSON` |
---
## š Telemetry & Privacy
This package collects anonymous, non-PII diagnostic telemetry (command executions, latency, error codes) to improve tool reliability. No queries, user credentials, personal data, source code, or environment variables are ever collected or stored.
You can opt out anytime by setting either of the following environment variables:
```bash
export DO_NOT_TRACK=1
# or
export MCP_TELEMETRY_OPT_OUT=1
```
---
## š License
MIT License. See [LICENSE](LICENSE) for details.
TDQS
Scored across 10 tools
Each tool targets a distinct resource or action: sites, dimensions, metrics, skills, sitemaps, analytics, and setup. The only similar pair is skills_list/skill_read but they are clearly list vs. fetch-content, matching the standard pattern. No meaningful overlap.
Most tools follow a clear verb_noun snake_case pattern (list_, get_, submit_, delete_, setup_). However, skills_list and skill_read invert the convention to noun_verb, which is a minor but noticeable deviation from the dominant pattern.
Ten tools is well-scoped for a GSC integration, covering metadata discovery, sitemap management, analytics retrieval, skills/playbooks, and setup. Each tool has a clear role without redundancy or bloat.
The surface covers core GSC workflows: listing sites, querying analytics, managing sitemaps, and enumerating dimensions/metrics. Minor gaps exist, such as no direct URL inspection tool or ability to fetch a single site's details, but these can be worked around with existing tools.