Podcastindex MCP vs Podwise
A side-by-side look at the Podcastindex MCP and Podwise MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
P
PodwisePodcasts · Remote HTTP/SSEPodwise gives agents podcast knowledge. Search podcasts and episodes, pull a full transcript, read the AI summary, chapters, highlights, Q&A and mind map, ask questions across transcripts, translate an episode, clip key moments, and export notes as Markdown or SRT. 38 tools. Hosted remote endpoint with OAuth; tool calls need a Podwise account on a Pro or Enterprise plan. Docs: https://docs.podwise.ai/mcp60GoodAuth: oauth 2.0Verdict: choose Podcastindex MCP for podcasts work over a hosted endpoint; choose Podwise for podcasts over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Podcastindex MCP when
- You need dedicated capabilities in the Podcasts domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
PODCASTINDEX_API_KEY, PODCASTINDEX_API_SECRET. - You want tools like
search_by_person, search_by_term, search_by_title.
PChoose Podwise when
- You need dedicated capabilities in the Podcasts domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | P Podwise | |
|---|---|---|
| Category | Podcasts | Podcasts |
| Quality signal | 55/100 · Good | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | API key required | OAuth 2.0 |
| Pricing | Free | Not declared |
| Required env vars | PODCASTINDEX_API_KEYPODCASTINDEX_API_SECRET | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 0 |
| Directory activity | 3 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 18 | Not listed |
| Full listing | View Podcastindex MCP | View Podwise |
Tools & capabilities
Podcastindex MCP tools 18
search_by_personSearch for episodes where a person appeared as host or guest. Returns matches across all indexed podcasts.search_by_termFull-text search across all podcasts by topic, show name, or keyword.search_by_titleSearch for podcasts by title.podcast_by_feed_urlLook up a podcast by RSS feed URL. Returns feed ID, iTunes ID, categories, last update, and feed health.podcast_by_feed_idLook up a podcast by its Podcast Index feed ID. Returns full metadata.podcast_by_itunes_idLook up a podcast by its Apple Podcasts (iTunes) ID.podcast_by_guidLook up a podcast by its `podcast:guid` tag value.trending_podcastsGet currently trending podcasts, with optional language and category filters.episodes_by_feed_idGet episodes for a specific podcast by feed ID.episode_by_idLook up a single episode by its Podcast Index episode ID.episodes_liveGet episodes that are currently live (actively streaming).recent_episodesGet the most recently published episodes across the entire index.- +6 more on the listing page
Podwise tools
No tool names declared yet. Check the project README from the listing page.
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.
Podcastindex MCP
{
"mcpServers": {
"conorbronsdon-podcastindex-mcp": {
"url": "https://mcp.transistor.fm"
}
}
}
Podwise
{
"mcpServers": {
"podwise": {
"url": "https://docs.podwise.ai/mcp"
}
}
}
Frequently asked questions
Podcastindex MCP is categorized under Podcasts and uses a remote HTTP/SSE transport. Podwise belongs to Podcasts and uses a remote HTTP/SSE transport. Pick Podcastindex MCP for podcasts work and Podwise 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.
Podcastindex MCP is listed as free. Auth: api key required. Podwise has no declared pricing — check the project's own site. Auth: oauth 2.0. 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 conorbronsdon-podcastindex-mcp and podwise as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Podcastindex MCP has a quality signal of 55/100 (Good) with 3 views, 0 installs and 1 GitHub stars. Podwise has 60/100 (Good) with 0 views, 0 installs and 0 GitHub stars.