mcp-server-google-search-console
Enables interaction with Google Search Console via MCP, offering search analytics, performance summaries, URL inspection, sitemap management, and property listing for SEO workflows.
README
mcp-server-google-search-console
Community-built MCP server for the Google Search Console API. Provides search analytics, performance summaries, URL inspection, sitemap management, and property listing through the Model Context Protocol.
Features
- 9 tools covering search analytics, performance summaries, URL inspection, sitemap management, and property listing
- 3 prompts for guided multi-step SEO workflows
- 2 resources for automatic property and sitemap discovery
- Service Account & OAuth — choose headless or interactive authentication
- Read-only by default — write tools are only registered when write scope is configured
- Safety gates —
delete_sitemaprequires explicitconfirm: true - Minimal dependencies — only
@modelcontextprotocol/sdkandzod
Quick Start
1. Set Up Credentials
Service Account (recommended for servers & CI):
- Go to Google Cloud Console
- Create or select a project
- Enable the Google Search Console API
- Create a Service Account and download the JSON key file
- In Google Search Console, add the service account email as a user to your properties
OAuth (recommended for personal use):
- In Google Cloud Console, create OAuth 2.0 Client ID (type: Desktop app)
- Download the client credentials JSON
- Set
GSC_OAUTH_CLIENT_FILE— the server will open a browser for consent on first run - Tokens are cached at
~/.config/gsc-mcp/oauth-token.json(orGSC_OAUTH_TOKEN_FILE)
2. Configure Your Client
<details open> <summary><strong>Claude Code</strong></summary>
claude mcp add google-search-console \
-e GSC_SERVICE_ACCOUNT_KEY_FILE=/path/to/service-account-key.json \
-- npx -y mcp-server-google-search-console
Or add to .mcp.json manually:
{
"mcpServers": {
"google-search-console": {
"command": "npx",
"args": ["-y", "mcp-server-google-search-console"],
"env": {
"GSC_SERVICE_ACCOUNT_KEY_FILE": "/path/to/service-account-key.json"
}
}
}
}
</details>
<details> <summary><strong>Claude Desktop</strong></summary>
Add to claude_desktop_config.json:
{
"mcpServers": {
"google-search-console": {
"command": "npx",
"args": ["-y", "mcp-server-google-search-console"],
"env": {
"GSC_SERVICE_ACCOUNT_KEY_FILE": "/path/to/service-account-key.json"
}
}
}
}
</details>
<details> <summary><strong>Cursor</strong></summary>
Add to .cursor/mcp.json:
{
"mcpServers": {
"google-search-console": {
"command": "npx",
"args": ["-y", "mcp-server-google-search-console"],
"env": {
"GSC_SERVICE_ACCOUNT_KEY_FILE": "/path/to/service-account-key.json"
}
}
}
}
</details>
<details> <summary><strong>VS Code / Copilot</strong></summary>
Add to .vscode/mcp.json:
{
"servers": {
"google-search-console": {
"command": "npx",
"args": ["-y", "mcp-server-google-search-console"],
"env": {
"GSC_SERVICE_ACCOUNT_KEY_FILE": "/path/to/service-account-key.json"
}
}
}
}
</details>
<details> <summary><strong>Docker</strong></summary>
docker build -t gsc-mcp .
{
"mcpServers": {
"google-search-console": {
"command": "docker",
"args": [
"run", "--rm", "-i",
"-e", "GSC_SERVICE_ACCOUNT_KEY_FILE=/key.json",
"-v", "/path/to/service-account-key.json:/key.json:ro",
"gsc-mcp"
]
}
}
}
</details>
Tools
Always available (read-only scope)
| Tool | Description |
|---|---|
list_sites |
List all GSC properties accessible by the current credentials |
get_site |
Get details for a specific property (permission level, verification) |
get_search_analytics |
Query search performance data with dimensions, filters, date ranges, and comparison mode |
get_performance_summary |
Quick performance overview: current vs previous period metrics, deltas, and top 10 queries in a single call |
inspect_url |
Check a URL's indexing status, mobile usability, and rich results |
batch_inspect_urls |
Inspect multiple URLs concurrently (up to 20) with a single call |
list_sitemaps |
List all sitemaps for a property with aggregated health summary |
Write scope required
These tools are only registered when GSC_SCOPES includes the full write scope. They do not appear in the tool list otherwise.
| Tool | Description |
|---|---|
submit_sitemap |
Submit a sitemap to Google |
delete_sitemap |
Delete a sitemap (requires confirm: true safety gate) |
Prompts
Guided multi-step SEO workflows that guide LLMs through structured analysis.
| Prompt | Parameters | Description |
|---|---|---|
seo_performance_analysis |
site_url, period (7d/28d/90d) |
5-step analysis: Top Queries → Top Pages → Device Split → Country Split → Trends. Produces a structured report with actionable insights. |
index_coverage_check |
site_url, urls (comma-separated) |
Batch URL inspection with structured coverage report — flags indexing issues, canonical mismatches, and mobile problems. |
content_opportunity_analysis |
site_url |
Full-funnel analysis: Low-Hanging Fruit (positions 5–20), Keyword Cannibalization detection, and Trending queries via comparison mode. |
Resources
| URI | Description |
|---|---|
sites://list |
Auto-discovery of all GSC properties accessible with current credentials. Enables LLMs to discover available sites without calling list_sites first. |
sitemaps://{site_url} |
Sitemaps for a specific property (e.g. sitemaps://sc-domain:example.com) with health summary, errors, warnings, and index rates. |
Environment Variables
| Variable | Required | Description |
|---|---|---|
GSC_SERVICE_ACCOUNT_KEY_FILE |
* | Path to service account JSON key file |
GSC_SERVICE_ACCOUNT_KEY |
* | Inline service account JSON (alternative to file) |
GSC_OAUTH_CLIENT_FILE |
* | Path to OAuth client credentials JSON (Desktop app type) |
GSC_OAUTH_TOKEN_FILE |
No | Custom path for cached OAuth tokens (default: ~/.config/gsc-mcp/oauth-token.json) |
GSC_SCOPES |
No | OAuth scope. Default: webmasters.readonly. Set to https://www.googleapis.com/auth/webmasters for write access |
* Auth priority: OAuth (GSC_OAUTH_CLIENT_FILE) > Service Account (GSC_SERVICE_ACCOUNT_KEY_FILE or GSC_SERVICE_ACCOUNT_KEY). At least one must be configured.
Development
npm install # Install dependencies
npm run build # Build
npm run dev # Watch mode
npm test # Run tests
License
Note: This is an unofficial community project. It is not affiliated with or endorsed by Google.
Built by Tobias Hein at artaxo — a digital marketing agency specializing in AI Search Optimization.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.