Skip to main content
Glama
getmcpads-com

google-search-console-mcp-server

by getmcpads-com
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to google-search-console-mcp-server

No user-submitted related servers found.

    Related Servers

    • gsc-mcp

      rachel-growthlever
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides read-only access to Google Search Console data, including search analytics, sitemap status, and URL inspection, for MCP clients like Claude.
      5 npm
      MIT

    • SearchConsole.ai

      AndreyAzimov
      A
      license
      Not graded
      quality
      B
      maintenance
      Read-only MCP server for Google Search Console data, enabling search analytics, URL inspection, indexing diagnostics, and sitemap management through MCP clients.
      7 npm
      MIT
    • io.scalably/gsc-mcp by scalably-io

      io.scalably/gsc-mcpofficial

      scalably-io
      A
      license
      A
      quality
      A
      maintenance
      Enables read-only access to Google Search Console data, including properties, Search Analytics with filters and auto-pagination, sitemaps, and URL inspection with batch support and throttling.
      5
      MIT

    • mcp-server-google-search

      thein-art
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables interaction with Google Search Console via MCP, offering search analytics, performance summaries, URL inspection, sitemap management, and property listing for SEO workflows.
      105 npm
      1
      MIT

    • @lomi./gsc-mcp

      lomiafrica
      A
      license
      B
      quality
      B
      maintenance
      Enables Google Search Console data queries via MCP, including search analytics, performance comparisons, URL inspection, and sitemap management.
      12
      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 20 tools

    Disambiguation2/5

    Several tools cluster around the same underlying resources with fuzzy boundaries, such as gsc_get_sitemap, gsc_get_sitemap_health, and gsc_list_sitemaps, or gsc_monitor_indexation_freshness and gsc_get_data_freshness. Search Analytics is also fragmented across gsc_query_search_analytics, gsc_compare_search_types, gsc_find_losses_gains, gsc_cluster_queries, and gsc_detect_cannibalization, making tool selection ambiguous.

    Naming Consistency4/5

    All tools consistently use a gsc_ prefix with snake_case verb_noun names, which is a clear and predictable pattern. Minor deviations exist in verb choices—monitor, detect, track, plan, and cluster feel less uniform than simple list/get/query verbs—but the overall convention is consistent.

    Tool Count3/5

    20 tools is on the heavy side for a Google Search Console read-only server, especially since many are specialized wrappers around Search Analytics and URL Inspection that could be consolidated. The count is not unreasonable for the domain, but it feels somewhat over-fragmented.

    Completeness4/5

    The server covers the main read-only Google Search Console surfaces: properties, sitemaps, Search Analytics, and URL Inspection, with no obvious dead ends. It lacks write operations like submitting or removing sitemaps, but the tool set appears intentionally read-only, so this is a minor gap rather than a critical one.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources