Podcli clips podcasts from
Claude Code
Direct answer
Add Podcli. Tell your agent to clip the episode.
26 local tools for Claude Code, Codex, Cursor, and more.
- 01AGPL-3.0 · free, no paid tier
- 02Local-first · files stay on your machine
- 03No watermark · no monthly minute cap
- 04CLI + web UI (:3847) + MCP (26 tools)
- 05Whisper + Remotion captions · Claude or Codex scoring
You talk to the agent. The agent calls Podcli.
The 26 tools, grouped by stage
The agent picks the path.
Ingest
5 toolstranscribe_podcasttranscribe_startset_videoimport_transcriptparse_transcriptScore
6 toolssuggest_clipsanalyze_energymodify_cliptoggle_clipknowledge_baseclip_historyRender
8 toolscreate_clipbatch_create_clipsmanage_presetsupdate_settingsmanage_assetslist_outputsmanage_thumbnail_configmanage_reelOps
4 toolsjob_statusget_ui_statemanage_envai_cli_statusIntegrate
3 toolsmanage_integrationsexport_to_davinci_resolvemanage_configAdd Podcli to Claude Code
The MCP config is one block. Same shape for Claude Code, Claude Desktop, and Codex.
// claude_desktop_config.json (same shape for Codex) { "mcpServers": { "podcli": { "command": "podcli", "args": ["mcp"] } } }
What you actually say to the agent
Natural language. The agent reads the tool list and figures out the call sequence.
Why not just use a generic FFmpeg MCP
Same prompt, two tool surfaces. The agent does less work when the tools already speak podcast.
Honest limits
The MCP server is podcast-clipping primitives, not a generic video editor.
- Not a full episode editor (use Descript or a DAW for that).
- First setup installs a local toolchain; hosted tools are faster on day one.
- AI clip scoring needs your own Claude or OpenAI key (optional).
Frequently asked
The questions people search before they wire Podcli into their MCP client.
What is the Podcli MCP server?+
Podcli ships as a Model Context Protocol (MCP) server with 26 tools that cover the full podcast-to-clip pipeline: transcription, AI clip scoring against a knowledge base, face-tracked 9:16 cropping, burned-in captions via Remotion, and hardware-accelerated export. It works with any MCP client, including Claude Code, Claude Desktop, Codex, and Cursor, and the agent runs the whole flow.
How do I add Podcli to Claude Code?+
Install Podcli (curl -fsSL https://podcli.com/install.sh | sh), then run 'podcli mcp install' to register it with Claude Code. For Claude Desktop, add a 'podcli' entry running 'podcli mcp'. Full instructions are in the repo README.
Does the MCP server send my podcast files anywhere?+
No. The MCP server runs locally as a process the agent talks to. The video, transcript, and renders all stay on your machine. The only network calls are the optional Claude or Codex API calls when you use AI clip scoring.
What can I ask the agent to do?+
Anything the 26 tools cover: 'transcribe episode.mp4', 'suggest the top 8 clips', 'change clip 3 to the karaoke caption style', 'render all selected clips in 1080x1920', 'show me clips that look similar to what I already shipped'. The agent picks the right tools and chains them.
Is this different from a CLI?+
Yes. The CLI is a fixed command; the MCP server exposes the same pipeline as discrete tools the agent composes on demand. Both ship in the same install, and you can use either or both.
What models work with Podcli's MCP server?+
Any MCP-compatible client. Tested with Claude Code, Claude Desktop, and Codex. Any agent that speaks MCP can read the tool list and call it.
Wire Podcli into Claude Code
Clone the repo, run the setup script, then point your MCP client at the built server.