Op3 MCP vs Podwise
A side-by-side look at the Op3 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 Op3 MCP for podcasts work as a local process; 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 Op3 MCP 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:
OP3_API_TOKEN. - You want tools like
op3_get_show, op3_show_downloads, op3_episode_downloads.
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 | 63/100 · Good | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | OAuth 2.0 |
| Pricing | Free | Not declared |
| Required env vars | OP3_API_TOKEN | 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 | 6 | Not listed |
| Full listing | View Op3 MCP | View Podwise |
Tools & capabilities
Op3 MCP tools 6
op3_get_showLook up a podcast show on OP3 and get its UUID, title, podcast GUID, and stats page URL. Pass a show UUID, a podcast:guid, or a base64-encoded feed URL. This is the entry point: most other tools need the show UUID this returns. Set include_episodes to also list episodes (id, title, pubdate).op3_show_downloadsGet a show's recent download summary from OP3: monthly downloads, a week-by-week breakdown, and the average weekly downloads. Use this for 'how many downloads does my show get' questions. Needs a show UUID (from op3_get_show).op3_episode_downloadsGet per-episode download counts for a show from OP3: for each recent episode, downloads in the first 1/3/7/30 days after publish and all-time. Good for comparing how episodes perform. Needs a show UUID. Use limit to cap how many episodes come back.op3_top_appsGet the top podcast apps and players downloading a show, from OP3, over the last three calendar months. Returns each app with its download count and percent share. Answers 'what apps do my listeners use'. Needs a show UUID.op3_top_countriesGet the top listener countries (or regions) for a show. NOTE: OP3 has no native geography query, so this counts raw download records and aggregates by country client-side. It is a representative sample, not an exact lifetime total. OP3 returns raw records oldest-first, so to keep the sample recent this tool defaults to the last `window_days` days (90) when you do not pass an explicit start. Each result has a download count and percent share. Needs a show UUID. Keep max_records modest to stay fast and within rate limits.op3_downloads_timeseriesFetch raw download records for a show from OP3 over a date range. Returns individual download events (time, country, app, device). This is the low-level feed behind the other tools. Use it when you need to filter by episode or a specific date window. Keep limit low (records are verbose). For totals or geography summaries, prefer op3_show_downloads / op3_top_countries.
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.
Op3 MCP
{
"mcpServers": {
"conorbronsdon-op3-mcp": {
"command": "npx",
"args": [
"-y",
"@conorbronsdon/op3-mcp"
],
"env": {
"OP3_API_TOKEN": "YOUR_OP3_API_TOKEN_HERE"
}
}
}
}
Podwise
{
"mcpServers": {
"podwise": {
"url": "https://docs.podwise.ai/mcp"
}
}
}
Frequently asked questions
Op3 MCP is categorized under Podcasts and uses a local stdio subprocess. Podwise belongs to Podcasts and uses a remote HTTP/SSE transport. Pick Op3 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.
Op3 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-op3-mcp and podwise as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Op3 MCP has a quality signal of 63/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.