Podwise

What Podwise MCP server does

Podwise MCP server gives AI agents access to podcast discovery and episode knowledge workflows. It can search podcasts and episodes, list followed shows and episodes, retrieve episode artifacts, and work with imported or processed audio. Episode information can include summaries, transcripts, chapters, highlights, Q&A, and mind maps where available through Podwise.

The server also supports questions across transcripts, episode translation, key-moment clips, and exports in Markdown or SRT. The bundled Podwise skill routes requests into workflows such as catch-up, weekly recap, episode notes, topic research, episode debate, language learning, and discovery. These workflows are useful for the 🎙️ Podcasts category when an agent needs more than a simple transcript lookup.

How it works

The service is hosted remotely at https://mcp.podwise.ai/mcp. It uses Streamable HTTP as its transport and OAuth 2.0 for authentication; this repository does not contain an API key. After authentication, the skill checks the connection with get_me and selects tools based on the request.

Podwise MCP server exposes 38 tools grouped around account access, search, library management, processing and import, episode artifacts, questions and answers, clips, exports, and Enterprise operations. Requests can search across episodes, inspect a particular episode, ask questions about transcript content, or produce files and notes for use elsewhere.

Setup and configuration

Plugin installation is documented for Claude Code, Cursor, and Codex. Claude Code uses its plugin marketplace commands, Cursor can import the GitHub repository through its plugin marketplace, and Codex uses its marketplace and plugin commands. Each route requires completing the OAuth flow when prompted.

Other agents can install the skill with npx skills add hardhackerlabs/podwise-plugin and add the remote server manually. The configuration uses type: "http" for Claude Code-style clients or type: "streamable-http" for Agent Plugins clients, with the Podwise endpoint as the URL.

A Podwise account and network access to the endpoint are required. Some functions need a Pro or Enterprise plan, while the enterprise_* tools are intended for Enterprise-plan API usage. OAuth uses a loopback callback, so authentication can fail when the host machine is separate from the browser, such as in some remote or SSH setups.

Tools and capabilities

The 38 tools include:

• Searching podcasts, episodes, and popular episodes.
• Listing followed podcasts, followed episodes, podcast episodes, and personal episode history.
• Following or unfollowing podcasts and marking episodes as read.
• Processing or importing episodes and uploading audio.
• Reading episode details, summaries, transcripts, and question history.
• Asking questions, translating episodes, and listing translations.
• Creating, reading, listing, deleting, exporting, and sending clips.
• Exporting episode notes as Markdown or subtitles as SRT.
• Processing, querying, translating, exporting, and checking usage for Enterprise workflows.

Podwise MCP server fits agents that need structured podcast research or repeatable listening workflows. It is less suitable when a local-only service, unauthenticated access, or an API-key-only setup is required.