Podcast Index MCP
Related Servers
Alternatives to Podcast Index MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceWraps the Podcast Index API (podcastindex.org) to enable AI agents to search and retrieve podcast episodes and metadata.4 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables users to search for podcasts, discover trending shows, find episodes, and explore Value4Value monetization using the PodcastIndex API.3-

Rephonicofficial
AlicenseAqualityBmaintenanceGive AI agents and LLMs access to podcast data from Rephonic — covering 3+ million podcasts with listener estimates, demographics, contact details, chart rankings, episodes, and more.262MIT- AlicenseAqualityAmaintenanceEnables AI agents to discover long-tail podcasts through randomized probe queries, trend lookups, and RSS feed peeks, providing cadence, episode length, and feed details without requiring API keys.6MIT
- FlicenseNot gradedqualityDmaintenanceConnects AI assistants to Pocket Casts accounts for browsing subscriptions, reading episode details, and retrieving transcripts with automatic transcription via AssemblyAI when no native transcript exists.-
- AlicenseBqualityCmaintenanceEnables AI agents to access public Spotify data (tracks, albums, artists, playlists, podcasts) without an API key, including lyrics and podcast transcripts with optional login.281,192 PyPI305MIT
TDQS
Scored across 36 tools
Most tools map to a distinct resource and action, and the descriptions carefully separate similar-looking options like search_podcasts vs search_podcasts_by_title and get_recent_episodes vs get_trending. The main ambiguity is search_episodes_by_person vs find_guest_appearances, which both handle credited-person lookups and could lead to misselection if an agent does not read closely.
The set mostly follows a clear verb_noun pattern: search_, get_, list_, find_, submit_. There are minor deviations such as bare status, notify_feed_update instead of update_feed, and the mix of list_value_podcasts vs get_new_value_feeds, but the overall style is predictable and readable.
At 36 tools, this is a large surface for an agent to choose from, and many tools cover very narrow niche features or redundant listing variants that could be consolidated. The broad scope of Podcast Index justifies some size, but this is beyond the range where each tool is easy to keep in mind.
The domain is well covered: search, metadata, episodes, transcripts, chapters, soundbites, value blocks, trends, feed health, submission, and stats all have dedicated tools. The main gaps are a general episode keyword search and any update/remove workflow, but those are largely API or directory limitations rather than obvious agent-dead-end omissions.