Podcast Parser vs Podcastindex
A side-by-side look at the Podcast Parser and Podcastindex MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Podcast Parser for podcasts work as a local process; choose Podcastindex for podcasts as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Podcast Parser when
- You need dedicated capabilities in the Podcasts domain.
- You prefer a local stdio subprocess transport.
Choose Podcastindex when
- You need dedicated capabilities in the Podcasts domain.
- You prefer a local stdio subprocess transport.
- You want tools like
search_podcasts, get_podcast, episodes.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Podcasts | Podcasts |
| Quality signal | 41/100 · Fair | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 4 |
| Full listing | View Podcast Parser | View Podcastindex |
Tools & capabilities
Podcast Parser tools
No tool names declared yet. Check the project README from the listing page.
Podcastindex tools 4
search_podcastsPodcast search by term. Find podcasts in the open podcast database by name or keyword. Returns matching podcasts with title, author, description, categories, episode count, and artwork. Example: search_podcasts({ query: "true crime", max: 10 })get_podcastGet full metadata for a single podcast by its Podcast Index feed ID. Returns title, author, description, owner, episode count, categories, language, and artwork. Example: get_podcast({ feed_id: 920666 })episodesList recent episodes for a podcast by its Podcast Index feed ID. Returns episode title, description, publish date, duration, audio URL, and episode/season numbers. Example: episodes({ feed_id: 920666, max: 10 })trendingGet trending podcasts across the open podcast database, ranked by recent activity. Optionally filter by language or category. Returns podcast title, author, categories, artwork, and trend score. Example: trending({ max: 10, lang: "en", cat: "Technology" })
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Podcast Parser
{
"mcpServers": {
"podcast-parser": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-podcast-parser"
]
}
}
}
Podcastindex
{
"mcpServers": {
"podcastindex": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-podcastindex"
]
}
}
}
Frequently asked questions
Podcast Parser is categorized under Podcasts and uses a local stdio subprocess. Podcastindex belongs to Podcasts and uses a local stdio subprocess. Pick Podcast Parser for podcasts work and Podcastindex for podcasts.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Podcast Parser has no declared pricing — check the project's own site. Podcastindex has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add podcast-parser and podcastindex as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Podcast Parser has a quality signal of 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Podcastindex has 53/100 (Good) with 1 views, 0 installs and 0 GitHub stars.