Claude Podcast MCP: Setup and 5 Recipes

To give Claude a podcast it can write into, add Reducer’s MCP server, https://mcp.reducerai.com/mcp, as a custom connector and sign in once. From then on, Claude can push text into a show’s inbox, publish a one-off episode, or set a schedule, and the audio arrives in the private RSS feed your podcast app already follows. The rest of this guide covers setup and five recipes that make the connection worth keeping.

Hand your podcast to your AI assistant explains why this works. This piece is the practical version: what to click, what to say, and what Claude actually does on your behalf.

Set up the connector

You need a Reducer account and a show. The quickest show to start with is Morning Brief, which creates a scheduled daily episode with headline and market updates, optional local weather, and a sample episode. Subscribe to its private feed in Apple Podcasts, Overcast, Pocket Casts, or any app that accepts a feed URL. The daily briefing guide walks through that part.

Then connect Claude:

1. Open Claude’s connector settings and choose to add a custom connector. On Pro and Max plans this lives under Connectors; on Team and Enterprise plans an admin adds it in the organization’s connector settings.
2. Name it Reducer and paste https://mcp.reducerai.com/mcp as the server URL.
3. Save, then connect. Claude opens Reducer’s sign-in page. Log in with your Reducer account and approve access.

The connection uses OAuth, so there is no API key to copy or store in a chat. Any other MCP-capable client that supports remote servers with OAuth can connect the same way.

To check it worked, ask Claude: “List my Reducer podcasts.” It should name your shows. If it does, every recipe below is one sentence away.

One setting that makes the inbox matter

Morning Brief is template-built. Each episode is assembled from widgets in a fixed order: headlines, markets, weather. Text Claude sends lands in the show’s inbox, and a template-built show only reads the inbox if its template includes a Grab from inbox widget. Add one in the show’s template editor and choose how many items it may take. Place it where you want saved material to play, usually after the recurring updates.

Skip this step and your segments wait in the inbox without reaching an episode. With it, the next scheduled build picks them up. The podcast inbox model covers why capture and publishing are separate steps.

Recipe 1: Send today’s research to tomorrow’s briefing

This is the core move. You finish working through something with Claude, a paper, a contract clause, a comparison of two tools, and you want to hear the result on tomorrow’s walk instead of losing it in chat history.

Say: “Write a three-minute spoken summary of what we just worked out and add it to my Morning Brief inbox.”

Claude writes the summary as prose meant for the ear and pushes it as a segment. It can also add a one-line spoken intro so the episode signals the change of topic before the segment starts. Nothing publishes yet. The segment waits until the next scheduled build, when the Grab from inbox widget pulls it in after the headlines.

Ask for spoken prose explicitly. Tables, bullet lists, and links read poorly aloud, and Claude does better when it knows the output will be heard.

Recipe 2: Check before you repeat yourself

If you send research to the same show for weeks, you will eventually send something it has already covered. Reducer gives Claude a semantic search over past segments for exactly this.

Say: “Before you add that, search my Reducer segments to see if we’ve covered it already.”

A strong match means the topic is probably a duplicate. Claude can then skip the push, or write only what is new since the earlier segment. This recipe pairs well with the first one; you can ask for both in a single sentence.

Recipe 3: Make an episode right now

Sometimes the briefing can’t wait for tomorrow. You are about to drive to a meeting and want the background in your ears before you arrive.

Say: “Make a short Reducer episode on the Henderson account history and publish it now, with show notes.”

Claude can push several segments, compile them, and publish in one step. It writes show notes too, so the episode in your podcast app has a description. Audio generation runs in the background. Claude can check the episode’s status, and the finished file appears in the same private feed as your briefing.

For this recipe, use a show that builds from its inbox rather than your template-built Morning Brief, so the one-off episode doesn’t take the morning slot. Claude can create a second show for you if you ask.

Recipe 4: Turn a topic into a course

Some subjects don’t fit one episode. You want to learn the basics of options pricing, or the history of a region before a trip, a little at a time.

Say: “Create a ten-lesson Reducer course on options pricing for a beginner, each lesson about five minutes, on a new show called Options 101. Release one lesson each weekday at 7am.”

Claude authors the lessons, attaches the course to the show, and sets the schedule. Each scheduled episode carries the next lesson until the course runs out. Claude can append lessons later if you want to keep going. Keep a course on its own show. A course switches the show to template building, so it shouldn’t share a show with ad-hoc inbox pushes. Make a course that arrives one lesson a day goes deeper on the format.

Recipe 5: Let Claude pace the inbox

Every show has a daily audio budget. When the inbox holds more than one episode can carry, Reducer keeps the extra segments for a later run, so one heavy day doesn’t produce a forty-minute episode.

Claude can read the inbox with an estimated length for each segment, alongside the show’s budget and how much audio is already queued. That lets it pace itself.

Say: “Look at my Morning Brief inbox. If tomorrow’s episode is already full, trim what you add to fit, or tell me what will roll over.”

This is the recipe that keeps a long-running habit listenable. You stop being the person who manages the queue. Claude reports what is waiting, and you decide whether anything should be cut.

What Claude can and can’t change

The connector reaches your Reducer shows and nothing else. Claude can list and create shows, push and search segments, compile and publish episodes, edit an episode’s title and show notes, build and share courses, and set a show’s schedule. It acts with your account’s access, inside your account’s plan limits.

It does not read your podcast app, and it does not fetch web pages on Reducer’s behalf. If you want an article in the briefing, Claude needs the article’s content in the conversation first, then it writes the spoken version and sends that. Reducer voices the text it receives.

Your feed stays private. The RSS address is a long private URL, so treat it like a password and share it only with people you want listening. How private RSS podcast feeds work explains the details.

Start with one recipe

Most people get value from the first recipe alone: the useful end of a conversation becomes part of tomorrow’s commute. Add the Grab from inbox widget, connect Claude, and send it one summary today. Start a Morning Brief in Reducer, and the next good answer Claude gives you will have somewhere to go.