flamexnreal/davinci-resolve-ai-bridge-mcp

Let your AI assistant help with the edit. Resolve AI Bridge connects Claude, Codex, Cursor, Antigravity, and other MCP-compatible assistants to the project open in **DaVinci Resolve Free or Studio**.
Inspect a timeline, place media, animate a zoom, adjust color, or try an edit on a duplicate timeline before touching the original.
Built to stay light
- **Works with Resolve Free.** No Studio license needed for the bridge. Individual tools still depend on your Resolve build; Studio-only effects stay Studio-only.
- **One click to start.** Choose **Start AI Bridge** in Resolve. Your AI gets the same tools and access as the old Console-paste workflow.
- **A small, local runtime.** No remote bridge server or manually entered token. Website dependencies stay out of the CLI package; FFmpeg and Remotion are optional.
- **Keep your tokens for the edit.** The launcher starts locally, without an AI request or extra startup tools.
> ⭐ Finding it useful? Give the bridge a star—it helps other editors find it.
---
Quick setup
You'll need **Python 3.10+** (download).
Option A: Run directly with npx (Recommended for Node / npm users)
Option B: One-line shell install
**macOS / Linux** (run in Terminal):
**Windows** (run in PowerShell):
From a downloaded/cloned repository, run python3 install.py --with-ffmpeg (Windows: py install.py --with-ffmpeg), or use install-macos.command / install-windows.bat for the base install.
Node/npm is only needed for the npm installer and optional website/motion-graphics development.
The installer sets up ~/.resolve-ai-bridge, a private Python environment, the Resolve menu entries, editing skills, and detected supported AI clients. Valid client configs are backed up and merged; invalid configs are left unchanged with a diagnostic. Antigravity and other clients can use the generated mcp-config.json manually.
Wait for **INSTALL COMPLETE**, then reopen Resolve. If setup stops after downloading, see installer troubleshooting.
Optional: add FFmpeg for source frames and audio
For Free-compatible source frame capture and efficient audio decoding, also install the optional private FFmpeg binary:
This optional download stays in the bridge's private Python environment. It is not a Studio dependency. An existing ffmpeg on PATH also works; macOS afconvert supports audio extraction without FFmpeg.
---
Connect to Resolve
1. Open **DaVinci Resolve** with a project.
2. Choose **Workspace → Scripts → Resolve AI Bridge → Start AI Bridge**. It may appear under **Utility**.
3. Ask your AI: **“Call resolve_status, then bridge_capabilities and timeline_overview.”** Open or create a timeline before using timeline tools; status works without one.
**Start from the menu and get editing.** Start once per Resolve session. You can see **RESOLVE AI BRIDGE READY** in **Workspace → Console**. Use **Stop AI Bridge** in the same menu to stop the worker; an active operation finishes first. Clicking Start again won't create another worker.
If the menu is missing after installation, quit and reopen Resolve once. Refresh/restart your AI client's MCP server after setup or a tool-schema update.
Menu startup is live-tested on **macOS / Resolve Free 21.0.3.7 / Python 3.14.6**. Windows, Linux, and other builds still need live verification; the Console fallback stays available.
Console fallback and startup details
If automatic startup reports an error on your build, open **Workspace → Console**, select **Py3**, paste this fallback command and press Enter:
**Live startup validation:** macOS, DaVinci Resolve **Free 21.0.3.7**, Python **3.14.6**: menu start, real status requests, repeated start, Stop, quit/reopen/start, and Console fallback passed. Windows/Linux and other Resolve builds still require live verification; the portable fallback remains available.
Resolve may keep the menu script marked busy while its separate fuscript process serves requests. Resolve's editing UI remains usable. Closing Resolve ends that process. The Console fallback uses a daemon worker with a startup handshake capped at one second. No new dependency, listening port, public MCP tool, or AI call is added.