OpenCut Rebuilds Its Video Editor Around MCP

OpenCut picked up about 14,800 GitHub stars in July while rebuilding its core around an MCP server, per its GitHub repo.

Automating video edits usually means scripting around a GUI never built for it, or fighting an SDK bolted on after the fact. OpenCut's MCP server skips both. An agent can call the editor the same way it calls any other tool, no GUI required.

Most video editors treat automation as an afterthought, a macro here, an export plugin there. OpenCut restructured around APIs, plugins, and headless automation instead, with MCP as the interface agents use to reach the timeline directly.

The open source CapCut alternative is still a video editor first. It's just one of the first consumer creative tools to treat agent control as a first-class interface rather than a bolt-on.

I'd bet the split in creative software from here runs between two camps. One keeps agent access as a side feature. The other builds the interface around it, the way OpenCut just did. Bolt-on automation is going to feel brittle next to a tool designed for agents from the start.

What OpenCut's repo doesn't say yet is how much of the editor's feature set is reachable through MCP. Effects, transitions, and color work might still be locked behind the GUI.