Skip to main content
Glama
surendranb

Google Search Console MCP Intel Engine

by surendranb

Related Servers

Alternatives to Google Search Console MCP Intel Engine

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables natural-language, read-only analysis of your own Google Search Console and Google Analytics 4 data, including search performance, engagement, sitemap health, ranking opportunities, and deterministic SEO audits through MCP clients like ChatGPT.
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Professional Google Search Console MCP server providing 40+ SEO tools for performance analysis, content decay, CTR opportunities, and more, enabling real search data in clients like Cursor and Claude.
      40
      10 npm
      6
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to fetch Google Search Console search analytics reports (clicks, impressions, CTR, position) over MCP, with support for custom date ranges, dimensions, filters, comparisons, and exports.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables natural-language querying of Google Search Console data, including search analytics, site properties, URL inspection, and sitemap status, through MCP-compatible clients like ChatGPT and Claude.
      MIT
    • 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
    • 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

    TDQS

    A4/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: sites, dimensions, metrics, skills, sitemaps, analytics, and setup. The only similar pair is skills_list/skill_read but they are clearly list vs. fetch-content, matching the standard pattern. No meaningful overlap.

    Naming Consistency4/5

    Most tools follow a clear verb_noun snake_case pattern (list_, get_, submit_, delete_, setup_). However, skills_list and skill_read invert the convention to noun_verb, which is a minor but noticeable deviation from the dominant pattern.

    Tool Count5/5

    Ten tools is well-scoped for a GSC integration, covering metadata discovery, sitemap management, analytics retrieval, skills/playbooks, and setup. Each tool has a clear role without redundancy or bloat.

    Completeness4/5

    The surface covers core GSC workflows: listing sites, querying analytics, managing sitemaps, and enumerating dimensions/metrics. Minor gaps exist, such as no direct URL inspection tool or ability to fetch a single site's details, but these can be worked around with existing tools.

    Maintenance

    ActivityActive
    ResponsivenessResponsive