Skip to main content
Glama
shutovdef-dotcom

Google Search Console MCP Server

by shutovdef-dotcom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Google Search Console MCP Server

No user-submitted related servers found.

    Related Servers

    • Google Search Console (GSC)

      amirjahfar1
      A
      license
      A
      quality
      C
      maintenance
      Connects Google Search Console to AI assistants, enabling natural language queries for SEO data, indexing audits, sitemap management, and full site audits.
      20
      MIT

    • Google Search Console MCP

      justingluska
      A
      license
      A
      quality
      D
      maintenance
      Connects AI assistants to Google Search Console data for SEO analysis, including search analytics, URL inspection, sitemaps, indexing, and opportunity detection.
      17
      MIT

    • mcp-search-console

      ledokter
      A
      license
      A
      quality
      C
      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

    • Google Search Console MCP

      appscaptain
      A
      license
      A
      quality
      C
      maintenance
      Connects Google Search Console to AI assistants, enabling natural language analysis of SEO data. Provides read-only tools for properties, search analytics, URL inspection, and sitemaps.
      15
      MIT

    • Google Search Console MCP

      hablapro
      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
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 32 tools

    Disambiguation3/5

    Many tools have overlapping purposes (e.g., get_sitemaps, list_sitemaps_enhanced, manage_sitemaps all can list sitemaps; get_search_analytics vs get_advanced_search_analytics). Detailed descriptions help distinguish, but the redundancy creates ambiguity.

    Naming Consistency2/5

    Naming is inconsistent: some use verb_noun (list_properties, get_site_details), others use gsc_ prefix for diagnostics, but verbs vary (list vs get, build vs gsc_build). No single pattern is followed across all tools.

    Tool Count2/5

    32 tools is excessive for GSC's limited API surface. Many tools are near-duplicates or highly specialized diagnostics that could be combined, making the toolset feel bloated.

    Completeness4/5

    Covers properties, sitemaps, URL inspection, search analytics, performance overview, and advanced diagnostics. Minor gaps like crawl errors or detailed index coverage, but overall a thorough surface for GSC.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources