GSC Maestro MCP Server
Related Servers
Alternatives to GSC Maestro MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables read-only collection and comparison of Google Search Console and Bing Webmaster data, conservative URL protection, content auditing, reviewed-build verification, and private report generation through ten typed tools over stdio.10Apache 2.0
- AlicenseAqualityAmaintenanceConnects AI assistants to a site owner's search performance data, letting them ask in plain language about clicks, queries, pages, indexing and sitemaps and get back structured results. Runs locally with your own credentials, read-only by default, and validates requests up front so the API's silent empty-result and terse-error quirks are caught before they mislead.22109 PyPI8MIT
- AlicenseNot gradedqualityBmaintenanceEnables read-only access to Google Search Console, Bing Webmaster Tools, and PageSpeed Insights, allowing queries for analytics, sites, sitemaps, inspections, crawl issues, and page speed analysis via natural language.1,619 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 gradedqualityBmaintenanceExposes Google Search Console's API as MCP tools for SEO analytics, including up to 25,000-row search analytics, regex filters, quick-win and cannibalization detection, period comparisons, sitemap/site management, and batch URL inspection, accessible over stdio, HTTP/SSE with bearer auth, or Cloudflare Workers.4,423 npmMIT
- AlicenseBqualityDmaintenanceRead-only MCP server for Google Search Console, with browser-based OAuth flow and local token storage, enabling querying search analytics, site lists, and URL inspection.8MIT
TDQS
Scored across 4 tools
The two computational tools (maestro_calculate_ctr, maestro_compare_periods) are clearly distinct, and the two explanatory tools differ in subject matter (demo scope vs. metric definitions). There is mild overlap between maestro_public_capabilities and maestro_explain_search_metrics, since both are descriptive/explanatory with no side effects, but the descriptions make the boundary readable.
All tools share the maestro_ prefix and snake_case naming, which is highly predictable. The only deviation is that three names start with a verb (calculate, compare, explain) while maestro_public_capabilities is a noun phrase, a minor inconsistency.
Four tools is on the thin side but fits a deliberately narrow, credential-free metrics demo: two calculators and two explainers. Each tool earns its place and nothing appears redundant, though the surface leaves little room for variation.
The demo covers CTR calculation and period comparison plus explanatory context, but there is a gap: average position is explained yet no tool computes it, and there is no tool for aggregating or deriving other metrics from supplied clicks/impressions. These are notable but minor omissions given the stated educational scope.