MCP server for Google Search Console, Bing Webmaster Tools, and Google Analytics 4
Most developer tooling work still happens through a UI a human drives. Search Console MCP MCP server moves it into the conversation instead. MCP server for Google Search Console, Bing Webmaster Tools, and Google Analytics 4.
SEO data lives in three different silos. Answering one question — "did my traffic drop because of a ranking loss or a UX issue?" — usually means logging into three dashboards, exporting three CSVs, and doing VLOOKUPs by hand.
Installation goes through your MCP client rather than a global install: point it at search-console-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
The server publishes 14 tools. What each one is for:
sites_list — engine: "all" \sites_manage — action: "add" \accounts_manage — action: "list" \sitemaps_list — siteUrl, feedUrl, enginesitemaps_submit — siteUrl, feedUrl, enginesitemaps_delete — siteUrl, feedUrl, engineanalytics_query — siteUrl, engine, dimensions, metricsanalytics_compare — mode: "period_over_period" \analytics_anomalies — siteUrl, thresholdinspection_inspect — siteUrl, urls, enginepagespeed_analyze — url, strategy, cwvOnlyindexing_submit — urls, method: "standard" \Configuration is passed through the environment: BING_API_KEY, GOOGLE_APPLICATION_CREDENTIALS. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Search Console MCP's toolset — sites_list, sites_manage, accounts_manage and 11 more — is a fair guide to whether it matches your workflow. It is maintained by saurabhsharma2u; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Search Console MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| sites_list | engine: "all" \ |
| sites_manage | action: "add" \ |
| accounts_manage | action: "list" \ |
| sitemaps_list | siteUrl, feedUrl, engine |
| sitemaps_submit | siteUrl, feedUrl, engine |
| sitemaps_delete | siteUrl, feedUrl, engine |
| analytics_query | siteUrl, engine, dimensions, metrics |
| analytics_compare | mode: "period_over_period" \ |
| analytics_anomalies | siteUrl, threshold |
| inspection_inspect | siteUrl, urls, engine |
| pagespeed_analyze | url, strategy, cwvOnly |
| indexing_submit | urls, method: "standard" \ |
| indexing_status | siteUrl, type: "quota" \ |
| seo_audit | type: "quick_wins" \ |
{
"mcpServers": {
"search-console": {
"command": "npx",
"args": ["-y", "search-console-mcp"],
"env": {
"BING_API_KEY": "your-value",
"GOOGLE_APPLICATION_CREDENTIALS": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| BING_API_KEY | Credential the server authenticates with. | Yes |
| GOOGLE_APPLICATION_CREDENTIALS | Configuration value read at startup. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.