proofcut MCP server

proofcut

<!-- mcp-name: io.github.tydude001/proofcut -->

An AI video editor that proves its cuts. Your recordings in, a finished, mastered film out: cut by transcript, with b-roll, cards, music and captions, and every step an agent can call. proofcut renders on your own machine, then transcribes the render and checks that it says what the edit says.

https://github.com/user-attachments/assets/4153d180-3d7c-4c70-af5f-54d63d0a8bd5

Above: an agent cutting a demo video, unattended. The two runs it was cut from, uncut (silent: the recorder took frames only, and the voice is in the film the agent cut): the workspace (2:26) and Claude Code with the proofcut plugin (3:09).

That is not a staged run. TRIAL.md scores three unattended ones, each handed a goal and no steps, and each passed every one of its checks:

plus four clips of film footage. The agent cut it to 45 seconds, chose footage by what each line was about, burned captions, and checked its own render: all 123 expected words heard back.

• The demo cut, the one above.
• Real footage. 96 seconds of narration with its fluffed takes left in,

film ready to upload. In 192 seconds and $2.27 the agent cut it, laid the music under the voice, ended on a card, mastered it to −16 LUFS, and checked it. The score, the level and the end card were each measured in the delivered file, not taken from the project.

• A whole film. The demo material plus a score, briefed as a finished

proofcut makes no footage and writes no script. It takes what you recorded to a film, and proves the film matches the edit.

How people use it

Tell an agent what film you want. In Claude Code, install the plugin and describe the film: which recording is the voice, what the b-roll is, where the music goes, what it ends on. The agent imports, transcribes, cuts the retakes, hangs footage off the lines it belongs to, scores, masters and checks the render, using proofcut's tools and nothing else. It can look at the picture track as a labelled grid while it works, so it sees what it placed rather than a filename. Every MCP client runs the same server; the plugin is the one that needs no setup.

/plugin marketplace add tydude001/proofcut
/plugin install proofcut@proofcut

Cut from a shell, by naming words. Every tool is also a proofcut subcommand printing JSON, so a cut is a script you can read, re-run and diff. --plan prints what a range says before anything changes, and undo walks it back.

uv run proofcut -C myproject cut vo 111:114 --plan

Edit by hand in the workspace. Strike words in the transcript, drag-trim and razor on the timeline, review every crop in place, and export from Finish. It plays the source through the edit, so seeing a cut costs no render, and the truth strip warns while you edit if the film would ship wrong. The agent sits in a side rail of the same window.

uv run proofcut -C myproject open

Finish elsewhere, and still prove the file. Rough-cut here, export a .kdenlive or OpenTimelineIO file, finish in Kdenlive, Resolve or Premiere, and bring the trim back with import-edit. Then point verify at the delivered file, and a retake left in is caught before anyone watches.

uv run proofcut -C myproject verify final.mp4

Cut a vertical teaser from the film. reel copies a span of the finished film into a second project at another canvas, so the film itself is never reshaped to take one render. It names every picture the teaser will not have and pins the ones it keeps to the frames the film showed, so the teaser shows what the film showed. Frame mode then reviews each crop on the source's own frames.

Shortened. The full README is on GitHub.