Podcli vs ClipsAI

Short answer

ClipsAI is a Python library that gives you clip-detection and dynamic 9:16 reframing primitives. Podcli is the end-to-end product around the same idea: CLI, web UI, captions, AI scoring, MCP server.

  • 01AGPL-3.0 · the app is free
  • 02Local-first · files stay on your machine
  • 03No watermark · no monthly minute cap
  • 04CLI + web UI (:3847) + MCP (32 tools)
  • 05Whisper + Remotion captions · Claude or Codex scoring

ClipsAI: Open-source Python library for clip detection and 9:16 reframing. Free, MIT. Library, not a product. You build the UI yourself.

Updated October 29, 2026 · Nika Siradze

Podcli or ClipsAI

Pick Podcli when

  • You want a finished tool, not a library you need to compose.
  • You need burned-in captions out of the box.
  • You want a web UI with a 9:16 phone preview before export.
  • You want an MCP server so Claude Code can run the pipeline for you.
  • You want AI clip suggestion scored against your show's voice.

Pick ClipsAI when

  • You're building your own product and want clip-detection primitives in Python.
  • You only need the clip-finding step and already have your own captions/export stack.
  • You want a Python library you import, and no app to install.

Feature by feature

The rows that change the day-to-day for someone posting clips every week.

FeaturePodcliClipsAI
ShapeProduct (CLI + UI + MCP)Python library
LicenseAGPL-3.0MIT
TranscriptionWhisperWhisperX
Speaker diarizationPyannotePyannote
9:16 reframingYuNet + mouth-motion split-screenSpeaker-driven dynamic crop
Burned-in captionsYes (Remotion, 4 styles)No (BYO)
AI clip scoringClaude/Codex + knowledge baseNo (BYO)
Web UIYes (localhost:3847)No
MCP serverYes (32 tools)No
Stars at time of writingBuilding~487

Where the difference shows up

Library vs product

ClipsAI is excellent at what it sets out to do: it gives Python developers two primitives. One does clip detection from transcripts; the other does speaker-aware dynamic 9:16 reframing. You import it, you call it, you wire it into your own pipeline. The caption step, the UI, the export queue, and the AI ranking are all yours to build.

Podcli is the opposite shape: a finished pipeline. Same core building blocks (Whisper, Pyannote, face detection), plus the entire surface above them. Captions rendered via Remotion. A web UI with a 9:16 phone-frame preview. AI clip scoring against a knowledge base. An MCP server so Claude Code can drive it. If you don't want to build the wrapper, Podcli is the wrapper.

When ClipsAI is the right pick

If you're shipping your own clipping product or a hosted SaaS on top of clip-detection, ClipsAI is a sensible foundation. You get Python-native primitives without the rest of the opinionated pipeline. Podcli's opinions (Remotion captions, knowledge-base scoring, MCP server) become baggage if you already have your own answers.

What you'd have to build on top of ClipsAI

ClipsAI gives you two primitives: clip detection and 9:16 reframing. To turn that into a workflow you'd still write the caption renderer, the export pipeline, the review UI, and any AI ranking, plus the glue code and error handling around them. That's real engineering time.

Podcli is that work already done and maintained: Remotion captions, a web UI with a phone-frame preview, AI scoring against a knowledge base, and an MCP server. If you're building your own product, ClipsAI's primitives are a head start. If you just want clips, Podcli is the finished tool.

When Podcli is the right pick

If you are a podcaster or studio that wants the clips themselves, not a clip-detection toolkit, install Podcli and run the CLI. The pipeline is already there. Same goes for anyone who lives in Claude Code or Cursor and wants the agent to do the whole thing; that's what the MCP server is for.

Switching from ClipsAI

Something missing? support@podcli.com

Is Podcli a fork of ClipsAI?

No. Podcli is an independent project. It uses similar building blocks (Whisper, Pyannote, face detection) because that's the standard stack for this task, but the code, pipeline, captions, UI, and AI scoring layers are all separate.

Can I use Podcli without writing Python?

Yes. The CLI is a single command. The web UI is a browser app. The MCP server takes natural-language instructions. You only touch code if you want to edit a caption style (React/Remotion) or extend the knowledge base (markdown).

Does Podcli use the same dynamic reframing approach as ClipsAI?

Both use face/speaker detection to crop 16:9 → 9:16. Podcli adds a mouth-motion analysis for 2-person split-screen interviews so you don't need diarization for the camera framing, plus a scene-cut guard that suppresses jittery pans on B-roll-heavy clips.

Can I get captions out of ClipsAI like Podcli?

Not directly. ClipsAI returns clip ranges and reframed crops, and you bring your own captioning. Podcli ships burned-in word-level captions in five editable Remotion styles out of the box.