Skip to main content
Glama
Suganthan-Mohanadasan

Google Search Console MCP Server

Related Servers

Alternatives to Google Search Console MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables natural language analysis of Google Search Console data through Claude, with pre-built tools for quick wins, cannibalization detection, content decay, and more.
      Apache 2.0
    • A
      license
      B
      quality
      C
      maintenance
      Connects Google Search Console with Claude AI to enable SEO professionals to analyze their SEO data through natural language conversations, providing access to property information, search analytics, URL inspection, and sitemap management.
      4,306 PyPI
      1,524
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Connects Google Search Console with Claude AI to analyze SEO data through natural language, enabling search analytics reporting, URL inspection, indexing status checks, sitemap management, and data visualization for SEO professionals.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables querying Google Search Console search analytics (clicks, impressions, CTR, position) with flexible dimensions, inspecting URL indexing and mobile usability, and listing verified properties, all via Claude.
      86 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying Google Search Console data, including search analytics, indexing status, and sitemap management, through natural language conversations with Claude.
      91 npm
      5
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude to access Google Search Console data including search performance, URL indexation, sitemaps, and built-in SEO analysis tools such as trending queries, cannibalization detection, and traffic drop diagnostics.
      91 npm
      11
      MIT

    TDQS

    A3.7/5.0

    Scored across 29 tools

    Disambiguation4/5

    Each tool has a clear analytical target: URL inspection, site snapshot, quick wins, traffic drops, content gaps, cannibalization, image-search variants, etc. The main overlap is among synthesizing tools like check_alerts, content_recommendations, and generate_report, but their descriptions clearly frame them as aggregators. Advanced_search_analytics could duplicate several specialized tools, but it is positioned as the low-level custom query option.

    Naming Consistency3/5

    Tool names are consistently snake_case and readable, and operative actions follow a clear submit_/ist_ pattern. However, most analytical tools use noun phrases like quick_wins, content_gaps, and image_content_decay rather than a uniform verb_noun convention, and compare_web_vs_image stands out as a different verb style.

    Tool Count2/5

    29 tools exceeds the 25-tool threshold, making the surface feel bloated rather than well-scoped. Many tools are near-variants of the same analytical idea (e.g. quick_ins vs image_search_quick_wins, content_decay vs image_content_decay) or are synthesizing tools that could potentially be consolidated.

    Completeness4/5

    The core GSC workflows are covered well: search analytics, URL inspection, indexing submission, sitemap management, and SEO opportunity identification. Minor gaps like sitemap deletion, property listing, and lower-level site management are absent but can be worked around in most agent workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow