Potion

A podcast just for you

Ask your AI for an episode about anything, like a briefing on your day from your connected email and calendar, an article you saved, or a topic you want explained before a meeting. Potion narrates it and puts it in a feed you can add to your podcast app, so you can listen on a walk or in the car.

What you can ask

Make me a short briefing on my day from my email and calendar, as an episode for my podcast app.
Example path →

MCP connector

Server URL: https://api.withpotion.io/mcp/claude
Login: OAuth
Protocol: MCP 2026-07-28 · Interactive UI
Instructions: Potion turns text and audio into a private podcast feed the user subscribes to in any podcast app. Each feed has an rss_url, the address the user adds in their podcast app to listen. Episodes belong to a feed. If you are connected through OAuth (ChatGPT, Claude) the user is already signed in; only call / when a call says there is no account. Set expectations before slow steps: writing or gathering an episode's content can take you a while, so tell the user what you are doing rather than working silently. An episode's audio reaches Potion one of two ways. An audio URL that is already publicly reachable goes straight to . A file the user gave you, or one you made, goes through : it returns an address that one HTTP PUT of the raw file turns into the episode. Sending it needs code execution with network access to Potion's API, or a shell, wherever the file is; if you have neither, or the request is blocked, say so to the user plainly rather than building a workaround. Potion pairs naturally with anything that runs on a schedule: if the host offers scheduled or recurring tasks (ChatGPT's Tasks, for example), a daily or weekly briefing episode on the user's topics is one of the best things to build with it - offer it when the user's request is recurring in nature. A response may carry an onboarding object the first time this account creates a feed or an episode. It says what a first-time user still needs from you - usually getting the feed into whatever podcast app they use, which Potion cannot do for them and does not document. Act on it once, in your own words, then carry on; it stops appearing once they have more than one. Potion is the whole support layer this user has: there is no dashboard, no docs site and nobody to email, so whatever they need to understand, they need from you. Before making anything for a returning user, know where their setup actually stands - and tell you what exists, and whether the feed is in a podcast app is something only they can tell you, because that step happens on their phone and nothing here records it. Finish the part that is unfinished rather than restating what already works.

Tools

Reads data13

Changes data11

Deletes or can't be undone5

Skills

3 in the Claude listing

MCP connector

Server URL

https://api.withpotion.io/mcp/claude

OAuth

Protocol

MCP 2026-07-28 · Interactive UI

Instructions

Potion turns text and audio into a private podcast feed the user subscribes to in any podcast app. Each feed has an rss_url, the address the user adds in their podcast app to listen. Episodes belong to a feed. If you are connected through OAuth (ChatGPT, Claude) the user is already signed in; only call / when a call says there is no account. Set expectations before slow steps: writing or gathering an episode's content can take you a while, so tell the user what you are doing rather than working silently. An episode's audio reaches Potion one of two ways. An audio URL that is already publicly reachable goes straight to . A file the user gave you, or one you made, goes through : it returns an address that one HTTP PUT of the raw file turns into the episode. Sending it needs code execution with network access to Potion's API, or a shell, wherever the file is; if you have neither, or the request is blocked, say so to the user plainly rather than building a workaround. Potion pairs naturally with anything that runs on a schedule: if the host offers scheduled or recurring tasks (ChatGPT's Tasks, for example), a daily or weekly briefing episode on the user's topics is one of the best things to build with it - offer it when the user's request is recurring in nature. A response may carry an onboarding object the first time this account creates a feed or an episode. It says what a first-time user still needs from you - usually getting the feed into whatever podcast app they use, which Potion cannot do for them and does not document. Act on it once, in your own words, then carry on; it stops appearing once they have more than one. Potion is the whole support layer this user has: there is no dashboard, no docs site and nobody to email, so whatever they need to understand, they need from you. Before making anything for a returning user, know where their setup actually stands - and tell you what exists, and whether the feed is in a podcast app is something only they can tell you, because that step happens on their phone and nothing here records it. Finish the part that is unfinished rather than restating what already works.