GSC MCP Server
Related Servers
Alternatives to GSC MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables interaction with Google Search Console via MCP, offering search analytics, performance summaries, URL inspection, sitemap management, and property listing for SEO workflows.105 npm1MIT
- AlicenseBqualityBmaintenanceEnables Google Search Console data queries via MCP, including search analytics, performance comparisons, URL inspection, and sitemap management.12MIT
- AlicenseNot gradedqualityDmaintenanceConnects Google Search Console to MCP clients to query search analytics, manage sitemaps, and perform URL inspections. It enables users to identify SEO opportunities and generate performance reports through natural language interactions.52 npm4MIT
- AlicenseNot gradedqualityCmaintenanceProvides Google Search Console tools for listing sites, querying search analytics, managing sitemaps, and inspecting URL index status via MCP.5 npmMIT
- AlicenseNot gradedqualityAmaintenanceMCP server for Google Search Console API that enables querying search analytics, managing sites, inspecting URLs, and supporting domain delegation via service accounts.MIT
- FlicenseNot gradedqualityDmaintenanceEnables managing multiple Google Search Console accounts through a single MCP server, providing tools for search analytics, quick win detection, period comparison, URL inspection and indexing, and sitemap management.-
TDQS
Scored across 20 tools
Several tools have overlapping purposes, such as get_sitemaps, list_sitemaps_enhanced, and manage_sitemaps (with 'list' action), which all list sitemaps. Similarly, get_search_analytics, get_advanced_search_analytics, and get_performance_overview all retrieve performance data with varying levels of detail. The distinctions are often subtle and may confuse an agent selecting the appropriate tool.
Most tool names follow a verb_noun pattern (e.g., list_properties, add_site, get_search_analytics, submit_sitemap). Minor inconsistencies exist, such as 'batch_url_inspection' being a noun phrase rather than a verb-led name, and 'reauthenticate' being a single verb. Overall, the naming is fairly consistent and predictable.
With 20 tools, the server is on the heavier side, and the redundancy among sitemap and analytics tools inflates the count. The scope covers multiple subdomains (properties, analytics, sitemaps, inspection, auth), so a count near 20 is not wildly excessive, but it could be streamlined to around 12-15 tools without losing functionality.
The tool set provides good coverage of the Google Search Console API: property lifecycle (list, add, delete, details), analytics (basic, advanced, comparison, page-specific), sitemap management (list, details, submit, delete, and a combined tool), and URL inspection (single, batch, indexing issues). Minor gaps exist, such as no explicit tool for testing robots.txt, but the core workflows are well represented.