{"id":5908,"date":"2026-11-14T22:13:31","date_gmt":"2026-11-14T19:13:31","guid":{"rendered":"https:\/\/mubert.com\/blog\/podcast-editing-ai-cast-mcp-agents"},"modified":"2026-11-14T22:14:06","modified_gmt":"2026-11-14T19:14:06","slug":"podcast-editing-ai-cast-mcp-agents","status":"publish","type":"post","link":"https:\/\/mubert.com\/blog\/podcast-editing-ai-cast-mcp-agents","title":{"rendered":"Podcast Editing AI That Asks Before It Spends: Let Claude, Cursor or n8n Cut Your Episode Through Cast","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"\n

Podcast editing AI in Cast plays you 30 seconds of your own episode, already edited<\/a>, about a minute after upload. Now Claude, Cursor or n8n can run it for you through one URL, https:\/\/cast-mcp.mubert.com\/mcp<\/code>, approved once in the browser. That’s it. The agent then cuts the episode to the length you asked for, puts music under it and exports. This post covers podcast editing with AI from setup to export for people who cut their own shows: what the agent can do, what it can’t, and the switch that keeps it away from your credits.<\/p>\n\n\n\n

Editing a talk show by hand is forensic work. You zoom the waveform until one “um” looks like a mountain range. You delete it, play it back and find the guest now sounds like a time machine interrupted them. We did this for years. Our worst evening went on one sentence, which we then cut entirely.<\/p>\n\n\n\n

\"Podcast\"Podcast<\/figure>\n\n\n\n

Podcast editing AI now plugs in through MCP, not a plugin<\/h2>\n\n\n\n

Cast speaks MCP, the Model Context Protocol, which its own docs call “an open-source standard for connecting AI applications to external systems”<\/a>. In plain words, it lets an assistant press buttons in another app instead of telling you which buttons to press. Cast’s docs say any MCP client works<\/a>: Claude Code, Claude Desktop, Cursor, Windsurf, VS Code, n8n, or your own code.<\/p>\n\n\n\n

The MCP docs compare the protocol to a USB-C port. That is fair, although USB-C has never asked us whether it may spend money.<\/p>\n\n\n\n

For podcast editing, AI used to mean a magic button inside one app, and you clicked it there or nowhere. With MCP, the podcast editing itself becomes a set of tools any AI assistant can call: import, transcribe, plan cuts, build the project, export. So the assistant that already writes your show notes can also cut the show. Cast’s docs even list “many episodes at once” among the jobs an agent handles. A whole season, then.<\/p>\n\n\n\n

There is a catch, and Cast’s docs state it themselves: “an agent spends faster than a person”. We come back to that below, because trust in the whole setup depends on it.<\/p>\n\n\n\n

Connecting Claude, Cursor or n8n to Cast takes one URL<\/h2>\n\n\n\n

Setting up podcast editing AI in Cast takes one address and one approval in the browser. No token to copy, unless your client can’t open a browser. The first time the assistant uses the server, a Cast page opens. Sign in and click Allow. Cast then creates a token for that one assistant and lists it in Settings \u2192 API & MCP, where you can revoke it any time.<\/p>\n\n\n\n

For Claude Code it is one command:<\/p>\n\n\n\n

claude<\/span> mcp add --transport<\/span> http cast https:\/\/cast-mcp.mubert.com\/mcp<\/span><\/code><\/pre>\n\n\n\n
The other clients differ in where the URL goes:<\/p>\n\n\n\n