gsc-mcp
Related Servers
Alternatives to gsc-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server for querying Google Search Console data — search analytics, URL inspection, sitemap monitoring, and more — read-only tools for any MCP-compatible AI client.7Apache 2.0
- AlicenseBqualityDmaintenanceProfessional Google Search Console MCP server providing 40+ SEO tools for performance analysis, content decay, CTR opportunities, and more, enabling real search data in clients like Cursor and Claude.4010 npm6MIT
- AlicenseAqualityDmaintenanceGoogle Search Console for Claude, Cursor & any MCP client — one sign-in, 30 seconds, no Google Cloud project. Six read-only tools (search analytics incl. Google Discover, period comparison with computed deltas, batch URL inspection, sitemaps) plus five built-in SEO analyses as slash-commands. Tokens stay on your machine. MIT.693 npm7MIT
- AlicenseNot gradedqualityCmaintenanceSelf-hosted Google Search Console MCP server deployable to Cloudflare Workers, allowing natural language queries of GSC data via ChatGPT, Claude, or any MCP-capable client.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that exposes the Google Search Console API, allowing LLMs to query SEO data, inspect URLs, manage sitemaps, and analyze search performance via natural language.46 npmMIT
- AlicenseNot gradedqualityBmaintenanceSelf-hosted MCP server that exposes Google Search Console tools (list sites, query analytics, inspect URL, list sitemaps) via natural language to AI assistants like ChatGPT and Claude.1MIT
TDQS
Scored across 20 tools
The set includes five specialized query tools (gsc_query_pages, gsc_query_queries, etc.) that all overlap with the generic gsc_search_analytics tool, which supports arbitrary dimensions and filters. Additionally, gsc_top_pages and gsc_top_queries are essentially sorted queries that could also be expressed via gsc_search_analytics. This creates significant ambiguity in tool selection.
Most tools follow a `gsc_verb_noun` snake_case pattern (e.g., list_sites, query_pages, inspect_url). However, `gsc_search_analytics` and `gsc_server_info` deviate from the verb-first convention, and there is minor mixing of verb styles (query vs list vs diagnose). Overall, the pattern is still recognizable and consistent enough.
At 20 tools, the set is on the heavy side but not excessive for a Google Search Console integration covering analytics, sitemaps, sites, and URL inspection. The redundancy among query-related tools makes the count feel somewhat inflated; trimming a few would tighten the surface.
The server covers core Search Console workflows: analytics querying with multiple dimensions and comparisons, sitemap listing/detail, site listing/detail, URL inspection, and common SEO analyses. Gaps exist around sitemap submission/removal and site verification, but these are secondary for an analytics-focused tool.