Search Console MCP

🔍 Search Console MCP

Google Search Console + Bing Webmaster Tools + GA4 + AdSense — in one context window.

Stop exporting CSVs. Start asking your AI agent questions about your site's traffic, rankings, and revenue.

📚 Docs · Quick Start · Tools · Backward Compatibility · Security

⚡ What's New in v2.1.4

• 🎯 Correct-property resolution (`#110`): Accounts with multiple verified properties sharing one hostname (locale subfolders like /en-gb/ + /de-de/, the root property, and the sc-domain: property) could get analytics data silently returned for the wrong property — whichever colliding property the resolver happened to touch first. Resolution is now exact by property type and path; bare-domain queries rank deterministically (sc-domain: › root), and truly ambiguous requests fail with the list of matching properties instead of guessing. *With thanks to Alcip for the outstanding root-cause analysis in #110.*
• 🔐 Explicit write authorization for GSC mutation tools (`#113`): sitemaps_submit, sitemaps_delete and site-management calls now require an explicit webmasters write scope, offered as an inline re-authorization flow in the CLI when a tool first needs it. The server stays read-only by default at setup; you opt into write capabilities explicitly. *Credit to chase-weiser88 for surfacing the missing write scope in #84.*
• 🛡️ SSE transport secured & deprecated (`#114`): SSE mode now binds to 127.0.0.1 by default (--host=/MCP_HTTP_HOST to override), requires a bearer token (--token=/MCP_HTTP_TOKEN, auto-generated if unset), never sends wildcard CORS, and rejects forged non-loopback Host headers (DNS-rebinding guard). SSE mode is deprecated and will be removed in the next release — prefer the default stdio transport.
• 🪲 `find_quick_wins` prompt typing (`#112`): min_impressions was declared as a number, but MCP clients must send prompt arguments as strings — so every use errored with expected number, received string. It is now string-typed and coerced internally (1000 default preserved).

What's New in v2.1.2

• 🤖 GenAI Query Insights (`genai_query_insights`): Surfaces likely generative-AI / AI-Mode / conversational "fanout" queries across Google and Bing. This is custom heuristic logic — no official API is provided by Google or Bing for GenAI citation data, so it flags prompt verbs, follow-ups, acknowledgements, and conversational phrasing on the regular query data both engines already return. See docs →
• 🪲 `analytics_query` fix: rowLimit is now honored instead of being silently ignored (previously always returned up to 1000 rows); limit remains as a backward-compatible alias.

What's New in v2.1.0

• 💰 Google AdSense Integration: Earnings reports, payments and account alerts via setup --engine=adsense. Enabling AdSense requires you to approve a separate adsense.readonly OAuth scope; your existing GSC, Bing, and GA4 configuration remains unchanged until you opt in.
• 🔐 OAuth-only AdSense auth: The AdSense Management API supports user OAuth only — setup now validates access live and rejects unsupported service-account configs with actionable guidance. Multi-account users get explicit publisher-account selection with full pagination (>100 accounts).
• 📊 `adsense_report` upgrades: Custom startDate/endDate now override preset dateRanges, plus a new orderBy parameter (-ESTIMATED_EARNINGS) for sorted revenue reports.
• 🧪 End-to-end MCP test suite: The built server binary is now tested over stdio and SSE exactly like an MCP host would drive it — handshake, tool schemas, error envelopes, and multi-account resource behavior (11 e2e tests wired into CI).

What's New in v2.0.x

• 💰 Google AdSense Integration: Earnings reports, payments and account alerts via setup --engine=adsense. Enabling AdSense requires you to approve a separate adsense.readonly OAuth scope; your existing GSC, Bing, and GA4 configuration remains unchanged until you opt in.
• 🔐 OAuth-only AdSense auth: The AdSense Management API supports user OAuth only — setup now validates access live and rejects unsupported service-account configs with actionable guidance. Multi-account users get explicit publisher-account selection with full pagination (>100 accounts).
• 📊 `adsense_report` upgrades: Custom startDate/endDate now override preset dateRanges, plus a new orderBy parameter (-ESTIMATED_EARNINGS) for sorted revenue reports.
• 🧪 End-to-end MCP test suite: The built server binary is now tested over stdio and SSE exactly like an MCP host would drive it — handshake, tool schemas, error envelopes, and multi-account resource behavior (11 e2e tests wired into CI).

What's New in v2.0.x

• 📦 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

Site data lives in four different silos. Answering one question — *"did my ad revenue drop because of a traffic dip or a lower RPM?"* — usually means logging into four dashboards, exporting four CSVs, and doing VLOOKUPs by hand.

Search Console MCP puts GSC, Bing, GA4, and AdSense behind one set of tools your AI agent can call directly, and does the analysis (cannibalization, anomaly detection, revenue attribution) *before* the data ever reaches your context window.

⚡ 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?"

"Run `seo_audit` on my top pages: which have high search visibility but poor CTR?"

More example prompts

• *"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_submit with method: "index_now"."*

🔌 Connect your accounts

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 →

Headless servers (Docker, CI, VPS)

AdSense cannot use service accounts, and config files are machine-encrypted — so authorize once on any machine with a browser and transfer the grant:

# 1. On your laptop (after setup --engine=adsense):

npx search-console-mcp adsense-export

2. On the server (prints a ready-to-run command on step 1):

npx search-console-mcp adsense-import --token='...' --publisher-id='accounts/pub-...'

The token is stored encrypted on the server and auto-refreshes — no browser needed again. Setup over SSH also works directly: when no browser is detected, setup prints the authorization URL plus ssh -L 3000:localhost:3000 port-forward instructions instead of failing.

🖥️ 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

Service Account setup (for servers/automation)

1. Create a service account in the Google Cloud Console
2. Generate a JSON key
3. Add the service account email as a user in Search Console with "Full" or "Restricted" access
4. `export GOOGLE_APPLICATION_CREDENTIALS