mcp-search-console
Multi-account Google Search Console MCP server for account routing, search analytics, URL inspection, and sitemap management.
List accounts and set the default account; force reauthentication.
List properties and get site verification/permission details.
Query search analytics, performance overviews, period comparisons, advanced filtered analytics, and page-level queries.
Inspect URLs individually or in batches and check indexing issues.
List, get, submit, and delete sitemaps; submit/delete require
GSC_ALLOW_DESTRUCTIVE=true.Use a named account per call or fall back to the default, with retried GSC API calls.
Query Google Search Console data including search analytics, indexing status, sitemaps, and URL inspection across multiple accounts.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-search-console Show top queries for my-site last month"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-search-console
Multi-account Google Search Console MCP server for operators who need one MCP surface across multiple sites or clients without restarting the server.
Release posture: beta package, version 0.1.3 from pyproject.toml.
Choose your path
You are... | Start here | Then |
Connecting the server to Claude/Codex/Cursor | Quick start below | |
Auditing account routing or destructive guards | ||
Reviewing packaging or registry metadata |
Related MCP server: searchconsole-mcp
Architecture
flowchart TD
U[AI operator] --> C[MCP client]
C --> S[FastMCP server]
S --> M[Account manager]
M --> F[Accounts config]
M --> A[OAuth or service-account auth]
S --> R[Retry wrapper]
R --> G[Google Search Console API]
G --> R --> SRequest flow
flowchart TD
P[Operator asks for analytics or indexing data] --> T[Selected MCP tool]
T --> A[Resolve named or default account]
A --> B[Build authenticated GSC client]
B --> C[Call Search Console endpoint]
C --> D{API call succeeds?}
D -- yes --> E[Return normalized JSON]
D -- retryable --> F[Backoff and retry]
F --> D
D -- no --> G[Return error payload]Quick start
Install the package.
python -m pip install mcp-search-console-multiCreate the accounts config.
mkdir -p ~/.config/mcp-search-console
cp accounts.example.json ~/.config/mcp-search-console/accounts.jsonRegister it in your MCP client.
{
"mcpServers": {
"search-console": {
"command": "uvx",
"args": ["mcp-search-console-multi"],
"env": {
"GSC_ACCOUNTS_CONFIG": "/Users/you/.config/mcp-search-console/accounts.json"
}
}
}
}Available tools
Tool group | Tools | Purpose |
Account routing |
| Inspect accounts, switch defaults, refresh auth |
Property inventory |
| Discover accessible properties and permissions |
Search analytics |
| Query search-performance data |
Inspection and sitemaps |
| Inspect indexing and manage sitemap submissions |
submit_sitemap and delete_sitemap stay behind the destructive flag documented in
docs/start-here.md.
Runtime proof
Claim | Proof |
Package entry point is stable |
|
Multi-account routing is first-class |
|
Search Console calls are retried |
|
Auth is file-driven per account |
Repo map
Path | Purpose |
FastMCP tool surface and response normalization | |
Account config, auth loading, client construction | |
OAuth and service-account auth implementations | |
Retry behavior for transient API failures | |
Setup, env, validation, common failures | |
Component map and runtime lifecycle |
Validation
Check | Command |
Import compiles |
|
Package builds |
|
README/docs links stay local |
|
License
MIT
Project context for new tasks
Use INDEX.md to find task-specific contracts; consult prompt.md when product direction is relevant. Historical examples do not select the current task.
Available Tools
17 toolsbatch_inspect_urlsA
Inspect multiple URLs at once. Returns one result per URL. Maximum 10 URLs per call (GSC API limit).
Inputs: site_url (required), page_urls (required), account. Returns: result
check_indexing_issuesB
Check a list of URLs for indexing problems. Returns a prioritised summary of issues — more actionable than raw inspect_url output.
Inputs: site_url (required), page_urls (required), account. Returns: result
compare_periodsB
Compare search performance between two date ranges. Returns rows for both periods side-by-side with delta calculations.
Inputs: site_url (required), period1_end (required), period2_end (required), period1_start (required), +4 more. Returns: object
delete_sitemapB
Delete a sitemap from Google Search Console. Requires GSC_ALLOW_DESTRUCTIVE=true.
Inputs: site_url (required), sitemap_url (required), account. Returns: object
get_advanced_search_analyticsC
Advanced search analytics with dimension filters.
filters format: [{"dimension": "country", "operator": "equals", "expression": "usa"}] operators: equals, notEquals, contains, notContains, includingRegex, excludingRegex
Inputs: end_date (required), site_url (required), start_date (required), account, +3 more. Returns: object
get_performance_overviewA
Get a high-level performance summary: total clicks, impressions, CTR, average position. No dimension breakdown — use get_search_analytics for that.
Inputs: end_date (required), site_url (required), start_date (required), account. Returns: object
get_search_analyticsB
Fetch search analytics data (clicks, impressions, CTR, position).
Inputs: end_date (required), site_url (required), start_date (required), account, +2 more. Returns: object
get_search_by_pageC
Get search queries driving traffic to a specific page URL.
Inputs: end_date (required), page_url (required), site_url (required), start_date (required), +2 more. Returns: object
get_site_detailsB
Get verification and permission details for a specific GSC property.
Inputs: site_url (required), account. Returns: object
get_sitemapC
Get details and status of a specific sitemap.
Inputs: site_url (required), sitemap_url (required), account. Returns: object
inspect_urlB
Inspect a URL's indexing status, last crawl date, mobile usability, and rich result eligibility.
Inputs: page_url (required), site_url (required), account. Returns: object
list_accountsA
List all configured GSC accounts and which is the current default.
Inputs: no named parameters. Returns: result
list_propertiesB
List all Google Search Console properties for the specified account.
Inputs: account. Returns: result
list_sitemapsB
List all sitemaps submitted to GSC for this property.
Inputs: site_url (required), account. Returns: result
reauthenticateA
Force re-authentication for an account. Clears the cached token and re-runs the OAuth flow (or reloads service account credentials). Useful when a token has been revoked or you need to switch Google accounts.
Inputs: account. Returns: object
set_default_accountA
Set the default account used when no account is specified in other tools.
Inputs: account (required). Returns: object
submit_sitemapB
Submit a sitemap to Google Search Console. Requires GSC_ALLOW_DESTRUCTIVE=true.
Inputs: site_url (required), sitemap_url (required), account. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 17 tools
Each tool targets a specific operation with clear boundaries. Search analytics tools are differentiated by scope and features (overview, compare, advanced, per-page). URL inspection tools distinguish single, batch, and actionable issue-checking.
All tool names use lowercase with underscores following a consistent verb_noun pattern (e.g., list_accounts, submit_sitemap, inspect_url). No mixing of styles.
17 tools is slightly above the typical 3-15 range, but each tool serves a distinct purpose within the Google Search Console domain. The count is justified by the breadth of functionality covered.
The tool set covers the full lifecycle: account management, property details, sitemap operations, multiple search analytics views, and URL inspection (single, batch, issue analysis). No obvious gaps for common GSC workflows.
Maintenance
Related MCP Connectors
Read-only Google Search Console MCP server for AI assistants.
Google Search Console, GA4 and PageSpeed MCP server for Claude, ChatGPT and Cursor. Free, hosted.
Hosted Google Search Console MCP server, with each action switched on or off per account.
Hosted MCP server for GA4, Google Ads and Search Console. Google OAuth, nothing to install.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceSelf-hosted MCP server that exposes Google Search Console tools (list sites, query analytics, inspect URL, list sitemaps) via natural language to AI assistants like ChatGPT and Claude.2MIT
- AlicenseAqualityDmaintenanceA lightweight, fast MCP server for Google Search Console. Query search analytics, manage sitemaps, and inspect URLs directly from your AI assistant.7Apache 2.0
- AlicenseNot gradedqualityDmaintenanceA unified MCP server that gives AI assistants direct access to Google Analytics 4, Google Search Console, Google Ads and Google Merchant Center data using OAuth2 user credentials.MIT
- FlicenseAqualityDmaintenanceMCP server integrating Google Search Console, Google Analytics 4, and GitHub, enabling AI clients to query search analytics, traffic data, and repository information.1-