Opencut Controller
Automate OpenCut video edits—cuts, timelines, and export steps—through MCP while you ship content-heavy products.
Overview
OpenCut Controller is a Build-phase MCP server that automates professional video editing workflows inside OpenCut.
What is this MCP server?
- Professional MCP server for OpenCut video editing automation
- npm stdio package opencut-controller at v1.30.0
- Targets repeatable edit pipelines driven from coding agents
- stdio transport for Claude Code, Cursor, and similar clients
- Separates edit orchestration from manual timeline clicking
- Package version 1.30.0
- stdio transport via npm identifier opencut-controller
- No required env vars documented in server manifest
What problem does it solve?
Agent-assisted content shipping stalls when every video tweak still requires manual OpenCut timeline work.
Who is it for?
Indie builders producing frequent video who already use OpenCut and want agent-driven edit automation.
Skip if: Teams needing a full cloud render farm, non-OpenCut NLEs, or purely static blog content with no video.
What do I get? / Deliverables
Your agent can drive OpenCut editing steps through MCP so repeatable cuts and project changes run from the IDE.
- Agent-invokable OpenCut editing automation tools
- Reduced manual timeline work for repeatable video tasks
- Integration path from IDE to local NLE project control
Recommended MCP Servers
Journey fit
How it compares
OpenCut NLE automation via MCP, not a generative video model or social scheduling skill.
Common Questions / FAQ
Who is opencut-controller for?
Content-focused solo builders using OpenCut who want Claude Code or Cursor to run edit automation via MCP.
When should I use opencut-controller?
When building integrations for launch videos, courses, or recurring social clips that need scripted OpenCut operations.
How do I add opencut-controller to my agent?
Install the npm stdio server opencut-controller, ensure OpenCut is available locally, and add it to your MCP client server list.