Skip to main content
Glama
saurabhsharma2u

Search Console MCP

by saurabhsharma2u
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to Search Console MCP

No user-submitted related servers found.

    Related Servers

    • GSC MCP Server

      drewbeechler
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that provides read-only access to Google Search Console data, enabling natural language queries about SEO performance, rankings, and indexing status.
      113 npm
      MIT

    • gsc-mcp

      jayrockliffe-defused
      A
      license
      A
      quality
      C
      maintenance
      MCP server for querying Google Search Console data — search analytics, URL inspection, sitemap monitoring, and more — read-only tools for any MCP-compatible AI client.
      7
      Apache 2.0

    • gsc-mcp

      odrones
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that exposes the Google Search Console API, allowing LLMs to query SEO data, inspect URLs, manage sitemaps, and analyze search performance via natural language.
      73 npm
      MIT

    • Google Search Console MCP

      damupi
      A
      license
      Not graded
      quality
      D
      maintenance
      This MCP server provides LLMs with programmatic access to Google Search Console data and functionality, including search analytics, sitemap management, site management, and URL inspection.
      MIT

    • Google Search Console MCP

      Vrealmatic
      A
      license
      Not graded
      quality
      D
      maintenance
      Read-only MCP server that gives AI clients access to Google Search Console data, enabling natural language queries about traffic, rankings, and SEO opportunities.
      113 npm
      MIT

    • searchconsole-mcp

      harisnadeem
      A
      license
      A
      quality
      C
      maintenance
      A lightweight, fast MCP server for Google Search Console. Query search analytics, manage sitemaps, and inspect URLs directly from your AI assistant.
      7
      Apache 2.0
    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

    B3/5.0

    Scored across 25 tools

    Disambiguation3/5

    Most tools target distinct resources (sitemaps, indexing, sites, AdSense), but the analytics/audit cluster is fuzzy: site_health_check, seo_audit, analytics_anomalies, and analytics_compare all overlap around diagnosing traffic/health issues. Descriptions help separate them, but an agent could still hesitate between health check, audit, anomaly detection, and period comparison.

    Naming Consistency2/5

    Tool names mix conventions unpredictably: some are noun_verb (sites_manage, sitemaps_submit), some verb_noun (compare_engines), some bare nouns (diagnostics, get_started), and some are redundant (inspection_inspect). This makes it hard to guess the correct tool name from the pattern.

    Tool Count3/5

    With exactly 25 tools, the server sits at the heavy end of the borderline range. The breadth partially justifies the count since it covers Search Console, Bing, GA4, AdSense, PageSpeed, and schema validation, but many adjacent concerns are exposed as individual tools rather than consolidated surfaces.

    Completeness4/5

    The core Search Console/Bing workflows are well covered: site management, sitemaps CRUD, performance analytics, URL inspection, indexing submission, and status checks. Minor gaps exist (e.g., no URL removal tool or GSC message/alerts surface), but nothing creates a dead end in normal SEO diagnostic workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessSlow

    Resources