Skip to main content
Glama

Related Servers

Alternatives to OP3 MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying and analyzing marketing data from Google Analytics 4, Search Console, YouTube, and optionally Google Ads and Meta Ads, stored in a unified DuckDB database, via natural language in Claude.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides statistical analysis and usage tracking for Claude Code, enabling users to query daily/monthly stats, compare users, analyze trends, detect anomalies, and generate usage reports through natural language.
      1
      -
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to search millions of podcasts, read and search episode transcripts with timestamps and speakers, and access chapters, soundbites, Podcasting 2.0 tags, value-for-value data, feed health, and index statistics through 36 tools.
      36
      371 npm
      1
      MIT
    • A
      license
      B
      quality
      A
      maintenance
      Enables querying Rybbit Analytics data directly through MCP-compatible clients like Claude Code. It provides tools for monitoring website statistics, user sessions, error logs, funnels, and performance metrics via natural language.
      43
      219 npm
      4
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Connects Google Analytics 4 data to Claude, Cursor and other MCP clients, enabling natural language queries of website traffic, user behavior, and analytics data with access to 200+ GA4 dimensions and metrics.
      10
      1,082 PyPI
      242
      MIT

    TDQS

    A4/5.0

    Scored across 22 tools

    Disambiguation4/5

    Most tools target clearly distinct analytical questions, and the descriptions do heavy lifting to explain why each exists. However, there is real overlap: op3_app_share and op3_benchmark_apps both report a show's app mix (one adds a global index), op3_get_show with include_episodes duplicates op3_list_episodes, and the three download tools (show/episode/query) sit close together, though the escape-hatch framing of op3_query_downloads helps.

    Naming Consistency4/5

    All names share a uniform op3_ prefix and snake_case, so they scan consistently. The style mixes verb-led names (get_show, resolve_show, list_episodes, compare_shows, verify_prefix, query_downloads) with noun-phrase names (download_trend, listening_patterns, show_downloads, audience_summary, geography), which is a minor deviation but still predictable and readable.

    Tool Count4/5

    22 tools is on the heavy side, but each maps to a genuinely distinct analytics question (retention, overlap, geography, device, apps, curves, verification). A couple could arguably be merged (app_share vs benchmark_apps, get_show's episode flag vs list_episodes), so it is slightly over-scoped rather than bloated.

    Completeness4/5

    For a read-only podcast analytics domain, the surface is broad: identity resolution, show/episode lookup, download and audience metrics, retention, geography, app/device breakdowns, raw queries, and a prefix-verification tool that addresses the common zero-data failure. Write operations are absent but out of scope for an analytics server, so coverage is nearly complete with only minor consolidation gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues