Search Console MCP

What saurabhsharma2u/search-console-mcp does

saurabhsharma2u/search-console-mcp gives MCP-compatible agents access to four Google and Microsoft web-data systems: Google Search Console, Bing Webmaster Tools, Google Analytics 4, and Google AdSense. It combines account and property operations with server-side analysis, so an agent can query performance data, inspect URLs, submit sitemaps, assess site health, and review advertising metrics through MCP tools.

The server supports both operational tasks and investigative workflows. Examples include finding pages behind a traffic decline, identifying queries ranking near the first page, comparing Google with Bing, checking structured data, and connecting search traffic changes with AdSense earnings or RPM.

How it works

Run the server through the standard MCP stdio transport using the search-console-mcp command. The recommended initial command is npx search-console-mcp setup; setup opens a browser for Google authorization and stores credentials securely. After adding the server command to an MCP client configuration, call get_started first to receive the active platforms and suggested workflows.

Queries can target Google, Bing, GA4, or multiple engines. The server includes a parallel engine: "all" mode for multi-engine requests and retains backward compatibility with older tool names through a fallback router. Google Search Console mutation operations, including sitemap submission and deletion, require an explicit webmasters write scope; read access remains the default during setup. AdSense uses a separate OAuth read-only scope and supports user OAuth rather than service-account authentication.

Setup and configuration

Install and initialize the server with:

npx search-console-mcp setup

Then add an MCP server entry such as:

{
  "mcpServers": {
    "search-console": {
      "command": "npx",
      "args": ["search-console-mcp"]
    }
  }
}

Restart the MCP client after saving the configuration. AdSense is enabled separately with setup --engine=adsense, and requires approval of the adsense.readonly OAuth scope. The server also provides an MCPB bundle for one-click Claude Desktop installation. SSE mode is available but deprecated; when used, it binds to the loopback address by default and requires a bearer token.

Tools and capabilities

• Discover and manage verified properties across Search Console, Bing Webmaster Tools, and GA4 with sites_list and sites_manage.
• Manage Search Console service accounts and site permissions through accounts_manage.
• List, submit, and remove XML sitemaps with the sitemaps_* tools.
• Query search performance by queries, pages, countries, devices, and search appearances using analytics_query.
• Compare periods, attribute traffic drops, and detect anomalies with analytics_compare and analytics_anomalies.
• Query GA4 e-commerce, realtime, user-behavior, and conversion-funnel metrics with analytics_advanced.
• Review AdSense earnings, impressions, clicks, CTR, RPM, payments, and alerts.
• Inspect indexing, canonical, and crawl status; analyze PageSpeed and Core Web Vitals; and submit URLs through Google, Bing, or IndexNow.
• Run SEO audits, keyword research, structured-data validation, site-health checks, and Google-versus-Bing comparisons.
• Detect likely conversational or generative-AI-related queries using heuristic patterns in regular search-query data. These results are estimates rather than official citation reports.
• Use diagnostics to troubleshoot connectivity, authentication, and empty-result problems.

Limitations and notes

Generative-AI query insights are heuristic and can undercount relevant queries because Google and Bing do not expose official generative-AI citation data through their public APIs. AdSense requires separate authorization and does not accept service-account authentication. SSE transport is deprecated in favor of stdio. Property resolution distinguishes property types and paths; genuinely ambiguous requests fail instead of selecting a property arbitrarily.