🎬 OpenCut Controller (MCP Server)

🌐 Leer en Español: README.es.md

By leveraging Playwright under the hood, this server seamlessly injects into the OpenCut browser environment, granting LLMs programmatic access to manipulate the timeline, scenes, media assets, rendering engine, and more—effectively turning OpenCut into an AI-driven, headless video editing powerhouse.

✨ Key Features

• 161 Comprehensive MCP Tools: Full programmatic control over OpenCut's core editing capabilities.
• Dual Transport Support: Connect locally via stdio (default) or integrate remotely via modern HTTP Streamable transport.
• Playwright Integration: Connects directly to the OpenCut web interface to manipulate application state in real-time.
• Contextual Resources: Inspect the editor's live state, current projects, and timeline tracks.
• Pre-built MCP Prompts: Ready-to-use templates for common high-level editing tasks.

🚀 Installation

Ensure you have Bun installed on your system.

# Clone the repository
git clone https://github.com/JXUE0/opencut-controller.git
cd opencut-controller

# Install dependencies (Playwright browsers will install automatically)
bun install

# 3. Patch the Local Editor:
# To enable MCP control, you need to apply small patches to the OpenCut source code. We provide an automated script for this:
bun run scripts/patch-editor.ts ../path-to-opencut

# 4. Install & Run Editor:
cd ../path-to-opencut
bun install
bun dev:web

💻 Usage

The server can be launched using two different transport protocols depending on your client environment.

1. stdio Transport (Default)

Ideal for standard local MCP clients like Claude Desktop.

bun run src/index.ts

2. HTTP Streamable Transport

Ideal for integrating with external workflow tools like n8n or remote services. The server listens at http://localhost:3002/mcp.

Linux / macOS (Bash):

TRANSPORT_TYPE=http PORT=3002 bun run src/index.ts

Windows (PowerShell):

$env:TRANSPORT_TYPE="http"; $env:PORT="3002"; bun run src/index.ts

🛠️ Available MCP Tools (161)

The controller exposes 161 highly granular tools to the LLM, categorized as follows:

📦 MCP Resources

Resources provide context directly to the LLM about the current state of OpenCut:

• opencut://projects - JSON array of all available OpenCut projects.
• opencut://editor/state - Live tracking of the active project, scene, playhead time, and playback status.
• opencut://timeline/tracks - Detailed breakdown of tracks in the active scene.

🤖 MCP Prompts

Quick-start templates for complex actions:

• create_intro_video - Automates creating a 10-second intro with text overlays.
• add_background_music - Searches the OpenCut sound library and trims music to fit.
• apply_transition - Seamlessly blends two clips with a specified effect.

🔌 Integrating with Claude Desktop

Make sure to replace /absolute/path/to/opencut-controller with the actual path on your local machine.

To connect OpenCut Controller to your local Claude Desktop app, add the following to your claude_desktop_config.json:

{
  "mcpServers": {
    "opencut-controller": {
      "command": "bun",
      "args": ["run", "src/index.ts"],
      "cwd": "/absolute/path/to/opencut-controller"
    }
  }
}

⚠️ Troubleshooting

• "Playwright browser not found": Ensure postinstall ran successfully. You can trigger it manually with bun run playwright install chromium.
• "PowerShell: The term 'TRANSPORT_TYPE=http' is not recognized": You are using bash syntax in Windows. Use $env:TRANSPORT_TYPE="http"; bun run src/index.ts instead.
• Connection Refused: Ensure OpenCut is open and accessible by Playwright.

🛠 Troubleshooting (Solución de problemas)

1. Error: window.__opencut is undefined

Cause: You are trying to use the MCP server with the production web app (opencut.app). Fix: You must run the OpenCut editor locally. The production site doesn't expose the internal hooks required for MCP control.

2. Error: Incompatible React versions

Cause: react and react-dom versions mismatch in the monorepo. Fix: Ensure both are set to the exact same version (e.g., 19.0.0) in the root package.json and run bun install.

3. Error: Invalid input: expected string, received undefined (Zod Error)

Cause: Missing environment variables in apps/web/.env. Fix: Ensure you have a .env file in apps/web/. We have updated the code to make most variables optional, but BETTER_AUTH_SECRET may still be needed for some features.

4. Connection Timeout

Cause: The local OpenCut server (Next.js) is still compiling. Fix: Wait until you see ✓ Ready in the editor terminal before starting the MCP server.

📄 Credits & Acknowledgments

This project's original codebase and concept were inspired by and built upon the foundational work done in RavenMeld/OpenCut-MCP. We extend our sincere gratitude to RavenMeld for their pioneering work on connecting OpenCut via the Model Context Protocol.

📄 License

This project is licensed under the MIT License.