Skip to main content
Glama
dienhokhanh

Google Search Console MCP

by dienhokhanh

Related Servers

Alternatives to Google Search Console MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to retrieve Search Console search analytics, find multilingual question-shaped queries and SEO opportunities, inspect URLs, and view or manage sitemaps with server-side date resolution and comparisons.
      6
      MIT
    • 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
    • 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.
      110 npm
      1
      MIT
    • A
      license
      A
      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
      553 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to list accessible Search Console properties and query search-analytics data—clicks, impressions, CTR, and position—over date ranges grouped by chosen dimensions, authenticating read-only as the user's own Google account.
      94 npm
      MIT
    • 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

    TDQS

    A3.6/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: sites (list vs permission get), sitemaps (list vs detail get), URL inspection, and search analytics. The list/get pairs are clearly separated by their descriptions, and query_search_analytics and inspect_url have no overlap.

    Naming Consistency5/5

    All tools use a uniform gsc_ prefix followed by a consistent verb_noun pattern (list_sites, inspect_url, get_site, query_search_analytics, list_sitemaps, get_sitemap). No style mixing.

    Tool Count5/5

    Six tools is well-scoped for a Search Console read surface, covering properties, sitemaps, analytics, and URL inspection without redundancy. Each tool earns its place.

    Completeness4/5

    Core read operations (list/get sites, list/get sitemaps, analytics query, URL inspection) are covered. Notable gaps exist on the write side: no sitemap submission/deletion and no indexing request, which limits lifecycle coverage but is workable for a read-focused server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues