Open Podcast Prefix Project (OP3) MCP Server
Related Servers
Alternatives to Open Podcast Prefix Project (OP3) MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server for the Podcast Index API — search podcasts, track appearances, monitor trending shows, check feed health18291MIT

@vskstudio/takt-mcpofficial
AlicenseAqualityFmaintenanceMCP server for querying privacy-friendly website analytics from a self-hosted Takt instance, supporting metrics like visitors, pageviews, realtime activity, and more.1016MIT- AlicenseAqualityDmaintenanceRead-only MCP server for Umami analytics. It talks to the Umami REST API directly over HTTP, supporting self-hosted and cloud setups.810MIT
- FlicenseNot gradedqualityDmaintenanceMinimal MCP server for OpenPanel analytics, enabling queries for landing pages, page events, and tracked event names.-
- AlicenseAqualityDmaintenanceRead-only MCP server for querying ClickHouse (product telemetry) and Elasticsearch (download analytics), built for Percona VISTA.9Apache 2.0
- FlicenseAqualityCmaintenanceMinimal read-only MCP server that lets you query a Dawarich instance for stats, timeline, visits, points, track details, exports, reverse geocoding, and journey summaries.9-
TDQS
Scored across 6 tools
Each tool targets a distinct aspect of OP3 analytics: raw download records, per-episode counts, show lookup, download summary, top apps, and top countries. Descriptions clearly differentiate their purposes and guide the agent to choose the right one.
All tools start with 'op3_' and use snake_case, but there is a minor inconsistency: 'op3_get_show' uses a verb prefix while others use noun phrases (e.g., 'op3_show_downloads'). Overall, the pattern is clear and predictable.
With 6 tools, the server covers the essential queries for the Open Podcast Prefix Project without being overly numerous or sparse. Each tool serves a clear purpose and earns its place.
The tool set covers core podcast analytics needs: show discovery, raw data, per-episode stats, summary, app distribution, and geography. Missing features like user-agent breakdown or time-of-day analysis are minor; the set is well-scoped for its domain.