Podwise vs Dibatto
A side-by-side look at the Podwise and Dibatto 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 Dibatto for podcasts over a hosted endpoint. 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 Dibatto 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 | 60/100 · Good | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | OAuth 2.0 | OAuth 2.0 |
| 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 | Not listed |
| Full listing | View Podwise | View Dibatto |
Tools & capabilities
Podwise tools
No tool names declared yet. Check the project README from the listing page.
Dibatto 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.
Podwise
{
"mcpServers": {
"podwise": {
"url": "https://docs.podwise.ai/mcp"
}
}
}
Dibatto
{
"mcpServers": {
"dibatto": {
"url": "https://soxoa.com/mcp"
}
}
}
Frequently asked questions
Podwise is categorized under Podcasts and uses a remote HTTP/SSE transport. Dibatto belongs to Podcasts and uses a remote HTTP/SSE transport. Pick Podwise for podcasts work and Dibatto 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. Dibatto 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 podwise and dibatto 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. Dibatto has 56/100 (Good) with 1 views, 0 installs and 0 GitHub stars.