Skip to main content
Glama
Mrshahidali420

Google Search Console MCP Server

Related Servers

Alternatives to Google Search Console MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      An MCP server integrating Google Analytics 4, Search Console, and Indexing API, enabling AI agents to run reports, inspect URLs, manage properties, and request indexing.
      16
      73
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      MCP server for the Google Search Console API. Enables search performance analytics, sitemap management, URL index inspection, and property management through natural language.
      12
      71
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      MCP server for querying Google Search Console data — search analytics, URL inspection, sitemap monitoring, and more — read-only tools for any MCP-compatible AI client.
      7
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      This MCP server provides tools to query Google Search Console data, including search analytics, URL inspection, sitemap management, and site listing. It enables AI assistants to retrieve SEO performance metrics and manage sitemaps through natural language.
      5
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP 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.
      62
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      MCP server for Google Search Console, enabling querying search performance, listing properties, and inspecting URL indexing status from MCP-compatible clients.
      4
      14
      1
      MIT

    TDQS

    A4.1/5.0

    Scored across 15 tools

    Disambiguation4/5

    Each tool has a clearly defined primary purpose, and the descriptions are thorough in distinguishing them. However, a few pairs (gsc_check_status vs gsc_find_unindexed, gsc_request_indexing vs gsc_start_indexing_job) operate in the same domain and could be confused without careful reading.

    Naming Consistency3/5

    All tools share the gsc_ prefix and snake_case, which provides a consistent feel, but the structural pattern is mixed. Most use verb_noun (list_sites, check_status, submit_sitemaps), while several are plain nouns (doctor, quota, performance, setup, audit) or noun_noun (job_status). This is readable but not fully consistent.

    Tool Count4/5

    At 15 tools, the server is on the higher end of the ideal range, but the broad domain of Search Console management justifies it. Each tool covers a distinct aspect (setup, properties, inspection, analytics, quota, sitemaps, indexing jobs), and none feel redundant or unnecessary.

    Completeness4/5

    The tool set covers the core Search Console workflows: setup, property listing, index status inspection, performance analytics, quota estimation, sitemap submission, and indexing jobs. Minor gaps exist, such as no standalone tool to list or remove sitemaps and no property creation/removal, but agents can work around these limitations.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive