Skip to main content
Glama
mario-hernandez

google-search-console-mcp-claude-code

by mario-hernandez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to google-search-console-mcp-claude-code

No user-submitted related servers found.

    Related Servers

    • google-search-console-mcp

      russjeffery
      A
      license
      A
      quality
      B
      maintenance
      MCP server for Google Search Console API, enabling search performance analysis, URL inspection, sitemap management, and property listing. Supports local, self-hosted, and Cloudflare Workers deployments.
      11
      MIT

    • flin-google-search-console-mcp

      flin-agency
      A
      license
      B
      quality
      C
      maintenance
      Read-only MCP server for Google Search Console, with browser-based OAuth flow and local token storage, enabling querying search analytics, site lists, and URL inspection.
      8
      MIT

    • google-search-console-mcp

      locomotive-agency
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for Google Search Console API that enables querying search analytics, managing sites, inspecting URLs, and supporting domain delegation via service accounts.
      16 PyPI
      MIT

    • SearchConsole.ai

      AndreyAzimov
      A
      license
      Not graded
      quality
      B
      maintenance
      Read-only MCP server for Google Search Console data, enabling search analytics, URL inspection, indexing diagnostics, and sitemap management through MCP clients.
      18 npm
      MIT

    • 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
    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.7/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool targets a distinct concept: alerts for regressions, cannibalization for competing pages, content_decay for declining pages, etc. No two tools have overlapping purposes; descriptions clearly differentiate them.

    Naming Consistency4/5

    All tool names use lowercase with underscores. While some are verb_noun (get_capabilities, inspect_url) and others are noun phrases (alerts, cannibalization, content_decay), the pattern is consistent and readable, with minimal deviation.

    Tool Count5/5

    14 tools is well-scoped for a Search Console server. It covers analytics, diagnostics, management, and specialized insights without being overwhelming or too thin.

    Completeness4/5

    The tool surface covers core Search Console operations: analytics (search_analytics, site_snapshot), diagnostics (inspect_url, list_sitemaps), and specialized insights (alerts, cannibalization, etc.). Minor gaps exist (e.g., no tool for managing users or viewing all errors), but the set is comprehensive for its focus.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources