← Back to Podcli

Podcli vs SupoClip

Both are open-source. SupoClip's path leads to a hosted upsell. Podcli stays local-first, ships an MCP server, and adds a knowledge-base layer so the AI picks clips that sound like your show.

Open-source AI clipper with self-host and a hosted (waitlist) version. · Free to self-host. Hosted plan TBD.

Choose Podcli when

  • You want to stay local, with no hosted version to migrate to later.
  • You want an MCP server so Claude Code or Codex can run the pipeline.
  • You want the AI to score clips against your voice, banned words, and title formulas, not just generic virality heuristics.
  • You want captions as editable React/Remotion components, not template configs.
  • You'd rather one tool covered transcript → clip → caption → export.

Choose SupoClip when

  • You want a Docker-deployable hosted-style clipper for your team.
  • You plan to use SupoClip's hosted offering when it ships.
  • You prefer their UX and don't need the MCP/agent integration.

Side by side

The features that change the day-to-day for clip creators.

Feature
Podcli
SupoClip
License
MIT
Open source
Local processing
Yes
Yes (self-host)
Hosted upsell
None (local only)
Waitlist for hosted
MCP server
Yes (19 tools)
No
Knowledge base for AI scoring
Yes (13 markdown files)
No
Captions
Remotion (React components)
Built-in
Episode dedupe DB
Yes
No
PodStack slash commands
Yes (9 commands)
No

Same category, different center of gravity

SupoClip is the closest peer to Podcli in spirit. Both ship open-source clippers with a clear “not OpusClip” pitch. The difference is the long-term direction. SupoClip funds development with a hosted version (currently waitlist). Podcli stays local-first and funds nothing because there's nothing to fund.

That choice changes what you should expect over time. Hosted-first projects accumulate features that only matter at scale. Local-first projects accumulate features that matter for a single creator on a laptop. Pick the one whose future you want to use.

The MCP and PodStack layer

Podcli's MCP server exposes 19 tools to Claude Code, Claude Desktop, and Codex. You can say “clip this episode” and the agent handles transcription, scoring, cropping, captions, and export. PodStack adds slash commands for the surrounding workflow (plan episode, generate titles, descriptions, thumbnails, retro). SupoClip doesn't ship this layer. If you live in Claude Code, that's a real workflow difference.

Knowledge base for voice-aware clip scoring

Most clippers (including SupoClip) pick clips with a transcript heuristic. Podcli pipes the transcript plus 13 markdown files (your show's voice, banned words, title formulas, past learnings) to Claude or Codex, which scores each candidate on four dimensions. The episode database tracks which clips you've already shipped so the model doesn't repeat itself. This is the bigger differentiator once you've published a few episodes.

Questions about switching from SupoClip

Direct answers to the searches people run before they decide.

Is Podcli a fork of SupoClip?+

No. Independent projects with overlapping goals. Both target the same OpusClip-alternative niche but the codebases, architectures, and roadmaps are separate.

Which open-source OpusClip alternative should I pick?+

If you want a Docker-deployable, hosted-style clipper for your team, SupoClip's shape fits. If you want a single-creator local-first tool that plugs into your AI coding agent (Claude Code, Codex, Cursor) via MCP, Podcli fits.

Can both run on the same laptop?+

Yes. They don't share ports or processes. You can install and try both.

Try Podcli yourself

The setup script handles the toolchain. You'll have a clip out the other side in a few minutes.

$ git clone https://github.com/nmbrthirteen/podcli.git
$ cd podcli
$ ./setup.sh