Skip to main content
Glama
woosteragency

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 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
    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects AI assistants to Google Search Console so users can query search analytics, compare performance periods, inspect URL indexing status, and manage sitemaps and properties through natural language.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to query Google Search Console data—properties, search analytics, URL inspection, and sitemaps—through natural language via a self-hosted MCP endpoint.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Connects 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.
      82 npm
      4
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A self-hosted connector that exposes Search Analytics, URL Inspection, sitemap listing, and property discovery tools to MCP-capable AI assistants. It lets users query clicks, impressions, CTR, position, indexing status, and sitemap processing in natural language using their own Google account, with read-only OAuth access and no service account setup.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to analyze Google Search Console SEO data through natural language, including search analytics, URL inspection, sitemap management, and property management.
      21
      MIT

    TDQS

    A3.7/5.0

    Scored across 21 tools

    Disambiguation3/5

    Search analytics tools are mostly differentiated, but sitemap operations overlap heavily: get_sitemaps, list_sitemaps_enhanced, get_sitemap_details, submit_sitemap, delete_sitemap, and manage_sitemaps duplicate each other. URL inspection tools also overlap (inspect_url_enhanced, batch_url_inspection, check_indexing_issues), creating meaningful misselection risk.

    Naming Consistency4/5

    Nearly all tools use snake_case with a verb_noun pattern such as list_properties, get_search_analytics, submit_sitemap. Minor deviations like batch_url_inspection (noun phrase) and manage_sitemaps (generic verb) keep it from being fully consistent.

    Tool Count3/5

    21 tools is on the heavy side for the Search Console surface, especially since sitemap actions are offered both individually and through the all-in-one manage_sitemaps tool. The count is not extreme, but redundancy and meta tools make the set feel bloated.

    Completeness4/5

    Core GSC workflows are covered: properties, search analytics (basic/advanced/compare/page-level), URL inspection, indexing checks, and sitemap lifecycle. Minor gaps remain around property verification/update and explicit indexing-request actions, but agents can work around them.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues