Google Search Console MCP Server
Related Servers
Alternatives to Google Search Console MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables natural-language, read-only analysis of your own Google Search Console and Google Analytics 4 data, including search performance, engagement, sitemap health, ranking opportunities, and deterministic SEO audits through MCP clients like ChatGPT.MIT
- AlicenseNot gradedqualityCmaintenanceEnables SEO teams to query GA4 and Search Console data in plain language through a read-only MCP connector, with a client registry and automatic property discovery.68 npmMIT
- AlicenseAqualityAmaintenanceEnables local, read-only access to Google Search Console data, allowing users to query site performance, identify ranking opportunities, inspect URL indexing, and review sitemap status through MCP clients.8MIT
- AlicenseNot gradedqualityCmaintenanceEnables natural-language querying of Google Search Console data, including search analytics, site properties, URL inspection, and sitemap status, through MCP-compatible clients like ChatGPT and Claude.MIT
- AlicenseBqualityBmaintenanceMCP server providing 32 tools for Google Search Console and Google Analytics 4, enabling search analytics, URL inspection, indexing, and cross-platform analysis via natural language.4311MIT
- AlicenseAqualityBmaintenanceEnables Claude and other MCP clients to read Google Search Console and Bing Webmaster Tools data, analyze query/page performance, compare periods, inspect indexing and canonical status, and retrieve sitemap and keyword statistics.23MIT
TDQS
Scored across 37 tools
Most tools target distinct Search Console resources or analytics views, with clear boundaries such as single vs. batch URL inspection and API vs. local history. A few boundaries blur around the general-purpose query_search_analytics tool versus specialized analytics tools like performance_overview, compare_periods, and history_query, but the descriptions help disambiguate.
All tool names use snake_case consistently, with no camelCase or mixed styles. Many names are noun/report phrases rather than strict verb_noun patterns, but prefixes like history_, inspect_url(s), and sitemap_ are used predictably.
37 tools is well above a practical scoped set and risks overwhelming an agent, even for a feature-rich domain like Search Console. Many specialized analytics and history tools could be consolidated or surfaced as optional modes rather than separate top-level tools.
The surface covers properties, sitemaps, URL inspection, search analytics, advanced query/page analytics, variant handling, local history sync/query, and operational checks like capabilities and quota. No obvious lifecycle or CRUD gaps exist for the stated Google Search Console purpose.