Skip to main content
Glama
gsc-mcp

gsc-mcp

by yan-labs

Related Servers

Alternatives to gsc-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables read-only access to Google Search Console data, including property discovery, search analytics queries, and URL inspection, through a security-focused interface.
      3
      941 PyPI
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to perform evidence-backed Google Search Console investigations, including traffic change diagnosis, opportunity discovery, cannibalization detection, and indexing audits, all through read-only access.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables read-only access to Google Search Console data, including search analytics, sitemap status, URL inspection, and property listing.
      4
      51 npm
      MIT
    • 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
      69 PyPI
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables read-only access to Google Search Console, Bing Webmaster Tools, and PageSpeed Insights, allowing queries for analytics, sites, sitemaps, inspections, crawl issues, and page speed analysis via natural language.
      1,431 npm
      MIT
    • A
      license
      A
      quality
      B
      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
      165 npm
      Apache 2.0

    TDQS

    C2.5/5.0

    Scored across 8 tools

    Disambiguation3/5

    The core tools (list_sites, search_analytics, inspect_url, list_sitemaps) are clearly distinct, but the four insight tools have tautological descriptions ("Search Console insight: striking_distance") that give no real explanation, forcing the agent to infer meaning from names. All five analytics-related tools draw from the same underlying Search Console data, so the boundary between search_analytics and striking_distance/low_ctr/movers/cannibalization is unclear.

    Naming Consistency3/5

    Four tools follow a clean verb_noun convention (list_sites, search_analytics, inspect_url, list_sitemaps) while the four insight tools are bare noun phrases (striking_distance, low_ctr, cannibalization, movers). The style split is systematic but still breaks predictability about whether a tool is an action or a report.

    Tool Count5/5

    Eight tools is a well-scoped size for a Search Console analytics server, with room for site/sitemap listing, querying, inspection, and canned insights. Nothing feels padded or missing at the count level.

    Completeness3/5

    The surface covers discovery (sites, sitemaps), reporting (search_analytics), and inspection, but sitemaps are read-only — no submit or delete operation — and sites cannot be added or removed. For a diagnostics-oriented server this is workable, but sitemap submission is a standard Search Console operation that agents will hit as a dead end.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues