kimo
A free, open-source headless video editor written in Rust that AI agents drive over MCP, with every edit exposed as a tool call.
At a Glance
Free, MIT-licensed open-source video editor with no GUI, driven by AI agents over MCP. Runs locally on CPU and requires FFmpeg and FFprobe on PATH.
Engagement
Available On
Listed Nov 2026
About kimo
kimo is an open-source (MIT) video editor with no editing GUI, written in Rust and built by Naman. AI agents connect to it over the Model Context Protocol, and cutting, keyframing, grading, tracking, captioning, audio mixing and export are all tool calls. The latest release listed is v3.0.0, with installers for Windows and Linux and a build-from-source path for macOS.
What It Is
kimo ships as kimo-mcp, an MCP stdio server of roughly 15 MB with a CPU-only renderer that the docs say is tuned for a 2 GB machine. It needs ffmpeg and ffprobe on the PATH for decoding, encoding and probing media. The project's FAQ describes it as an early engine and points to FEATURES.md in the repository for which capabilities are solid, beta or not yet built.
How the Workflow Runs
You register the kimo-mcp binary with an MCP client (docs cover Claude Code, Codex CLI, Cursor and OpenCode, plus any generic stdio client), then describe edits in plain language. The agent translates them into calls such as trim, grade, caption and export. kimo renders on the CPU through FFmpeg and saves an editable project file alongside the output video, so edits can be reopened and re-rendered.
By default the server lists tools in 17 groups to keep agent context small, and agents find specific tools with search_tools and kimo_describe. The KIMO_TOOLS variable switches to core or flat profiles that list more tools up front. The README describes 376 registered tools across areas including editing, motion, compositing, text, 3D VFX, tracking, color science, audio and output.
Spectator App and CLI
The repository also includes a read-only Tauri spectator app that shows the agent's tool calls, timeline and preview frames live over loopback telemetry. A kimo command-line client can call the same tools directly against a project file. Per the FAQ, kimo runs locally as a stdio server and talks only to the agent that launched it.
Platform Notes
Linux x86_64 is the documented tested platform. The Windows installer is not code-signed and is marked unverified, so SmartScreen shows a warning. There is no prebuilt macOS binary.
Community Discussions
Be the first to start a conversation about kimo
Share your experience with kimo, ask questions, or help others learn from your insights.
Pricing
Open Source (MIT)
Free, MIT-licensed open-source video editor with no GUI, driven by AI agents over MCP. Runs locally on CPU and requires FFmpeg and FFprobe on PATH.
- MIT license, free to use, change and ship
- Headless Rust engine; every edit is an MCP tool call
- Works with any MCP client (Claude Code, Codex CLI, Cursor, OpenCode)
- CPU only, no GPU required
- Needs FFmpeg and FFprobe on PATH
Capabilities
Key Features
- Headless video editing driven entirely by MCP tool calls
- Cut, trim, keyframe, color grade, tracking, keying, captioning, audio mixing and export
- CPU-only rendering through FFmpeg
- Editable project files saved after each render
- Grouped, core and flat tool list profiles via KIMO_TOOLS
- On-demand tool discovery with search_tools and kimo_describe
- Optional read-only spectator app showing live tool calls and preview frames
- Command-line client for the same tools
- 3D scenes, particles, masks and text animators
- Runs locally over stdio
