mcp-search-console
Query Google Search Console data including search analytics, indexing status, sitemaps, and URL inspection across multiple accounts.
Click on "Install 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-consoleShow 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: gsc-mcp-connector
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
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/apexradius/mcp-search-console'
If you have feedback or need assistance with the MCP directory API, please join our Discord server