Podwise vs Fyyd
A side-by-side look at the Podwise and Fyyd 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 Podwise for podcasts work over a hosted endpoint; choose Fyyd for podcasts as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
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.
Choose Fyyd when
- You need dedicated capabilities in the Podcasts domain.
- You prefer a local stdio subprocess transport.
- You want tools like
search_podcasts, search_episodes, get_podcast.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | P Podwise | |
|---|---|---|
| Category | Podcasts | Podcasts |
| Quality signal | 60/100 · Good | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | OAuth 2.0 | 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 | 7 |
| Full listing | View Podwise | View Fyyd |
Tools & capabilities
Podwise tools
No tool names declared yet. Check the project README from the listing page.
Fyyd tools 7
search_podcastsfyyd, the open podcast directory — search podcast shows by title term, optionally restricted to a language code, up to 30 per page. Returns each show's fyyd podcast id, title, author, description, RSS feed URL, artwork and episode count. Answers which podcast shows exist under a name and where the RSS feed is.search_episodesfyyd, the open podcast directory — search individual podcast episodes, matching the term against episode titles and show-note descriptions, optionally filtered by language. Returns each episode's fyyd id, title, description, publication date, duration, audio enclosure URL and its parent podcast id. Answers which podcast episode covered a subject and where to listen to it.get_podcastPodcast metadata + recent episodes.get_podcast_by_urlResolve an RSS feed URL to its fyyd id.latest_episodesLatest episodes for a podcast.top_podcastsReturn the most popular podcasts on fyyd, optionally filtered by category slug and language code, with up to 30 results per call.categoriesCategory tree.
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.
Podwise
{
"mcpServers": {
"podwise": {
"url": "https://docs.podwise.ai/mcp"
}
}
}
Fyyd
{
"mcpServers": {
"fyyd": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-fyyd"
]
}
}
}
Frequently asked questions
Podwise is categorized under Podcasts and uses a remote HTTP/SSE transport. Fyyd belongs to Podcasts and uses a local stdio subprocess. Pick Podwise for podcasts work and Fyyd 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.
Podwise has no declared pricing — check the project's own site. Auth: oauth 2.0. Fyyd 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 podwise and fyyd as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Podwise has a quality signal of 60/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Fyyd has 56/100 (Good) with 1 views, 0 installs and 0 GitHub stars.