Skip to main content
Glama
apexradius

mcp-search-console

by apexradius
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to mcp-search-console

No user-submitted related servers found.

    Related Servers

    • gsc-mcp-connector

      dzhitnitsky
      A
      license
      Not graded
      quality
      C
      maintenance
      Self-hosted MCP server for Google Search Console. Enables natural language queries to list sites, analyze search analytics, inspect URLs, and check sitemaps through AI assistants.
      MIT

    • gsc-mcp-connector

      JuJu78
      A
      license
      Not graded
      quality
      B
      maintenance
      Self-hosted MCP server that exposes Google Search Console tools (list sites, query analytics, inspect URL, list sitemaps) via natural language to AI assistants like ChatGPT and Claude.
      1
      MIT

    • gsc-mcp-connector

      ValetudoSEO
      A
      license
      Not graded
      quality
      C
      maintenance
      Self-hosted MCP server that connects Google Search Console to AI assistants, enabling natural language queries about search analytics, sitemaps, and URL inspection data.
      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

    • Google MCP Server

      kairos-company
      A
      license
      Not graded
      quality
      D
      maintenance
      A unified MCP server that gives AI assistants direct access to Google Analytics 4, Google Search Console, Google Ads and Google Merchant Center data using OAuth2 user credentials.
      MIT

    • wingolf-ai-mcp

      sonzin
      F
      license
      A
      quality
      D
      maintenance
      MCP server integrating Google Search Console, Google Analytics 4, and GitHub, enabling AI clients to query search analytics, traffic data, and repository information.
      1
      -
    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 17 tools

    Disambiguation5/5

    Each tool targets a specific operation with clear boundaries. Search analytics tools are differentiated by scope and features (overview, compare, advanced, per-page). URL inspection tools distinguish single, batch, and actionable issue-checking.

    Naming Consistency5/5

    All tool names use lowercase with underscores following a consistent verb_noun pattern (e.g., list_accounts, submit_sitemap, inspect_url). No mixing of styles.

    Tool Count4/5

    17 tools is slightly above the typical 3-15 range, but each tool serves a distinct purpose within the Google Search Console domain. The count is justified by the breadth of functionality covered.

    Completeness5/5

    The tool set covers the full lifecycle: account management, property details, sitemap operations, multiple search analytics views, and URL inspection (single, batch, issue analysis). No obvious gaps for common GSC workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources