Skip to main content
Glama
sarahpark

Google Search Console MCP Server

by sarahpark

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 AI agents to access Google Search Console search performance and index health data, including clicks, impressions, rankings, URL inspection, and sitemap management.
      9 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Provides read-only access to Google Search Console data, allowing AI assistants to query site performance metrics like keywords, clicks, and rankings using natural language. It supports listing verified properties, querying search analytics with dimension filters, and retrieving sitemap information.
      3
      1
      MIT
    • 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
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to query and analyze Google Search Console data, including search analytics, URL inspection, sitemaps, and property verification, and to perform actions like submitting sitemaps and adding properties through natural language.
      19
      6 npm
      MIT
    • 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
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to query and manage Google Search Console data, including search analytics, URL indexing status, and sitemap management, for SEO and LLMO analysis directly from a conversation.
      15
      4,321 npm
      MIT

    TDQS

    A3.6/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct Google Search Console resource and action: site listing, analytics queries, URL inspection, and sitemap listing. There is no overlap in purpose, so an agent can easily select the right tool for a given task.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern in lowercase snake_case (list_sites, search_analytics, inspect_url, list_sitemaps). The naming is predictable and uniform across the entire set.

    Tool Count4/5

    Four tools is a reasonable size for a focused read-only Search Console server. It is slightly lean but each tool covers a distinct core function, and the count feels appropriate for the apparent scope.

    Completeness3/5

    The server covers primary read operations but misses common management actions like submitting or deleting sitemaps. Analytics and URL inspection are present, but there is no sitemap submission or deeper detail (e.g., sitemap errors), leaving notable gaps for workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow