Skip to main content
Glama
amirjahfar1

Google Search Console (GSC) MCP

by amirjahfar1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Google Search Console (GSC) MCP

No user-submitted related servers found.

    Related Servers

    • Google Search Console MCP

      justingluska
      A
      license
      A
      quality
      D
      maintenance
      Connects AI assistants to Google Search Console data for SEO analysis, including search analytics, URL inspection, sitemaps, indexing, and opportunity detection.
      17
      MIT

    • Sam GSC MCP

      krishanthsam
      F
      license
      Not graded
      quality
      C
      maintenance
      Connects Google Search Console to AI assistants so users can query and analyse SEO performance data in natural language. Provides search analytics, SEO insights, URL inspection, indexing, sitemaps, hourly reporting, and CSV export.
      -

    • mcp-search-console

      ledokter
      A
      license
      A
      quality
      D
      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

      bafrey
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects AI assistants to Google Search Console so users can query search analytics, compare performance periods, inspect URL indexing status, and manage sitemaps and properties through natural language.
      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.5/5.0

    Scored across 20 tools

    Disambiguation2/5

    Multiple tools serve overlapping purposes: sitemap management has three tools (get_sitemaps, list_sitemaps_enhanced, manage_sitemaps) and URL inspection has three (batch_url_inspection, inspect_url_enhanced, check_indexing_issues). Search analytics tools also overlap, causing potential ambiguity.

    Naming Consistency2/5

    Naming pattern is inconsistent: some tools use verb_noun (add_site, delete_site, submit_sitemap) while others use get_X or other patterns (get_sitemaps, inspect_url_enhanced, batch_url_inspection). This mix reduces predictability.

    Tool Count3/5

    20 tools for a GSC server is near the upper bound of reasonableness. While the scope is broad, there is redundancy (e.g., manage_sitemaps duplicates individual sitemap tools) suggesting a leaner set would be more appropriate.

    Completeness3/5

    Covers core GSC areas (sites, sitemaps, search analytics, URL inspection) but lacks coverage reports (like index coverage or mobile usability). Some CRUD operations for sitemaps are duplicated rather than streamlined.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources