mcp-search-console
Multi-account Google Search Console MCP server — connects GSC to any MCP-compatible AI assistant
Documentation
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 | docs/start-here.md | Quick start below |
| Auditing account routing or destructive guards | docs/architecture.md | `gsc/server.py` |
| Reviewing packaging or registry metadata | `pyproject.toml` | `server.json` |
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
1. Install the package.
python -m pip install mcp-search-console-multi2. Create the accounts config.
mkdir -p ~/.config/mcp-search-console
cp accounts.example.json ~/.config/mcp-search-console/accounts.json3. Register 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 | `list_accounts`, `set_default_account`, `reauthenticate` | Inspect accounts, switch defaults, refresh auth |
| Property inventory | `list_properties`, `get_site_details` | Discover accessible properties and permissions |
| Search analytics | `get_search_analytics`, `get_performance_overview`, `compare_periods`, `get_advanced_search_analytics`, `get_search_by_page` | Query search-performance data |
| Inspection and sitemaps | `inspect_url`, `batch_inspect_urls`, `check_indexing_issues`, `list_sitemaps`, `get_sitemap`, `submit_sitemap`, `delete_sitemap` | Inspect indexing and manage sitemap submissions |
`submit_sitemap` and `delete_sitemap` stay behind the destructive flag documented in
Runtime proof
| Claim | Proof |
|---|---|
| Package entry point is stable | `mcp-search-console-multi = "gsc.server:main"` in `pyproject.toml` |
| Multi-account routing is first-class | `AccountManager()` and `_get_manager()` in `gsc/server.py` |
| Search Console calls are retried | `with_retry()` in `gsc/server.py` and `gsc/retry.py` |
| Auth is file-driven per account | `accounts.example.json` and `gsc/accounts.py` |
Repo map
| Path | Purpose |
|---|---|
| `gsc/server.py` | FastMCP tool surface and response normalization |
| `gsc/accounts.py` | Account config, auth loading, client construction |
| `gsc/auth/` | OAuth and service-account auth implementations |
| `gsc/retry.py` | Retry behavior for transient API failures |
| `docs/start-here.md` | Setup, env, validation, common failures |
| `docs/architecture.md` | Component map and runtime lifecycle |
Validation
| Check | Command |
|---|---|
| Import compiles | `python -m compileall gsc` |
| Package builds | `python -m build` |
| README/docs links stay local | `rg '\\]\\(([^)]+\\.md)\\)' README.md docs/` |
License
MIT
Frequently asked questions
What is mcp-search-console?
mcp-search-console is Multi-account Google Search Console MCP server — connects GSC to any MCP-compatible AI assistant
How do I install mcp-search-console?
Open the GitHub repository and follow its README. Most MCP servers are added to your client's MCP config, then called by your agent.
Is mcp-search-console open source?
Yes — it is hosted on GitHub at https://github.com/apexradius/mcp-search-console.
Related MCP tools
Cognee is the open-source AI memory platform for agents. Give your AI agents persistent long-term memory across sessions with a self-hosted knowledge graph engine.
Automate browser based workflows with AI
Hindsight: Agent Memory That Learns
A privacy-first app that strips AI watermarks from content you own.
Agent framework and applications built upon Qwen>=3.0, featuring Function Calling, MCP, Code Interpreter, RAG, Chrome extension, etc.
The power of Claude Code / GeminiCLI / CodexCLI + [Gemini / OpenAI / OpenRouter / Azure / Grok / Ollama / Custom Model / All Of The Above] working as one.
Run your own MCP server? See who uses it and what to fix.
Measure it with TrackMCP