MCP server de podcli
Commit 3 nov 2026Convierte episodios largos de podcast en clips verticales cortos con seguimiento de rostros y subtítulos integrados mediante un agente de IA.
También conocido como nmbrthirteen/podcli
- Stars
- 89
- Herramientas
- —
- Descargas, 30 días
- —
- Última versión
- —
- Último commit
- 3 nov 2026
- Licencia
- AGPL-3.0
¿Qué es podcli MCP?
podcli es un MCP server. Convierte episodios largos de podcast en clips verticales cortos con seguimiento de rostros y subtítulos integrados mediante un agente de IA.
Resumen generado a partir del README del proyecto
Acerca del MCP server de podcli
Transformar episodios largos de podcast en clips verticales cortos con seguimiento de rostros y subtítulos integrados es lo que podcli permite a los creadores de contenido. Esta herramienta de código abierto permite a los usuarios automatizar el tedioso proceso de encontrar momentos destacados, recortar el video para seguir a los interlocutores y añadir varios estilos de subtítulos, como estilo karaoke o diseños de marca. Se ejecuta localmente en macOS, Linux y Windows, garantizando que la transcripción y el renderizado ocurran en tu propia máquina para mantener la privacidad de los datos.
Los desarrolladores pueden interactuar con el sistema a través de una interfaz de línea de comandos, un estudio basado en web en localhost:3847, o conectándolo a un agente de IA mediante 32 herramientas MCP. Aunque la transcripción y el renderizado son locales, el scoring de clips puede utilizar una API key de Anthropic o un inicio de sesión en Claude Code o Codex. Para un seguimiento avanzado de los interlocutores, el sistema puede integrarse con AssemblyAI. El servidor admite flujos de trabajo complejos que incluyen sincronización multicámara, audio con normalización de sonoridad y exportación de líneas de tiempo a software profesional como Premiere o Final Cut.
Qué puedes hacer con él
- 1Generación automatizada de clipsUn agente puede transcribir un episodio y renderizar automáticamente clips cortos con subtítulos.
- 2Edición de episodios multicámaraSincroniza múltiples archivos de cámara y micrófono para crear un episodio completo y pulido.
- 3Descubrimiento de momentos destacados mediante IAUtiliza IA para puntuar e identificar los momentos más atractivos a partir de una transcripción.
- 4Entrega de video profesionalExporta tus ediciones como archivos especializados para finalizar el trabajo manual en DaVinci Resolve.
Escrito a partir del README del proyecto. Cada caso de uso se verifica con una cita del mismo.
Verificaciones automáticas
Ejecutado 14 nov 2026Informe completo →Aún no verificado. Un servidor necesita una puntuación de 80, ningún hallazgo grave y suficientes datos para que podamos revisarlo. Cómo funcionan las verificaciones · Qué corregir para obtener más puntos
- Repositorio de origen vinculado y accesiblenmbrthirteen/podcli is public and reachablegithub.com/nmbrthirteen/podcli ↗Aprobado
- El paquete indica este repositorio como su origenNo verificado
- Procedencia de la compilación (atestación de Sigstore)No verificado
- Licencia de código abierto (OSI)AGPL-3.0spdx.org/licenses/AGPL-3.0.html ↗Aprobado
- Commit o lanzamiento en el último añoLast commit or release 2026-11-03github.com/nmbrthirteen/podcli ↗Aprobado
- OpenSSF ScorecardNo verificado
- El nombre del paquete no es similar a un paquete popularNo verificado
- No hay avisos críticos en el paquete ni en sus dependenciasNo verificado
- Sin instrucciones ocultas para el modelo0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersAprobado
- Las herramientas destructivas están etiquetadasNo verificado
- El endpoint remoto responde al handshake de MCPNo verificado
README
Ver en GitHubpodcli process episode.mp4
That one command transcribes the episode, picks the moments worth clipping, crops to the visible face, and burns the captions in. Transcription and rendering run on your machine. Clip scoring uses Claude Code or Codex login, or an Anthropic API key; without those it falls back to heuristics.
Install
No prerequisites. The installer fetches a self-contained binary, and the first run provisions Python, Node, FFmpeg, whisper.cpp, and the models it needs into a managed folder.
macOS and Linux
curl -fsSL https://podcli.com/install.sh | sh
Windows (PowerShell)
irm https://podcli.com/install.ps1 | iex
Runs on macOS (Apple Silicon), Linux (x64 and arm64), and Windows (x64). Intel Macs aren't supported.
Quick start
podcli # interactive menu, opens the web studio
podcli process episode.mp4 # transcribe, pick moments, render clips
podcli multicam ~/ep12 # sync every camera and mic, cut to the speaker, render the episode
Clips land in podcli-clips/ in the directory you ran it from, so each show keeps its own renders. Everything else (knowledge, presets, assets, clip history, cache) lives in one managed folder that follows you between directories. Set PODCLI_OUTPUT to render somewhere fixed instead.
What you get
Clips
- 9:16, 16:9, or 1:1, with captions sized for each canvas
- Face tracking that follows the visible face, split-screen layouts included. Following the active speaker needs AssemblyAI, or a source install with openai-whisper and
HF_TOKEN - Multi-segment cuts that drop filler, long pauses, and tangents
- Four caption styles: branded, hormozi, karaoke, subtle
- Logos, intros, outros, and background music from a reusable asset library
- Loudness-normalized audio and hardware encoding on VideoToolbox and NVENC, with a CPU fallback
Editing the full episode
- Multicam edit: point at one folder of camera and mic files, confirm who each file belongs to, and podcli syncs them by audio and corrects clock drift between devices
- Automatic camera cuts that follow whoever is talking, with wide shots for crosstalk and a guest's answer held on the guest
- Remote shows too: one file per person becomes a split screen, and a single gallery recording is split into a camera per tile. Questions stay on the split and the guest goes full frame on long answers
- Render the episode as an MP4 with one WAV per person. Studio shoots can also go to Premiere or Final Cut as a timeline that points at your original files
- Same edit from the studio (Multicam edit), the CLI (
podcli multicam <folder>), or an agent (manage_multicam). Re-running reuses the sync and the cut, so only the step you changed runs again - With podcli Pro, steer the cut in the cloud editor:
podcli multicam <folder> --clouduploads per-camera proxies, a mic mix (about 550 MB for a two-hour, three-camera episode), and the transcript. Your original camera files stay on your computer, and--pullrenders the cut you made there
Finding the moments
- Whisper transcription (speaker diarization on AssemblyAI, or openai-whisper from a source install or
podcli setup --speakers), or bring your own transcript as.txt,.srt, or.vtt - AssemblyAI as an alternative engine, and yt-dlp to pull an episode straight from a URL
- AI scoring against your knowledge base, checked against your episode database so it stops resuggesting moments you already published
- Audio energy and laughter detection to build highlight reels
The studio at localhost:3847
- Library, episode workspace, multicam edit, per-clip detail, highlights, thumbnails, content, analytics, assets, knowledge, config, integrations, and MCP setup
⌘Kcommand palette across pages, clips, and assets- Titles, descriptions, tags, and hashtags, with any section regenerated on your own guidance
- Thumbnail studio for 16:9 and 9:16, with frame and text options
- Transcript corrections that carry through to every render
Shipping it
- 32 MCP tools, so an agent can transcribe, score, and render through conversation
- YouTube analytics to see which clips landed
- DaVinci Resolve export as FCPXML when you want to finish by hand
- Presets, clip history with duplicate detection, and a transcript cache
Why podcli
If you are weighing podcli against the cloud clippers, this is the difference:
- Runs locally. Transcription and rendering happen on your machine by default, so episodes stay there. Data leaves your machine only through these destinations:
- AssemblyAI, if you pick that engine: the episode audio.
- AI scoring and titles: the transcript goes to podcli Pro when you are signed in, to Anthropic when you set
ANTHROPIC_API_KEY, and to the provider behind your Claude Code or Codex login. - podcli Pro, when signed in: knowledge and asset sync, plus rendered clips and transcript slices if you turn on
PODCLI_CLOUD_SYNC=1(off by default). - YouTube, if you link it: read-only analytics requests.
- podcli multicam cloud, if you run
podcli multicam --cloud: per-camera proxies, a mic mix, and the transcript.
- Free and open source under AGPL-3.0. Exports are unlimited, full quality, and watermark-free.
- Agent-native. 32 MCP tools let Claude Code or Codex drive the whole flow, from transcription to rendered clips and publish-ready titles.
- A knowledge base keeps titles, captions, and descriptions in your show's voice, and stops the engine from resuggesting moments you already published.
- DaVinci Resolve handoff. Export any clip as FCPXML when you want to finish the edit yourself.
Use it from your agent
podcli is an MCP server, so an agent can transcribe, suggest clips, and render them through conversation.
podcli mcp install # registers it with Claude Code and Codex, whichever CLI is on PATH
--help and --version never download anything. First run of process, studio, transcribe, or multicam provisions the engine. podcli mcp does not, because stdout is JSON-RPC. Run podcli setup once before you point an agent at it.
podcli process episode.mp4 --json --yes
podcli doctor --json
--json writes one object to stdout and logs to stderr. -y/--yes skips prompts. NO_COLOR=1 (or a non-TTY) turns off colour and spinners.
rank_clip_candidates returns a shortlist so the agent does not have to read the whole transcript. process_episode runs the pipeline as one job; poll it with job_status. The workflow lives in SKILL.md. Tool names are generated into llms.txt.
Claude Desktop and Codex setup is in the MCP docs.
Content workflow
PodStack ships with podcli as a set of Claude Code slash commands. They take a transcript to a publish-ready package: scored moments, titles, descriptions, thumbnail briefs, a brand review, and a publish checklist.
/produce-shorts
The commands live in .claude/commands/. CLAUDE.md describes each one.
Docs
| Guide | What's in it |
|---|---|
| Getting started | Install, first episode, the whole flow |
| The studio | Web UI: library, episodes, content, highlights |
| CLI | Commands, flags, presets, assets |
| MCP server | Agent setup and available tools |
| Captions and formats | Styles, aspect ratios, cropping |
| Configuration | Environment variables, config profiles, transcript format |
Docs are open source at nmbrthirteen/podcli-docs.
Contributing
See CONTRIBUTING.md for the dev setup and conventions, and RELEASE.md for how releases are cut.
Credits
Content workflow powered by PodStack, inspired by gstack by Garry Tan.
License
AGPL-3.0. See LICENSE.
Need podcli without AGPL terms? A commercial license is available. Email siradze@nikusha.me with a one-line description of your use case.
Preguntas sobre podcli MCP
¿Qué hace podcli?
Transcribe un episodio de podcast, selecciona los momentos dignos de ser recortados, realiza el recorte al rostro visible e integra subtítulos para producir clips cortos.
¿Cómo conecto podcli a Claude Code o Codex?
Ejecuta podcli mcp install después de realizar una configuración inicial de podcli; el comando registra el MCP server con cualquier CLI que esté en el PATH.
¿podcli se ejecuta localmente o en la nube?
La transcripción y el renderizado se ejecutan en tu máquina por defecto; las llamadas a la nube solo se realizan para servicios opcionales como el scoring de IA, AssemblyAI o podcli Pro.
¿Cuántas herramientas MCP expone podcli?
Expone 32 herramientas MCP que permiten a un agente transcribir, puntuar y renderizar clips mediante una conversación.
¿Es podcli gratuito y de código abierto?
Sí, podcli se lanza bajo la licencia AGPL-3.0 con exportaciones ilimitadas y sin marca de agua; una licencia comercial está disponible bajo petición.