Skip to main content
Glama
thenavidm

Google Search Console MCP

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Google Search Console MCP

No user-submitted related servers found.

    Related Servers

    • search-console-mcp

      OrellBuehler
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to access Google Search Console search performance and index health data, including clicks, impressions, rankings, URL inspection, and sitemap management.
      196 npm
      MIT

    • Google Search Console MCP

      sidiio
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to query Google Search Console data including search analytics, URL inspection, sitemap management, and site performance monitoring, with per-user OAuth authentication.
      -

    • 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

      sarahpark
      A
      license
      A
      quality
      A
      maintenance
      Provides AI agents with read-only access to Google Search Console data, including search analytics, index coverage, and sitemap status. It enables users to query clicks, impressions, and ranking performance or check URL indexing status through natural language.
      4
      66 npm
      9
      MIT

    • mcp-server-gsc

      noduslabs
      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
      2,444 npm
      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

    A4/5.0

    Scored across 19 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: site management, analytics queries, sitemap operations, URL inspection, and verification are well-separated. Overlaps like get_site vs list_sites vs list_verified_sites are differentiated by scope (single property, account properties, verified across Google).

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (get_site, list_sites, add_site, delete_site), with slight deviations like inspect_url vs inspect_urls and verify_site. The analytics tools use noun phrases (top_queries, striking_distance), which breaks the pattern but remains understandable.

    Tool Count5/5

    19 tools are well-suited for the comprehensive scope of Google Search Console management, covering all major areas without excessive bloat. Each tool appears to earn its place.

    Completeness5/5

    The server covers the full lifecycle: site add/delete/verify, sitemaps, analytics queries (including specialized reports), URL inspection (single and batch), and account management. No obvious gaps for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources