Server data from the Official MCP Registry
Multi-account Google Search Console MCP: analytics, URL inspection, sitemaps across named accounts.
Multi-account Google Search Console MCP: analytics, URL inspection, sitemaps across named accounts.
This is a well-structured MCP server for Google Search Console with proper authentication, appropriate permission scoping, and solid error handling. OAuth and service account credentials are handled securely using Google's official libraries, tokens are stored in user-controlled locations (not hardcoded), and destructive operations are protected by an environment flag. Minor code quality observations noted, but no security vulnerabilities detected. Supply chain analysis found 5 known vulnerabilities in dependencies (1 critical, 3 high severity). Package verification found 1 issue.
7 files analyzed · 11 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: GSC_ACCOUNTS_CONFIG
Environment variable: GSC_ALLOW_DESTRUCTIVE
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-ayo-fam-mcp-search-console": {
"env": {
"GSC_ACCOUNTS_CONFIG": "your-gsc-accounts-config-here",
"GSC_ALLOW_DESTRUCTIVE": "your-gsc-allow-destructive-here"
},
"args": [
"mcp-search-console-multi"
],
"command": "uvx"
}
}
}From the project's GitHub README.
Multi-account Google Search Console MCP server. Connect any number of GSC accounts to Claude, Cursor, Codex, or any MCP-compatible AI assistant — and query them by name in the same session.
# Install: uvx mcp-search-console-multi
# Ask your AI:
"Show me the top queries for my-site last month"
"Compare client-acme's performance between Q1 and Q2"
"Check indexing issues on client-beta's 5 product pages"
Most GSC MCP servers support one account per server process. This one lets you configure multiple accounts (your own sites + client sites) and switch between them per tool call — no restart needed.
| Feature | This server | Others |
|---|---|---|
| Multiple accounts | Yes — named, switchable | No — one per process |
| OAuth + service account | Both, mixed per account | Usually one type |
| Auto token refresh | Yes | Sometimes |
| Rate limit retry | Yes — exponential backoff | No |
| Destructive op guard | Yes — env flag required | Sometimes |
| SSE transport (remote) | Yes | Varies |
1. Create your accounts config:
mkdir -p ~/.config/mcp-search-console
cp accounts.example.json ~/.config/mcp-search-console/accounts.json
# Edit it — add your accounts
2. Add to your MCP client config:
{
"mcpServers": {
"search-console": {
"command": "uvx",
"args": ["mcp-search-console-multi"],
"env": {
"GSC_ACCOUNTS_CONFIG": "/Users/you/.config/mcp-search-console/accounts.json"
}
}
}
}
3. Restart your AI client. Done.
Copy accounts.example.json and edit it:
{
"default": "my-site",
"accounts": {
"my-site": {
"type": "oauth",
"client_secrets_file": "~/.config/mcp-search-console/client_secrets.json",
"token_file": "~/.config/mcp-search-console/my-site.token"
},
"client-acme": {
"type": "service_account",
"credentials_file": "~/.config/mcp-search-console/acme.json"
}
}
}
Set GSC_ACCOUNTS_CONFIG to its path, or put it at ~/.config/mcp-search-console/accounts.json (default).
client_secrets.jsonEvery tool accepts an optional account parameter. Omit it to use your default.
"Show top queries for my-site" # uses default
"Show top queries for client-acme" # uses named account
"Compare client-beta performance Jan vs Feb" # named account
Or set the default mid-session:
"Switch to client-acme as my default account"
| Tool | What it does |
|---|---|
list_accounts | Show all configured accounts and which is default |
set_default_account | Change the default account |
reauthenticate | Re-run OAuth flow or reload credentials for an account |
| Tool | What it does |
|---|---|
list_properties | List all GSC properties |
get_site_details | Verification + permission details for a property |
| Tool | What it does |
|---|---|
get_search_analytics | Queries, pages, clicks, impressions, CTR, position |
get_performance_overview | Site-level totals for a period |
compare_periods | Side-by-side comparison of two date ranges |
get_advanced_search_analytics | Analytics with dimension filters (country, device, etc.) |
get_search_by_page | Queries driving traffic to a specific page |
| Tool | What it does |
|---|---|
inspect_url | Indexing status, crawl date, mobile usability, rich results |
batch_inspect_urls | Inspect up to 10 URLs at once |
check_indexing_issues | Prioritised issue summary across multiple URLs |
| Tool | What it does |
|---|---|
list_sitemaps | All submitted sitemaps with status |
get_sitemap | Details for a specific sitemap |
submit_sitemap | Submit a new sitemap (requires GSC_ALLOW_DESTRUCTIVE=true) |
delete_sitemap | Remove a sitemap (requires GSC_ALLOW_DESTRUCTIVE=true) |
| Variable | Default | Description |
|---|---|---|
GSC_ACCOUNTS_CONFIG | ~/.config/mcp-search-console/accounts.json | Path to your accounts config |
GSC_ALLOW_DESTRUCTIVE | unset | Set to true to enable sitemap submit/delete |
MCP_TRANSPORT | stdio | Set to sse for remote/Docker deployment |
MCP_HOST | 127.0.0.1 | SSE bind host (use 0.0.0.0 for all interfaces) |
MCP_PORT | 3001 | SSE bind port |
docker build -t mcp-search-console .
docker run \
-e MCP_TRANSPORT=sse \
-e MCP_HOST=0.0.0.0 \
-e MCP_PORT=3001 \
-e GSC_ACCOUNTS_CONFIG=/config/accounts.json \
-v /path/to/config:/config \
-p 3001:3001 \
mcp-search-console
Your MCP client connects to http://your-server:3001/sse.
MIT
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.