Podcast Index MCP for AI. Pull structured episode and show data using any ID or keyword.
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
Podcast Index gives your agent direct access to an open database of podcast shows and episodes. Instead of scraping proprietary sites, you search for content using keywords, titles, or specific identifiers like iTunes IDs and GUIDs.
It lets you list all episodes for a feed or find niche shows by the people featured in them. Use it when you need structured metadata from across the entire podcasting ecosystem.
What your AI can do
Get episode by guid
Retrieves the full details for a single episode using its unique Global Unique Identifier (GUID).
Get episodes by feed id
Lists all episodes associated with a podcast feed, identified by its internal Index ID.
Get episodes by feed url
Lists episodes for a podcast by providing the full RSS feed URL.
Find podcasts across the index using a general search term, a specific title, or by the name of a person featured in an episode.
Get full details on a show using its RSS feed URL, internal Index ID, Podcast GUID, or iTunes ID.
Fetch a chronological list of every episode published under a known podcast feed URL or ID.
Discover new material by listing the most recently updated feeds, getting random episodes, or pulling the latest published items.
Ask an AI about this
Waiting for input…
Podcast Index: 16 Tools for Content Retrieval
These tools let you search the entire podcast index using specific identifiers (GUIDs, URLs, IDs) or general terms to pull structured metadata and episode lists.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Podcast Index on VinkiusGet Episode By Guid
Retrieves the full details for a single episode using its unique Global Unique Identifier (GUID).
Get Episodes By Feed Id
Lists all episodes associated with a podcast feed, identified by its internal Index...
Get Episodes By Feed Url
Lists episodes for a podcast by providing the full RSS feed URL.
Get Podcast By Feed Id
Gets general details about a podcast show using its internal Index ID.
Get Podcast By Feed Url
Gets general details about a podcast show by providing the full RSS feed URL.
Get Podcast By Guid
Retrieves high-level podcast information using its Podcast GUID.
Get Podcast By Itunes Id
Gets general details about a podcast show using its unique Apple iTunes ID number.
Get Random Episodes
Returns a selection of episodes chosen at random from the entire index.
Get Recent Episodes
Fetches a list of episodes that were published most recently across the network.
Get Recent Feeds
Lists podcast feeds that have been added or updated very recently to the index.
Get Recent New Feeds
Identifies and lists podcast feeds that have never been seen before by the index.
Get Value By Feed Id
Retrieves a specific value block (e.g., network details) using a feed's internal Index ID.
Get Value By Feed Url
Retrieves a specific value block for a podcast by providing its full RSS feed URL.
Search By Person
Searches the index for any podcasts that feature or are associated with a named...
Search By Term
Performs a broad search across all podcast content using general keywords (e.g....
Search By Title
Finds podcasts by searching for exact or partial matches against the show's official...
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Podcast Index, then connect any of our 5,000+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,000+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Podcast Index. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 16 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Finding podcast episodes shouldn't require knowing every API endpoint.
Today, to build a simple content indexer, you have to write logic that handles five different ways of identifying a show: by its GUID, by its URL, by its iTunes ID, and so on. You end up with brittle code full of `if/else` statements just checking which ID format the user provided.
With this MCP server, your agent takes care of the routing. It doesn't matter if you give it an Index ID or a feed URL; calling `get_episodes_by_feed_url` gives you the episode list. The complexity disappears into a single, simple call.
Podcast Index MCP Server: Structured data by keyword and ID
Before this tool, pulling an episode required knowing if it was best found via its feed's RSS URL or if you needed to search for the show's name. You were stuck copying and pasting dozens of different identifiers into multiple API calls.
Now, your agent handles that ambiguity. Need episodes about AI? Run `search_by_term`. Get the ID, then run `get_episodes_by_feed_id` to get the full list. It's simple, predictable, and always works.
What your AI can actually do with this
This Podcast Index server gives your agent direct access to a massive, open database of podcast shows and episodes. You don't have to scrape proprietary sites; you just tell your AI client what you need, and it finds structured metadata across the whole podcasting ecosystem.
When you use this, your agent can pull up general show details using multiple identifiers: feed URLs, internal Index IDs, Podcast GUIDs, or even Apple’s unique iTunes ID number. It’s robust. You'll never get stuck because of an unsupported format.
Finding Content
You need to find a specific show? Your agent runs searches by general keywords using search_by_term—think broad topics like 'finance' or 'machine learning.' You can nail down shows with search_by_title, which finds matches whether the title is partial or exact. Or, if you know who talked on it, you use search_by_person to find podcasts associated with a specific individual.
Listing Episodes and Show Details
Fetching episode lists is simple, regardless of how the show is indexed. If you've got the full RSS feed URL or the internal Index ID, your agent uses get_episodes_by_feed_url or get_episodes_by_feed_id, respectively, to list every single published episode for that podcast. For a single deep dive, it pulls all details for one show using its unique Global Unique Identifier (GUID) with get_episode_by_guid.
Beyond listing episodes, you can also grab the general metadata about the entire show—like getting basic info from get_podcast_by_feed_url or get_podcast_by_feed_id, or retrieving high-level data just using the Podcast GUID with get_podcast_by_guid. You can even pull network details, like a publisher's name block, by calling get_value_by_feed_id or get_value_by_feed_url.
Discovering New and Recent Material
Need to know what’s fresh? Your agent checks for new material. It runs get_recent_episodes to pull a list of the latest items published across the whole index. If you're looking at sources, it gives you a rundown of feeds that were recently updated or added using get_recent_feeds. Better yet, if you want something brand-new and never seen by this index before, use get_recent_new_feeds.
Sometimes you just wanna browse. You can ask for a random selection of episodes with get_random_episodes, or pull up the absolute latest content using dedicated functions designed to find new shows across the network.
Summary of Power
When your agent uses this, it means you're bypassing proprietary APIs and instead working off an open index. You can list all episodes from a feed URL via get_episodes_by_feed_url or pull general show details using its internal Index ID with get_podcast_by_feed_id. It handles retrieving detailed information for any given podcast's GUID, and it gives you access to specific value blocks like network info through both the feed URL (get_value_by_feed_url) and the feed index ID (get_value_by_feed_id).
Your agent controls all this data flow, letting you query content using keywords (search_by_term), by show title (search_by_title), or even just by a person's name featured on it (search_by_person). You’ll have comprehensive control over your podcast research.
019e38d8-92e5-736c-aca9-84c591c85459 Here's how it actually works
The bottom line is: you tell your agent what content you need—a keyword, an ID, or a date range—and it pulls the accurate, structured data back to you.
Subscribe to this server and provide your Podcast Index API Key and Secret.
Call a tool (e.g., search_by_term) from your AI client, passing the required search parameters.
The server executes the query against its index and returns structured metadata and episode lists.
Who is this actually for?
Content researchers and developers who build tools around media discovery. This server helps people stop building fragile scrapers that break when podcast sites change their structure. If your job involves cataloging, monitoring, or analyzing large amounts of audio content metadata, you need this.
Needs to find all episodes mentioning a specific topic (like 'quantum computing') across dozens of different podcast feeds for competitive analysis.
Writes an application that needs to pull the latest episode list from a client's unique RSS feed URL and display it in a custom dashboard.
Wants to track how often specific guests (e.g., Elon Musk) are featured across different podcasts to map industry influence.
What Changes When You Connect
Stop building custom scrapers. Instead of relying on fragile, site-specific code, you use tools like get_podcast_by_itunes_id to pull standardized metadata regardless of where the podcast lives.
Search deep by person. Use search_by_person when your goal is tracking industry influence—you find all shows featuring a guest without knowing their specific feed ID or title.
Get fresh content easily. The tools get_recent_episodes and get_recent_feeds let you build monitoring pipelines that alert you instantly to new material, bypassing manual checks of multiple RSS feeds.
Handle all discovery needs. You can start broad with search_by_term, then narrow down the result using get_podcast_by_feed_url to get actionable data for a specific show.
Never lose an episode ID. By having dedicated endpoints like get_episode_by_guid, you ensure that even if a feed moves or changes, your ability to pull one specific piece of content remains reliable.
See it in action
Tracking competitor mentions
A marketing analyst needs to see which podcasts are talking about their rival. Instead of manually searching YouTube and multiple RSS feeds, they ask their agent to run search_by_term with the rival's name. The agent returns a list of all relevant shows and episodes.
Building an archive for historical data
A content developer needs to build a database of classic interviews. They use get_podcast_by_guid combined with search_by_person to systematically gather all available metadata and episode details related to key figures, regardless of the original hosting service.
Validating new content sources
A podcast aggregator needs to know if a partner has started publishing. They run get_recent_new_feeds. If results appear, they can then use get_podcast_by_feed_id to quickly pull the show's core details and verify it's legitimate.
Curating a themed playlist
A user wants recommendations for shows related to AI. They ask their agent to run search_by_term ('artificial intelligence'). The agent returns the top results, and then they can use get_episodes_by_feed_url on the best candidate feed to see the latest episode list.
The honest tradeoffs
Assuming one search tool works for everything
The user thinks that calling search_by_term('AI') will give them the full metadata, including the iTunes ID or GUID. It only gives a list of shows.
First, run search_by_term to get the candidate show names. Then, take the name and pass it through get_podcast_by_feed_url (or use get_value_by_feed_id) to pull the structured metadata required for your database.
Building complex scrapers
Trying to write custom code that hits multiple public RSS feed URLs and manually parses XML tags to extract titles and dates. This breaks every time a podcast host updates their site.
Use the MCP server's specific tools like get_episodes_by_feed_url or get_episode_by_guid. These endpoints handle all the parsing complexity for you, giving clean JSON output.
Ignoring specific identifiers
When querying a show known to be on Apple Podcasts, the user only searches by keywords and misses the chance to use get_podcast_by_itunes_id for guaranteed accuracy.
If you have an iTunes ID or a Podcast GUID, always check if there is a dedicated retrieval tool. These specific endpoints are faster and more reliable than general term searching.
When It Fits, When It Doesn't
Use this server if your goal is to systematically extract structured metadata from the podcasting industry. For example, if you need to find every episode featuring 'Lex Fridman,' start with search_by_person. If you know a show's Apple ID, use get_podcast_by_itunes_id for immediate, focused data. Don't try to build a universal search that handles everything; instead, combine tools: Use search_by_term first to narrow down the shows, and then use get_episodes_by_feed_url on the top result to pull the actual episode list. Do not rely solely on get_recent_feeds if you need data from a specific, established show; always use an ID-based getter tool for reliability.
Questions you might have
How do I find episodes for a show if I only know the host's name? (using search_by_person) +
You run search_by_person with the host's name. This tool returns associated podcasts, giving you multiple options and their respective feed IDs to work with.
Can I get a list of episodes if I don't know the exact feed ID? (using get_episodes_by_feed_url) +
Yes. You use get_episodes_by_feed_url and pass in the full RSS URL instead of an ID. The server handles the parsing to list the episodes for you.
Which tool is best for getting all podcast details quickly? (using get_podcast_by_itunes_id) +
If you have an iTunes ID, get_podcast_by_itunes_id is the fastest way. It bypasses searching and goes straight to the metadata using a guaranteed unique identifier.
How do I find new podcasts that aren't in my usual feeds? (using get_recent_new_feeds) +
Run get_recent_new_feeds. This tool checks the index and returns a list of entire podcast feeds that have been added recently, helping you discover content sources.
If I use `get_podcast_by_feed_url`, what data fields are returned for a podcast? +
The tool returns core metadata including the title, description, and primary GUID. It provides enough context to verify if this is the correct show before you pull episode lists.
When using `search_by_term`, how do I handle multiple results or filters? +
The search function returns a list of matching podcasts, each with basic details. You must specify which result's Feed ID you want to use next for deeper episode lookups.
Can the `get_value_by_feed_id` tool retrieve specialized or structured data blocks? +
Yes, this tool accesses 'value block' metadata that goes beyond standard RSS fields. It pulls in unique content like specific network details or custom tags added to the feed.
If a podcast has thousands of episodes, how do I use `get_episodes_by_feed_id` without hitting rate limits? +
The tool handles results in paginated chunks. You must call the function repeatedly with the provided continuation token to pull all available data.
Can I search for podcasts where a specific person is a guest or host? +
Yes! Use the search_by_person tool with the person's name. The agent will return a list of podcasts associated with that individual.
How do I get the latest episodes from a specific show? +
You can use either get_episodes_by_feed_id if you have the internal ID, or get_episodes_by_feed_url if you have the RSS link. Both will provide a list of recent episodes.
Can I find a podcast if I only have its iTunes ID? +
Absolutely. Use the get_podcast_by_itunes_id tool to fetch the full Podcast Index metadata using the Apple Podcasts/iTunes identifier.
We've already built the connector for Podcast Index. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 16 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.