OP3 MCP
Related Servers
Alternatives to OP3 MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables asking Claude how apps are performing by reading App Store Connect sales, RevenueCat subscriber data, and PostHog events, comparing recent windows against previous periods.5MIT
- FlicenseAqualityDmaintenanceEnables natural language querying of Google Analytics 4, Google Search Console, Meta Ads, and Google Ads data through Claude.23-
- AlicenseNot gradedqualityBmaintenanceEnables 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.1MIT
- FlicenseNot gradedqualityDmaintenanceProvides 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-
- AlicenseAqualityBmaintenanceEnables 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.3635 npm1MIT
- AlicenseBqualityBmaintenanceEnables 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.4314 npm4MIT
TDQS
Scored across 22 tools
Each tool targets a distinct analytical dimension (downloads, unique listeners, geography, apps, devices, retention, overlap, raw rows), and the descriptions explicitly say when to prefer one over another. The few superficially similar tools (op3_show_downloads vs op3_query_downloads vs op3_episode_downloads, or op3_app_share vs op3_benchmark_apps vs op3_global_app_share) are clearly differentiated by scope and intent.
All 22 tools use a consistent snake_case verb_noun pattern uniformly prefixed with op3_. No camelCase, no mixed conventions, and the names read predictably.
22 tools is on the heavier side but justified by a genuinely broad analytics domain spanning downloads, listeners, geography, apps, devices, retention, and raw verification surfaces. Each tool earns its place rather than being redundant.
The surface covers the full analytic lifecycle: identifier resolution, show/episode metadata, aggregate metrics, audience composition, breakdowns, trends, cohort retention, raw escape hatches, and a diagnostic verification tool. No obvious dead ends for the stated podcast-analytics purpose.