Skip to main content
Glama
rohoswagger

Google Search Console MCP

by rohoswagger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Google Search Console MCP

No user-submitted related servers found.

    Related Servers

    • QuerySail: Google Search

      querysail
      A
      license
      Not graded
      quality
      C
      maintenance
      Hosted, read-only Google Search Console MCP server. Search performance by query, page, country, device and date, period comparisons, URL inspection and sitemaps for every property you can access. OAuth sign-in, no Google Cloud project or API key.
      MIT

    • Google Search Console MCP

      oscarcalvo
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables querying Google Search Console data, including search analytics with advanced filtering, quick wins detection, and rich dimensions, through natural language.
      2,444 npm
      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

    • gsc-mcp-server

      Klartika
      A
      license
      A
      quality
      F
      maintenance
      Enables natural language interaction with Google Search Console data, including property management, search analytics, URL inspection, and sitemap management via MCP.
      21
      MIT

    • gsc-mcp

      ajmalaksar25
      A
      license
      A
      quality
      D
      maintenance
      Turns Google Search Console into an SEO copilot by enabling natural language queries for search analytics, URL inspection, sitemap management, and opportunity discovery.
      16
      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.4/5.0

    Scored across 12 tools

    Disambiguation3/5

    Most tools are clearly distinct (sites, inspection, sitemap CRUD), but there is meaningful overlap among gsc_search_analytics, gsc_top_queries, and gsc_keyword_opportunities, all of which return query-level performance data. Single and batch sitemap tools also overlap, though they are separable by operation scope.

    Naming Consistency4/5

    All tool names use a consistent gsc_ prefix and snake_case convention, which is predictable. However, some names are verb-noun (list_sites, delete_sitemap) while others are noun-only (top_queries, keyword_opportunities), creating minor stylistic inconsistency.

    Tool Count5/5

    Twelve tools is well-scoped for a Search Console server covering site listing, URL inspection, sitemap management, and search analytics. Each tool has a defensible place in the overall surface without feeling padded or redundant.

    Completeness4/5

    The tool surface covers the major Search Console workflows: property discovery, URL inspection, sitemap submission/deletion/status, and search performance analysis. Minor gaps like per-property detail retrieval or richer analytics dimensions exist but are workable around.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources