Skip to main content
Glama
Klartika

gsc-mcp-server

by Klartika
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to gsc-mcp-server

No user-submitted related servers found.

    Related Servers

    • gsc-mcp-connector

      Alex-lang272
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables natural-language querying of Google Search Console data, including search analytics, site properties, URL inspection, and sitemap status, through MCP-compatible clients like ChatGPT and Claude.
      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.
      112 npm
      1
      MIT

    • GSC-MCP-Server

      AppsYogi-com
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects Google Search Console to MCP clients to query search analytics, manage sitemaps, and perform URL inspections. It enables users to identify SEO opportunities and generate performance reports through natural language interactions.
      52 npm
      4
      MIT

    • gsc-mcp-connector

      JBMKL
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to query Google Search Console data—properties, search analytics, URL inspection, and sitemaps—through natural language via a self-hosted MCP endpoint.
      MIT

    • GSC MCP Server

      soumyadeep-ux
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Google Search Console to query search analytics, inspect URL indexing status, and manage sitemaps. It allows users to monitor SEO performance and site health through natural language commands in MCP-compatible clients.
      89 npm
      3
      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

    A3.6/5.0

    Scored across 21 tools

    Disambiguation2/5

    Multiple tools overlap significantly: get_sitemaps, list_sitemaps_enhanced, and manage_sitemaps all list sitemaps; get_search_analytics, get_advanced_search_analytics, get_performance_overview, and get_search_by_page_query all return analytics data. This creates unclear boundaries and risks misselection.

    Naming Consistency3/5

    Most tools follow a verb_noun pattern (get_, list_, add_, delete_), but there are inconsistencies: get_sitemaps vs list_sitemaps_enhanced, inspect_url_enhanced vs batch_url_inspection (inconsistent word order), and the generic manage_sitemaps and reauthenticate break the pattern.

    Tool Count3/5

    21 tools is on the heavy side for a GSC server. Many tools duplicate functionality (e.g., multiple sitemap and analytics tools), making the count feel bloated, though it is not extremely excessive.

    Completeness4/5

    Core GSC operations are covered: property management (list/add/delete), sitemap submission and deletion, URL inspection, and search analytics. A minor gap is the lack of tools for managing permissions or performing bulk property changes, but the essential surface is complete.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive

    Resources