Skip to main content
Glama
eduardmur

Google Search Console MCP

by eduardmur
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Google Search Console MCP

No user-submitted related servers found.

    Related Servers

    • Google Search Console MCP

      dienhokhanh
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to query Search Analytics metrics, list and inspect properties and sitemaps, and inspect indexed URLs with secure authentication and optional allowlisted write controls.
      MIT

    • google-search-console-mcp

      getmcpads-com
      A
      license
      B
      quality
      A
      maintenance
      Enables MCP clients to query Google Search Console search performance, inspect indexing, analyze sitemaps, and run SEO analyses such as cannibalisation detection, query clustering, and wins/losses, all with read-only access.
      20
      230 npm
      Apache 2.0

    • @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
      1
      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.
      159 npm
      1
      MIT

    • GSC MCP Server

      luminarylane
      A
      license
      A
      quality
      A
      maintenance
      Connects MCP clients to the Google Search Console API, enabling search analytics queries, URL inspection, sitemap management, and performance comparison across time periods.
      20
      35 PyPI
      MIT

    • mcp-google-search-console

      crunchtools
      A
      license
      A
      quality
      A
      maintenance
      Secure MCP server for Google Search Console. Query search analytics (clicks, impressions, CTR, position), manage sitemaps, inspect URL indexing status, and manage site properties.
      10
      AGPL 3.0
    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

    A3.8/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool has a clearly stated distinct purpose, but query, question-queries, and opportunities all operate over the same Search Analytics data. The descriptions differentiate them well (raw rows vs question-shaped candidates vs pre-built analyses), so an agent can mostly tell them apart, though there is latent overlap since query could partially replicate the other two.

    Naming Consistency3/5

    All names are lowercase kebab-case, but the pattern is mixed: list-properties, question-queries, and inspect-url follow a verb_noun shape while query, opportunities, and sitemaps are bare nouns. Readable but not a predictable convention.

    Tool Count5/5

    Six tools is well-scoped for Search Console's surface, with each tool earning its place and none appearing redundant or trivial. No bloat or thinness.

    Completeness4/5

    Covers the core GSC lifecycle: property listing, Search Analytics (with comparison and filtering), question mining, opportunity detection, URL inspection, and sitemap status/submit/delete. Minor gaps like property-level administration or authentication/verification ops exist but are typically handled in the UI, so agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources