What is Search Console MCP?
Search Console MCP is an MCP server for accessing search, analytics and advertising data through AI agents and automation. It connects Google Search Console, Bing Webmaster Tools, Google Analytics 4 and Google AdSense through a shared tool interface. Its analysis tools cover traffic changes, keyword cannibalization, ranking opportunities and revenue attribution.
The server runs through an npm-based setup and connects to compatible MCP clients such as Claude Desktop and Cursor. Registered tools are also available through a command-line interface with JSON, CSV and table output. Authentication depends on the connected service, using OAuth, service accounts or an API key. Headless deployment is documented, including transferring an AdSense authorization grant to a server.
Key capabilities
- Unified analytics Queries search and website analytics across connected services and compares performance between periods or engines.
- SEO diagnostics Provides audits for ranking opportunities, keyword cannibalization, traffic anomalies and brand versus non-brand performance.
- Revenue reporting Retrieves AdSense earnings reports, payments and account alerts using separately authorized read-only access.
- Site operations Lists properties and sitemaps, inspects URLs, and exposes sitemap and indexing submission tools.
- Account management Supports multiple accounts and resolves the account associated with a requested site.
- CLI access Runs registered MCP tools directly from the command line and formats results as JSON, CSV or tables.
Where Search Console MCP fits
The server fits SEO investigation and reporting workflows where an AI assistant needs access to search performance, analytics and advertising data without manual exports. Teams can use it to investigate traffic declines, compare search engines or identify pages with visibility but weak click-through performance. Its CLI also supports scripted analysis outside an interactive assistant.
Before deployment, teams should verify property access, account resolution and the authentication method required by each service. Setup is read-only by default, while Google Search Console mutation tools require explicit write authorization. The default stdio transport is preferred; the documented SSE transport is deprecated. Generative-AI query insights use heuristics over ordinary search query data, not official citation data from Google or Bing.
Reviews of Search Console MCP
Be the first to share your experience with Search Console MCP.
Write a review
Loading review form…
Alternatives to Search Console MCP
EngramEngram is a local persistent memory system for AI coding agents, storing decisions and session summaries in SQLite and exposed through MCP and an HTTP API.
Firecrawl MCP ServerA Firecrawl connector for web search, page extraction, site mapping and bounded crawling with Markdown or structured results.