kimo / install · v6.0.0 · take 01
TC 00:00:00·MIT · Rust · MCP

Two minutes. First frame.

Pick your machine and your agent. We write every command for you.

begin
01 machinewindows · 03 agentclaude code · 02 engineffmpeg ready
~15 MB binary · cpu only · stdio

01 your machine

Pick your machine.

One ~15 MB CPU-only Rust binary, kimo-mcp, that runs over stdio.

Run the installer to place kimo-mcp.exe on your machine.

download windows installer ↓

note on Windows SmartScreen: the installer is not code-signed yet, so Windows SmartScreen shows a warning: click “More info” then “Run anyway”.

02 ffmpeg

Put FFmpeg on PATH.

kimo needs ffmpeg and ffprobe on PATH. Run the one-line install for your OS, then verify.

install ffmpeg
winget install Gyan.FFmpeg
verify
ffmpeg -version && ffprobe -version

03 your agent

Point your MCP client.

Pick your agent and confirm the absolute path to kimo-mcp.

setup method
--scope

user = all your projects

Claude Code · claude mcp add (--scope user)
verify kimo is connected
claude mcp list

and inside a Claude Code session type /mcp to see kimo connected.

04 first render

Say this to your agent.

No timeline to drag. Just direction. Pick a prompt below to watch the MCP tool calls resolve into a rendered frame.

claude code
>
“use kimo to import /path/to/clip.mp4, add a title that says hello, and render a frame so I can see it”
  1. import_media(src: "/path/to/clip.mp4", track: 1)00:00:00:08
  2. add_title(text: "hello", font: "Inter", weight: 600)00:00:00:19
  3. keyframe(opacity: 0 → 1, ease: "cubic-out")00:00:01:07
  4. render_frame(at: "00:02.00", out: "frame.png")00:00:02:00
Rendered frame preview
→ frame.png · film.kimo.json

05 if something breaks

If something breaks.