Audivo vs Pod Researcher
A side-by-side look at the Audivo and Pod Researcher MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Audivo for podcasts work as a local process; choose Pod Researcher 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 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.
Choose Pod Researcher when
- You need dedicated capabilities in the Podcasts domain.
- You prefer a local stdio subprocess transport.
- You want tools like
best_route, data_as_of, purpose.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Podcasts | Podcasts |
| Quality signal | 57/100 · Good | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | AUDIVO_API_KEYAUDIVO_API_BASE_URLAUDIVO_YTDLP_PATHAUDIVO_CACHE_DIR | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 13 | 6 |
| Full listing | View Audivo | View Pod Researcher |
Tools & capabilities
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
Pod Researcher tools 6
best_routedata_as_ofpurposeguestsponsorid
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.
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"
}
}
}
}
Pod Researcher
{
"mcpServers": {
"pod-researcher": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-pod-researcher"
]
}
}
}
Frequently asked questions
Audivo is categorized under Podcasts and uses a local stdio subprocess. Pod Researcher belongs to Podcasts and uses a local stdio subprocess. Pick Audivo for podcasts work and Pod Researcher 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.
Audivo has no declared pricing — check the project's own site. Auth: api key required. Pod Researcher 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 audivo and pod-researcher as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Audivo has a quality signal of 57/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Pod Researcher has 55/100 (Good) with 0 views, 0 installs and 0 GitHub stars.