MCP server podcli
Commit 3 de nov. de 2026Transforma episódios longos de podcasts em clipes verticais curtos com rastreamento de rosto e legendas embutidas através de um agente de IA.
Também conhecido como nmbrthirteen/podcli
- Stars
- 89
- Ferramentas
- —
- Downloads, 30 dias
- —
- Versão mais recente
- —
- Último commit
- 3 de nov. de 2026
- Licença
- AGPL-3.0
O que é o MCP podcli?
podcli é um MCP server. Transforma episódios longos de podcasts em clipes verticais curtos com rastreamento de rosto e legendas embutidas através de um agente de IA.
Resumo gerado a partir do README do projeto
Sobre o MCP server de podcli
Transformar episódios longos de podcasts em clipes verticais curtos com rastreamento de rosto e legendas embutidas é o que o podcli permite para criadores de conteúdo. Esta ferramenta open-source permite que os usuários automatizem o processo tedioso de encontrar destaques, cortar o vídeo para seguir os falantes e adicionar vários estilos de legenda, como estilo karaokê ou layouts personalizados. Ele roda localmente no macOS, Linux e Windows, garantindo que a transcrição e a renderização aconteçam na sua própria máquina para manter a privacidade dos dados.
Desenvolvedores podem interagir com o sistema por meio de uma interface de linha de comando, um estúdio baseado na web em localhost:3847 ou conectando-o a um agente de IA via 32 MCP tools. Embora a transcrição e a renderização sejam locais, o clip scoring pode utilizar uma chave de API da Anthropic ou um login do Claude Code ou Codex. Para rastreamento avançado de falantes, o sistema pode se integrar ao AssemblyAI. O servidor suporta fluxos de trabalho complexos, incluindo sincronização multicam, áudio com normalização de loudness e exportação de timelines para softwares profissionais como Premiere ou Final Cut.
O que você pode fazer com ele
- 1Geração automatizada de clipesUm agente pode transcrever um episódio e renderizar automaticamente clipes curtos com legendas.
- 2Edição de episódios multicamSincronize múltiplos arquivos de câmera e microfone para criar um episódio completo e polido.
- 3Descoberta de destaques via IAUse IA para avaliar e identificar os momentos mais engajadores a partir de uma transcrição.
- 4Entrega de vídeo profissionalExporte suas edições como arquivos especializados para finalizar o trabalho manual no DaVinci Resolve.
Escrito a partir do README do projeto. Cada caso de uso é verificado com uma citação dele.
Verificações automatizadas
Executado em 14 de nov. de 2026Relatório completo →Ainda não verificado. Um servidor precisa de uma pontuação de 80, nenhum problema grave e dados suficientes para verificarmos. Como as verificações funcionam · O que corrigir para ganhar mais pontos
- Repositório de origem vinculado e acessívelnmbrthirteen/podcli is public and reachablegithub.com/nmbrthirteen/podcli ↗Passou
- O pacote indica este repositório como sua origemNão verificado
- Proveniência da build (atestação Sigstore)Não verificado
- Licença de código aberto (OSI)AGPL-3.0spdx.org/licenses/AGPL-3.0.html ↗Passou
- Commit ou release no último anoLast commit or release 2026-11-03github.com/nmbrthirteen/podcli ↗Passou
- OpenSSF ScorecardNão verificado
- Nome do pacote não é próximo a um pacote popularNão verificado
- Nenhum aviso crítico no pacote ou em suas dependênciasNão verificado
- Sem instruções ocultas para o modelo0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPassou
- Ferramentas destrutivas estão rotuladasNão verificado
- O endpoint remoto responde ao handshake do MCPNão verificado
README
Ver no 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.
Perguntas sobre o MCP podcli
O que o podcli faz?
Ele transcreve um episódio de podcast, seleciona os momentos que valem a pena ser clipados, faz o crop para o rosto visível e insere legendas para produzir clipes curtos.
Como conecto o podcli ao Claude Code ou Codex?
Execute podcli mcp install após uma configuração única do podcli; o comando registra o MCP server em qualquer CLI que esteja no seu PATH.
O podcli roda localmente ou na nuvem?
A transcrição e a renderização rodam na sua máquina por padrão, com chamadas de nuvem apenas para serviços opcionais como AI scoring, AssemblyAI ou podcli Pro.
Quantas ferramentas MCP o podcli expõe?
Ele expõe 32 MCP tools que permitem que um agente transcreva, avalie e renderize clipes por meio de conversa.
O podcli é gratuito e open source?
Sim, o podcli é lançado sob a licença AGPL-3.0 com exportações ilimitadas e sem marca d'água, e uma licença comercial está disponível sob consulta.