Skip to main content
Glama
justingluska

Google Search Console MCP Server

by justingluska
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Google Search Console MCP Server

No user-submitted related servers found.

    Related Servers

    • Google Search Console (GSC)

      amirjahfar1
      A
      license
      A
      quality
      C
      maintenance
      Connects Google Search Console to AI assistants, enabling natural language queries for SEO data, indexing audits, sitemap management, and full site audits.
      20
      MIT

    • mcp-search-console

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

      appscaptain
      A
      license
      A
      quality
      C
      maintenance
      Connects Google Search Console to AI assistants, enabling natural language analysis of SEO data. Provides read-only tools for properties, search analytics, URL inspection, and sitemaps.
      15
      MIT

    • Google Search Console MCP

      andrewjpyle
      A
      license
      A
      quality
      C
      maintenance
      Provides AI assistants with live access to Google Search Console search analytics, URL inspection, and sitemap management through real API calls.
      10
      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.8/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: sitemap management, URL inspection, analytics queries, and specific diagnostics are all separated cleanly. The only real ambiguity is among the analytics-analysis tools like find_opportunities, diagnose_traffic_drops, and content_decay, though their descriptions give enough differentiation.

    Naming Consistency3/5

    Snake_case is consistent, and clusters like submit_sitemap/list_sitemaps/delete_sitemap follow a clear verb_noun pattern. However, several diagnostic tools use bare nouns (cannibalization, content_decay, ctr_benchmarks, topic_clusters) and search_analytics/verify_claim break the action-oriented naming convention.

    Tool Count4/5

    At 17 tools, the server is slightly above the ideal 3-15 range, but the breadth is justified by covering four distinct GSC areas: sitemaps, indexing, raw analytics, and SEO diagnostics. Each tool addresses a specific use case and there is little obvious filler.

    Completeness4/5

    Core GSC workflows are covered well: sitemap CRUD, single and batch URL inspection, indexing notification status, and search analytics with period comparison and diagnostic helpers. Minor gaps exist, such as no property create/delete and no broader GSC reports like links or Core Web Vitals, but common SEO tasks can be completed without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources