Podwise vs Audivo
A side-by-side look at the Podwise and Audivo 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 Audivo 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 Audivo when
- You need dedicated capabilities in the Podcasts domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
AUDIVO_API_KEY, AUDIVO_API_BASE_URL, AUDIVO_YTDLP_PATH, AUDIVO_CACHE_DIR. - You want tools like
transcribe, search_shows, chart_shows.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | P Podwise | |
|---|---|---|
| Category | Podcasts | Podcasts |
| Quality signal | 60/100 · Good | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | OAuth 2.0 | API key required |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | AUDIVO_API_KEYAUDIVO_API_BASE_URLAUDIVO_YTDLP_PATHAUDIVO_CACHE_DIR |
| 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 | 13 |
| Full listing | View Podwise | View Audivo |
Tools & capabilities
Podwise tools
No tool names declared yet. Check the project README from the listing page.
Audivo tools 13
transcribeThe default.** One episode in, its transcript out, a page at a timesearch_showsFind shows by name, host, or topicchart_showsThe current chart for a categorylist_episodesA show's episodes, newest firstquotePrice a selection of many episodes before anything runsconfirmTurn a quote into a job groupgroup_statusWhere a group's jobs are, and which transcripts are readylist_groupsYour recent groupscancel_groupStop what has not started and release its creditsread_transcriptA job's transcript, a page at a time; waits for a running joblist_transcriptsYour recent transcripts, with their titlesupload_audioAnnounce and upload a file from this machine- +1 more on 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.
Podwise
{
"mcpServers": {
"podwise": {
"url": "https://docs.podwise.ai/mcp"
}
}
}
Audivo
{
"mcpServers": {
"audivo": {
"command": "npx",
"args": [
"-y",
"@audivo/mcp@latest"
],
"env": {
"AUDIVO_API_KEY": "YOUR_AUDIVO_API_KEY_HERE",
"AUDIVO_API_BASE_URL": "YOUR_AUDIVO_API_BASE_URL_HERE",
"AUDIVO_YTDLP_PATH": "YOUR_AUDIVO_YTDLP_PATH_HERE",
"AUDIVO_CACHE_DIR": "YOUR_AUDIVO_CACHE_DIR_HERE"
}
}
}
}
Frequently asked questions
Podwise is categorized under Podcasts and uses a remote HTTP/SSE transport. Audivo belongs to Podcasts and uses a local stdio subprocess. Pick Podwise for podcasts work and Audivo 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. Audivo has no declared pricing — check the project's own site. Auth: api key required. 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 audivo 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. Audivo has 57/100 (Good) with 1 views, 0 installs and 0 GitHub stars.