Search Console MCP MCP Server
io.github.saurabhsharma2u/search-console-mcp
Unified SEO intelligence from Google Search Console, Bing, and GA4 for AI agents—no more manual exports.
What is the Search Console MCP MCP server?
Search Console MCP is an MCP server that unifies Google Search Console, Bing Webmaster Tools, and Google Analytics 4 data into a single context for AI agents. It provides deterministic SEO analysis—including anomaly detection, opportunity scoring, and cannibalization detection—before data reaches your agent, eliminating manual spreadsheet work.
Search Console MCP eliminates the need to log into three separate dashboards and manually export CSVs. It exposes 17 fluent domain tools that let your AI agent query search rankings, analytics, indexing status, Core Web Vitals, and run automated SEO audits across Google, Bing, and GA4 simultaneously. Perfect for diagnosing traffic drops, finding quick-win keywords, detecting cannibalization, and managing multi-account SEO workflows.
How to install Search Console MCP
Copy-paste configuration for popular MCP clients.
GOOGLE_APPLICATION_CREDENTIALSsecretGoogle Cloud Service Account JSON key content or path. Optional if OAuth setup is used.
BING_API_KEYsecretBing API Key
PAGESPEED_API_KEYsecretPageSpeed Insights API key for higher quota (25k/day). Optional.
Tools & capabilities
Tools this server exposes to the agent.
sites_list— Lists verified sites across search engines (Google, Bing, or both in parallel)sites_manage— Adds or removes site properties from search enginesaccounts_manage— Configures and manages multi-account profilessitemaps_list— Fetches sitemap status and indexing statesitemaps_submit— Submits sitemaps to Google Search Console and Bingsitemaps_delete— Removes sitemaps from search enginesanalytics_query— Multi-engine search and GA4 analytics queries with custom dimensions and metricsanalytics_compare— Analyzes period-over-period deltas, trend shifts, and drop attributionanalytics_anomalies— Statistical detection of traffic spikes and dropsinspection_inspect— Google URL inspection and Bing URL info for indexing statuspagespeed_analyze— Core Web Vitals and PageSpeed Insights auditsindexing_submit— Instantly indexes URLs via IndexNow, Google API, or Bing APIindexing_status— Checks remaining indexing quota and URL indexing statusseo_audit— Comprehensive automated SEO audits: quick wins, striking distance, cannibalization, low-hanging fruit, lost queries, and brand vs non-brand analysisseo_keywords_research— Keyword volume stats and related keyword researchsite_health_check— One-shot site performance and technical audit with crawl issue detectioncompare_engines— Side-by-side Google vs Bing performance breakdown
Use cases
- Diagnose traffic drops by identifying when they started and which pages are responsible
- Find keyword opportunities in positions 8–15 with high impressions for quick ranking wins
- Detect keyword cannibalization where multiple pages compete for the same query
- Run automated SEO audits on top pages to correlate search visibility with CTR performance
- Compare Google vs Bing performance and identify where each engine is winning
Search Console MCP MCP server FAQ
It's an MCP server that unifies Google Search Console, Bing Webmaster Tools, and GA4 into one context, letting your AI agent run SEO queries, audits, and analytics without manual CSV exports.
Yes. The server itself is MIT-licensed and free. You need free API keys/OAuth access to Google Search Console, Bing Webmaster Tools, and GA4—all free to set up.
Run `npx search-console-mcp setup` to authorize your Google account, then add the server to your MCP client config with `"command": "npx", "args": ["search-console-mcp"]`. Alternatively, download the `.mcpb` bundle and drag it into Claude Desktop.
Google Search Console and GA4 use OAuth (browser-based setup). Bing requires an API key from Bing Webmaster Tools. Credentials are stored securely in your OS keychain with AES-256-GCM encryption as fallback.
Yes. The server auto-resolves which account owns a site when you query it. Manage accounts via `npx search-console-mcp accounts list/add-site/remove`.
Yes. Use `npx search-console-mcp run <tool-name>` with parameters to execute any tool and output results as JSON, CSV, or ASCII table.
README (reference)
Source of truth, from the repository.
🔍 Search Console MCP
Google Search Console + Bing Webmaster Tools + GA4 — in one context window.
Stop exporting CSVs. Start asking your AI agent questions.
<br/>📚 Docs · Quick Start · Tools · Backward Compatibility · Security
</div>⚡ What's New in v2.0.2
- 📦 MCPB One-Click Bundle Support (
.mcpb): Drag and drop bundle installation for Claude Desktop. - ⚡ Parallel Fetch Engine (
engine: "all"): Multi-engine queries fetch Google, Bing, and GA4 concurrently with 50%+ lower latency. - 🔄 100% Backward Compatibility: All ~96 legacy tool names continue to work seamlessly via our fallback router. Read Backward Compatibility Guide →
Why this exists
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.
Search Console MCP puts GSC, Bing, and GA4 behind one set of tools your AI agent can call directly, and does the SEO math (cannibalization, anomaly detection, opportunity scoring) before the data ever reaches your context window — so your agent gets insights, not spreadsheets.
| Before | After | |
|---|---|---|
| Data | 3 dashboards, manual exports | 1 unified context |
| Analysis | Manual VLOOKUPs & pivot tables | Deterministic SEO math, done server-side |
| Accounts | Constant re-login | 20+ accounts, auto-resolved per site |
| Insight | Raw rows, agent guesses | Curated signals (opportunity scores, anomalies) |
⚡ Quick Start
npx search-console-mcp setup
This opens your browser, authorizes your Google account, and stores your credentials securely (see Security). Then add it to your MCP client config (Claude Desktop, Cursor, Antigravity, etc.):
{
"mcpServers": {
"search-console": {
"command": "npx",
"args": ["search-console-mcp"]
}
}
}
Restart your client — and try one of the prompts below.
💬 Try it
Paste these straight into your agent:
"My traffic dropped this week vs. last. Find exactly when it started and which pages are responsible."
"Find keywords for example.com ranking positions 8–15 with 1,000+ impressions — my best quick wins."
"Check for keyword cannibalization — are two of my pages competing for the same query?"
<details> <summary>More example prompts</summary>"Run
seo_auditon my top pages: which have high search visibility but poor CTR?"
- "Run a full SEO health check (
site_health_check), segmented by Brand vs Non-Brand." - "Fetch my top 5 pages by impressions and run
pagespeed_analyze— any correlation with declining rankings?" - "Compare Google vs Bing performance for the last 30 days (
compare_engines) — where is Bing winning?" - "Submit my latest URLs to Google and IndexNow using
indexing_submitwithmethod: "index_now"."
🔌 Connect your accounts
| Platform | Method | Setup |
|---|---|---|
| Google Search Console | OAuth (recommended) | npx search-console-mcp setup |
| Google Search Console | Service Account | Set GOOGLE_APPLICATION_CREDENTIALS — details |
| Bing Webmaster Tools | API Key | export BING_API_KEY="..." — get a key |
| Google Analytics 4 | Service Account | npx search-console-mcp setup --engine=ga4 |
Manage everything from the CLI:
npx search-console-mcp accounts list
npx search-console-mcp accounts add-site --account=you@company.com --site=example.com
npx search-console-mcp accounts remove --account=you@company.com
When your agent queries a site, the server auto-resolves which account owns it — no manual switching. Multi-account docs →
🖥️ Run tools from the CLI
Search Console MCP also exposes registered MCP tools as direct CLI commands. Use the run subcommand to list tools, inspect tool-specific arguments, and print results as JSON, CSV, or an ASCII table:
# List registered tools
npx search-console-mcp run --help
# Show options for one tool
npx search-console-mcp run analytics_query --help
# Run an SEO audit with JSON output
npx search-console-mcp run seo_audit --siteUrl=https://example.com --type=quick_wins
# Print array results as CSV or a table
npx search-console-mcp run analytics_query --siteUrl=https://example.com --startDate=2026-06-01 --endDate=2026-06-30 --dimensions=date,query --format=csv
npx search-console-mcp run sites_list --engine=all --format=table
<details>
<summary id="service-account-advanced">Service Account setup (for servers/automation)</summary>
- Create a service account in the Google Cloud Console
- Generate a JSON key
- Add the service account email as a user in Search Console with "Full" or "Restricted" access
export GOOGLE_APPLICATION_CREDENTIALS="/path/to/key.json"
🛠 Tools (Fluent Domain Architecture)
Search Console MCP v2.0 features 7 Fluent Domain Tools that handle all SEO, Analytics, Inspection, and Indexing operations cleanly:
| Fluent Tool | Parameters / Actions | Description |
|---|---|---|
sites_list | engine: "all" | "google" | "bing" | Lists verified sites across search engines in parallel |
sites_manage | action: "add" | "delete", siteUrl, engine | Adds or removes site properties |
accounts_manage | action: "list" | "add_site" | "remove" | Configures multi-account profiles |
sitemaps_list | siteUrl, feedUrl, engine | Fetches sitemap status and indexing state |
sitemaps_submit | siteUrl, feedUrl, engine | Submits sitemaps to GSC & Bing |
sitemaps_delete | siteUrl, feedUrl, engine | Removes sitemaps |
analytics_query | siteUrl, engine, dimensions, metrics | Multi-engine search & GA4 analytics query |
analytics_compare | mode: "period_over_period" | "trends" | "drop_attribution" | Analyzes period deltas, trend shifts, and drop causes |
analytics_anomalies | siteUrl, threshold | Statistical detection of traffic spikes/drops |
inspection_inspect | siteUrl, urls, engine | Google URL inspection & Bing URL info |
pagespeed_analyze | url, strategy, cwvOnly | Core Web Vitals and PageSpeed Insights audits |
indexing_submit | urls, method: "standard" | "index_now" | "remove" | Instantly indexes URLs via IndexNow or Google/Bing API |
indexing_status | siteUrl, type: "quota" | "status" | Checks remaining indexing quota & URL status |
seo_audit | type: "quick_wins" | "striking_distance" | "cannibalization" | "low_hanging_fruit" | "lost_queries" | "recommendations" | "brand_vs_nonbrand" | Comprehensive automated SEO audits |
seo_keywords_research | keywords, type: "stats" | "related" | "traffic" | Keyword volumes and related keyword stats |
site_health_check | siteUrl, level: "summary" | "full" | "crawl_issues" | One-shot site performance & technical audit |
compare_engines | siteUrl | Side-by-side Google vs Bing performance breakdown |
All legacy tool names (bing_sites_list, seo_quick_wins, sitemaps_get, bing_index_now, indexing_submit_url, opportunity_matrix, etc.) continue to work transparently via our fallback router.
Read our complete Backward Compatibility & Migration Guide →
</details>🔒 Security
- OS keychain first — tokens stored in macOS Keychain, Windows Credential Manager, or Linux Secret Service
- AES-256-GCM fallback — encrypted with a key derived from your machine's hardware ID; a stolen file is useless on another device
- Minimal storage — only
refresh_tokenandexpiry_dateare persisted, atmode 600 - Silent refresh — tokens renew automatically in the background
License
MIT · Contributing guide · Backward Compatibility Guide
<div align="center">If this saves you a spreadsheet, consider ⭐ starring the repo.
</div>Related MCP servers

io.github.saurav61091/mcp-openapi-runner
Turn any OpenAPI 3.x spec into callable MCP tools for Claude. No custom integration code needed.

io.github.savecharlie/almanac
Verified ephemeris & WMM2025 geomagnetic compute: the physical numbers LLMs hallucinate, done right.

io.github.savecharlie/touchstone
Verifiable text/code/measurement tools for agents, each reproducing a named authority.
Connect any API to LLMs through MCP with automatic Postman collection conversion and JSON configuration.

io.github.saviodamato/agentrank-mcp
Find real, verifiable businesses with provenance and source URLs - for AI agents.
Primary-source commodities data for AI agents — EIA, FRED, CFTC, USDA, USGS via x402 on Base.
