Ask Claude or ChatGPT About Any Podcast: The MCP Setup That Works
What the Podwise MCP server actually gives you, how to connect it in Claude, ChatGPT, Cursor or Codex, and the prompts that produce citations instead of vibes.
Guide5 min read
The first time it works, it feels like a party trick. You paste an episode link into Claude, ask "what did the guest say about hiring?", and get an answer with a timestamp you can click. No tab switching, no copy-pasting a transcript into the chat.
It is not magic. The assistant is calling a tool that already has the transcript. That distinction matters, because it explains what the setup can and cannot do.
What MCP actually is
Model Context Protocol is a standard way for an AI app to call external tools. Podwise runs a server that exposes podcast operations as tools: search shows, read a summary, pull a transcript, ask a question across episodes, save a clip, send notes to Notion.
Your assistant decides which tool to call based on what you ask. You do not need to know the tool names, though they help when a request is vague.
Setup, in about two minutes
Claude and ChatGPT. Both have Podwise in their plugin directories. Install it, click Connect (or Authenticate), approve in the browser. The plugin includes the Podwise skill, which adds named workflows like catch-up and weekly recap. The step-by-step for each app is in the MCP guide.
Claude Code, Cursor, VS Code, Codex. Add the server URL:
https://mcp.podwise.ai/mcpMost clients prompt for OAuth on first use. Codex and Claude Code take a one-line command; Cursor and VS Code take a small JSON block. All of them are documented in the same guide.
Anything that cannot do OAuth. Create an API access token and send it as a Bearer header. This is the path for headless agents and CI.
One gotcha worth knowing up front: the MCP server needs a Pro or Enterprise plan. A free account can connect and will get a polite refusal on the first tool call.
The prompts that work
Vague prompts get vague answers. These four consistently produce something you can check:
Summarise with structure.
Summarise this episode and give me the chapters with timestamps: https://app.podwise.ai/dashboard/episodes/1234567
You get an overview, takeaways, and chapter times. Click two of them before you trust the rest.
Ask across shows.
What do podcasts in Podwise say about developer hiring? Give me the positions, who argues each, and the episodes they came from.
This uses Ask, which searches transcripts across shows and cites its sources. It is the one thing a chat assistant cannot do on its own, because the corpus is not in its context window.
Turn a stretch into notes.
Read the transcript from 12:00 to 18:00 and write five bullet points I could send to my team.
Good for the part of an episode you would otherwise re-listen to twice.
File it.
Send my notes on this episode to Notion.
Works when Notion is already connected in Podwise. Otherwise the tool will tell you it is not configured, which is a better failure than a silent one.
If you want the assistant to pick the workflow for you, install the plugin and just describe the job: "catch me up on this week" or "make flashcards from this transcript." The skills page lists what it can route.
What it cannot do
- Read an unprocessed episode. Someone has to process it first, which costs a credit on your account. Asking the assistant to process it is possible, but Claude and ChatGPT will ask you to confirm because it spends credits.
- Read a local audio file by magic. The server is remote. The upload flow hands you a link to pick the file in your browser, or an agent with shell access can upload it directly.
- Replace the reading experience for a 40-chapter episode. Chat is good at targeted questions. For browsing a whole episode, the web app's summary and transcript tabs are still faster.
When it beats the app, and when it doesn't
Use the assistant when the output is a sentence in another document: a Slack answer, a research note, a paragraph in a draft. The value is not needing to leave the chat.
Open the app when you want to read, scan chapters, save clips, or compare two episodes side by side. Chat is a poor interface for a 90-minute transcript; the transcript view with timestamps is a good one.
If it does not work
| Symptom | Likely cause |
|---|---|
| The assistant says it has no podcast tools | The plugin or server is not connected to this chat |
| Tools appear, every call fails | OAuth approval was never completed; reconnect |
| "Requires a paid plan" | Free account, or the feature is outside your plan |
| Notion send fails | Notion is not connected in Podwise settings |
The full per-client steps, including the custom-connector path for organisations, live in MCP Server. Start there rather than reinstalling things at random.
