Blackmagic Design · 21.1.1
DaVinci Resolve and AI: scripting API, MCP and edition limits
AI agents can work in DaVinci Resolve through scripting and timeline files, with native MCP available in Studio 21.1 and later. Free and Studio have different automation boundaries, so choose the edition and platform route before connecting an assistant.
Best route: Use native MCP in Studio 21.1; free-edition Lua and timeline-file routes have narrower version and platform limits.

Ravi Parikh, Co-founder, Voyager
Can an AI agent drive DaVinci Resolve?
On Studio, an agent can build and restructure timelines, organise media, apply LUTs and CDLs, add transitions and fades, transcribe, generate Fusion comps and run unattended renders, all through a documented API and a vendor-supported MCP server. What keeps it from complete control is the API surface: primary grades, curves, qualifiers, trims on existing clips, speed ramps and Fairlight automation have no scripting calls. On the free edition we would rate it medium: Lua from the Scripts menu and import files still go a long way, but nothing external connects without a bridge script you start by hand.
Price: Freemium: the free edition costs nothing, and Studio is a one-time $295 licence with free updates (or a $30 a month Blackmagic Cloud rental); scripting from outside the app, the MCP server and nearly all AI tools need Studio.
The DaVinci Resolve scripting API (the DaVinciResolveScript module over fusionscript) lets an outside Python or Lua process drive a running Resolve: projects, media pool, timelines, markers, LUTs and CDLs, Fusion comps, transcription and render queues.
Scripts placed in the Fusion/Scripts folders appear under Workspace > Scripts and get a live resolve object; Fusion has its own scripting for comps and tools.
Resolve has no render or edit CLI of its own, but it launches headless with -nogui and Blackmagic says the scripting APIs keep working, so a script can import, build and render with no window.
Four plugin layers: OpenFX image effects in C++ (loaded on Color and Fusion nodes, in both editions, though some vendors such as Topaz require Studio), Workflow Integration plugins (Electron panels under Workspace > Workflow Integrations, Studio only), DCTL colour shaders (applying a DCTL as an effect is marked Studio only; 21.1 adds ValidateDCTL and EncryptDCTL to the API), and Fusion macros and scripts.
Yes, in Studio 21.1 and later: a ResolveMCP executable inside the app bundle, configured from File > Setup AI Assistants for Claude Desktop, Claude Code, Codex, Google Antigravity and Grok Build, and usable from any stdio MCP client by path.
Projects live in a database, not loose files, so an agent cannot simply edit a project on disk.
5 we would consider; we lead with ResolveMCP (native, DaVinci Resolve Studio).
Resolve's AI runs locally on the DaVinci Neural Engine, with no credits or cloud account, and almost all of it is Studio only.
What an AI agent can do in DaVinci Resolve
16 jobs people ask for, checked against what DaVinci Resolve’s interfaces expose: 9 fully, 5 in part, 2 not at all.
| Job | Agent can do it? | How, or why not |
|---|---|---|
| Assemble a rough cut from clips, a shot list or a transcript | Yes | Studio: MediaPool.AppendToTimeline and CreateTimelineFromClips with in and out points; free: the agent writes an FCPXML or OTIO timeline for import or builds it from a Lua script. |
| Import, rename and organise media into bins | Yes | MediaPool and Folder calls cover import, folders, clip names, colours and metadata; Smart Bins and Power Bins cannot be created.samuelgursky/davinci-resolve-mcp, API limitations (verified on Studio 21.0.2), read |
| Add markers at every cut and export them | Yes | Timeline and TimelineItem AddMarker, GetMarkers and DeleteMarkersByColor; the agent writes the CSV. |
| Batch render several deliverables | Yes | Render presets, SetRenderSettings, AddRenderJob and StartRendering, and headless with -nogui on Studio; AddRenderJob returns nothing useful on failure, so check job status after. |
| Add transitions, fades and constant speed changes | Yes | Studio 21.1 added TimelineItem.AddTransition and Get/Set Fades and Speed; earlier versions had no call, so older servers under-report this.Resolve scripting changelog 21.1, read |
| Apply a LUT or CDL look across a timeline | Yes | SetLUT per node, SetCDL and applying grades from DRX stills work on both editions' APIs; there is no GetCDL to read a value back. |
| Colour grade with wheels, curves and qualifiers | No | Primary grade values, curves and qualifiers have no scripting calls; an agent can only reach them as a LUT, CDL, DRX still or DCTL it writes.samuelgursky/davinci-resolve-mcp, API limitations: color node graph editing and primary grade values, read |
| Transcribe interviews and create subtitles | Partly | Studio: TranscribeAudio, GetTranscription (21.1) and CreateSubtitlesFromAudio; per-subtitle text, timing and styling cannot be edited by script, so agents usually write an SRT and import it.samuelgursky/davinci-resolve-mcp, API limitations: subtitle text and styling, read |
| Build multicam clips and switch angles by speaker | Yes | Studio 21.1: CreateMulticamClip, AutoAlignClips, PerformMulticamSmartSwitch and FlattenMulticam. |
| Create Fusion titles, lower thirds and motion graphics | Yes | Fusion's scripting API adds tools, sets inputs and keyframes and renders comps; open-fusion-mcp checks each write by reading it back. |
| Isolate a subject with Magic Mask | Partly | TimelineItem.CreateMagicMask exists on Studio but needs operator clicks to define the subject.samuelgursky/davinci-resolve-mcp, API limitations: CreateMagicMask, read |
| Trim, split or slip clips already on a timeline | No | There is no razor, blade, trim or position setter for existing timeline items; the workaround is rebuilding the timeline from source ranges.samuelgursky/davinci-resolve-mcp, API limitations: razor and trim, read |
| Mix audio in Fairlight | Partly | 21.1 added clip audio properties and NormalizeAudioLevel, but EQ, FairlightFX, automation and the AI Audio Assistant have no calls.samuelgursky/davinci-resolve-mcp, API limitations: Fairlight, read |
| Look at frames to check its own work | Partly | GetCurrentClipThumbnailImage only returns data on the Color page, so agents export stills or render a proof and inspect the file. |
| Run unattended on a render or edit server | Yes | Launch Studio with -nogui and connect a script; community measurement found no API capability lost headless, and no modal dialogs to wedge the session. |
| Do any of this on the free edition | Partly | Since 21.1 only Lua from Workspace > Scripts and file import remain; an outside agent needs a bridge script started by hand each session. |
What AI can’t do in DaVinci Resolve yet
On the free edition, no outside process can connect to Resolve, and since 21.1 Python scripts no longer list in the Scripts menu.
Workaround: Use a Lua bridge started from Workspace > Scripts, have the agent write FCPXML, OTIO or SRT files to import, stay on 21.0.x, or buy Studio.
Puget Systems, How DaVinci Resolve Free v21.1 scripting changes affect Puget Bench, read
Primary grades, curves, qualifiers and power windows cannot be set by script.
Workaround: Express the look as a LUT, CDL, DCTL or a DRX grade still and apply that; or grade by hand after the agent has done the structural work.
Existing timeline clips cannot be razored, trimmed, slipped or moved.
Workaround: Rebuild the timeline from source in and out points as a new version, which also keeps the original intact.
Speed ramps and retime curves have no API; 21.1 sets a constant speed only.
Workaround: Set constant speed by script and draw the ramp by hand, or let a computer-use agent operate the retime curve.
Neural Engine tools return False on the free edition, and some need an Extras pack the API cannot detect.
Workaround: Install the packs from the Extras Download Manager once; on free, use an outside model and import the result (an SRT, a matte, a cleaned WAV).
Blackmagic scripting README, Studio and AI Scripting APIs, read
Many calls fail silently: AddRenderJob, SetSetting and others return None or False with no reason.
Workaround: Read every write back, or use a wrapper such as dvr or samuelgursky's server that decodes errors.
Scripts the assistant writes run with the assistant's own disk and network permissions.
Workaround: Work on a duplicated timeline, keep project backups and leave External scripting on Local rather than Network.
DaVinci Resolve MCP shortlist
For installation, verification and troubleshooting, use our DaVinci Resolve MCP setup guide. The reference below covers the wider app and edition requirements.
- ResolveMCP (native, DaVinci Resolve Studio)
Start here on Studio 21.1: nothing to install, vendor supported, and the run-a-script design reaches everything the API does. Requirements: DaVinci Resolve Studio 21.1 or later, running with a project open. On Windows the executable is C:\Program Files\Blackmagic Design\DaVinci Resolve\ResolveMCP.exe. File > Setup AI Assistants writes the client config for supported clients.
Blackmagic Design press release, DaVinci Resolve 21.1, 8 September 2026, read
- davinci-resolve-mcp
The most maintained community server: pick it for Resolve 18.5 to 21.0, for clients the native server does not set up, or for transcription and media analysis outside Resolve's own tools. Requirements: Run
npx davinci-resolve-mcp setupfirst (it installs a managed Python environment), Python 3.10+, and Resolve Studio 18.5+ running with External scripting using set to Local. The free-edition bridge only works on 21.0.x and earlier.samuelgursky/davinci-resolve-mcp README and docs/install.md (v4.15.2), read
- Wasserman's Unofficial DaVinci MCP
The best fit for free Resolve users who want numeric work (beats, loudness, LUTs) done outside the app and imported as files. Requirements: pip install "git+https://github.com/wassermanproductions/unofficial-davinci-mcp.git", Python 3.10+ and ffmpeg. Resolve Studio for the live tier; any edition for the file tier. macOS and Linux.
- DaVinci Resolve Lua MCP
The cleanest free 21.1 route for Claude Desktop users; small and new, so expect point releases to break it. Requirements: Claude Desktop only: installed as a .mcpb extension, whose manifest runs this command with ${__dirname} set to the extension folder; download the .mcpb from the GitHub release rather than writing a config by hand. Resolve 21.1 free edition with a project open, and Workspace > Scripts > resolve_mcp_bridge clicked after every launch. macOS; Windows experimental.
- dvr
Use it when the job belongs in a pipeline or cron job as much as in a chat: the CLI and MCP share one code path. Requirements: pip install dvr, and Resolve Studio 18.5+ running with external scripting enabled.
mhadifilms/dvr README, read
- open-fusion-mcp
The specialist for motion graphics and titles built as editable Fusion node graphs; pair it with the native server for the edit. Requirements: macOS, DaVinci Resolve Studio 21.1 with External scripting using set to Local, Python 3.12, and a clone of the repository with connector/requirements.txt installed in connector/.venv. The allowlist names the only project the tools may change.

Connect DaVinci Resolve to Claude, ChatGPT, Codex and other assistants
Pick your assistant. Each setup panel leads with ResolveMCP (native, DaVinci Resolve Studio) and has the config for every other DaVinci Resolve server underneath.
Voyager Built in
Studio uses Voyager’s CLI over the official Blackmagic MCP on supported installs or the Python SDK on older versions, with Local external scripting enabled. Free-edition in-app commands run on macOS: import requires Resolve 18.5 or later and editing requires 21.1 or later; on Windows Voyager can prepare a timeline for manual import. Voyager inspects the current timeline and preserves existing work. Free commands also support editable Fusion motion graphics and keyframed titles, framing and audio adjustments, and SRT captions for burned-in renders; advanced color controls, speed ramps and Edit-page OpenFX remain outside them.
Requirements: Install Resolve from Blackmagic Design; Mac App Store Resolve is unsupported. Enable Local external scripting for Studio. Free in-app commands require macOS, with 18.5+ for import and 21.1+ for editing; Windows uses manual timeline import. Windows and Linux Voyager builds are alpha; computer control is unavailable on Linux.
Claude desktop app Config below
Does Claude desktop app work with DaVinci Resolve?
Yes, through ResolveMCP (native, DaVinci Resolve Studio), the official MCP server from Blackmagic Design.
Resolve Studio 21.1's Setup AI Assistants opens a Claude Desktop extension installer as a second step; early users needed to re-run it with Claude closed. The free-edition Lua server by saadk408 is distributed only as a Claude Desktop .mcpb extension.
ResolveMCP (native, DaVinci Resolve Studio) · config in claude_desktop_config.json (Settings > Developer > Edit Config), which is ~/Library/Application Support/Claude/ on macOS and %APPDATA%\Claude\ on Windows
First: DaVinci Resolve Studio 21.1 or later, running with a project open. On Windows the executable is C:\Program Files\Blackmagic Design\DaVinci Resolve\ResolveMCP.exe. File > Setup AI Assistants writes the client config for supported clients.
{
"mcpServers": {
"davinci-resolve": {
"command": "/Applications/DaVinci Resolve/DaVinci Resolve.app/Contents/Applications/ResolveMCP",
"args": [],
"env": {}
}
}
}{
"mcpServers": {
"davinci-resolve": {
"command": "C:\\Program Files\\Blackmagic Design\\DaVinci Resolve\\ResolveMCP.exe",
"args": [],
"env": {}
}
}
}›The other 5 DaVinci Resolve MCP servers in Claude desktop app
davinci-resolve-mcp
First: Run npx davinci-resolve-mcp setup first (it installs a managed Python environment), Python 3.10+, and Resolve Studio 18.5+ running with External scripting using set to Local. The free-edition bridge only works on 21.0.x and earlier.
{
"mcpServers": {
"davinci-resolve": {
"command": "npx",
"args": [
"-y",
"davinci-resolve-mcp",
"server"
],
"env": {}
}
}
}Wasserman's Unofficial DaVinci MCP
First: pip install "git+https://github.com/wassermanproductions/unofficial-davinci-mcp.git", Python 3.10+ and ffmpeg. Resolve Studio for the live tier; any edition for the file tier. macOS and Linux.
{
"mcpServers": {
"davinci-resolve": {
"command": "unofficial-davinci-mcp",
"args": [],
"env": {}
}
}
}DaVinci Resolve Lua MCP
First: Claude Desktop only: installed as a .mcpb extension, whose manifest runs this command with ${__dirname} set to the extension folder; download the .mcpb from the GitHub release rather than writing a config by hand. Resolve 21.1 free edition with a project open, and Workspace > Scripts > resolve_mcp_bridge clicked after every launch. macOS; Windows experimental.
{
"mcpServers": {
"davinci-resolve": {
"command": "node",
"args": [
"${__dirname}/server/index.js"
],
"env": {}
}
}
}This server installs from source: replace the placeholder path with where you cloned or installed it.
dvr
First: pip install dvr, and Resolve Studio 18.5+ running with external scripting enabled.
{
"mcpServers": {
"davinci-resolve": {
"command": "dvr",
"args": [
"mcp",
"serve"
],
"env": {}
}
}
}open-fusion-mcp
First: macOS, DaVinci Resolve Studio 21.1 with External scripting using set to Local, Python 3.12, and a clone of the repository with connector/requirements.txt installed in connector/.venv. The allowlist names the only project the tools may change.
{
"mcpServers": {
"davinci-resolve": {
"command": "/absolute/path/to/open-fusion-mcp/connector/bin/use-fusion-mcp",
"args": [],
"env": {
"FUSION_MCP_PROJECT_ALLOWLIST": "Testbed"
}
}
}
}This server installs from source: replace the placeholder path with where you cloned or installed it.
Quit and reopen the app after editing the config file; it is read at launch. Remote connectors are reached from Anthropic's cloud, not your computer, so a server on localhost or behind a VPN will not connect as a custom connector. Requires: a custom connector for remote servers, which Free plans limit to one and which an Owner adds on Team and Enterprise; local servers need only the desktop app. Claude desktop app docs.
Claude Code Config below
Does Claude Code work with DaVinci Resolve?
Yes, through ResolveMCP (native, DaVinci Resolve Studio), the official MCP server from Blackmagic Design.
Run Claude Code once before File > Setup AI Assistants so Resolve can detect it, then restart it and check claude mcp list.
ResolveMCP (native, DaVinci Resolve Studio) · config in ~/.claude.json for user scope (%USERPROFILE%\.claude.json on Windows), or .mcp.json in the project root for project scope
First: DaVinci Resolve Studio 21.1 or later, running with a project open. On Windows the executable is C:\Program Files\Blackmagic Design\DaVinci Resolve\ResolveMCP.exe. File > Setup AI Assistants writes the client config for supported clients.
claude mcp add --scope user --transport stdio davinci-resolve -- '/Applications/DaVinci Resolve/DaVinci Resolve.app/Contents/Applications/ResolveMCP'claude mcp add --scope user --transport stdio davinci-resolve -- 'C:\Program Files\Blackmagic Design\DaVinci Resolve\ResolveMCP.exe'›The other 5 DaVinci Resolve MCP servers in Claude Code
davinci-resolve-mcp
First: Run npx davinci-resolve-mcp setup first (it installs a managed Python environment), Python 3.10+, and Resolve Studio 18.5+ running with External scripting using set to Local. The free-edition bridge only works on 21.0.x and earlier.
claude mcp add --scope user --transport stdio davinci-resolve -- npx -y davinci-resolve-mcp serverWasserman's Unofficial DaVinci MCP
First: pip install "git+https://github.com/wassermanproductions/unofficial-davinci-mcp.git", Python 3.10+ and ffmpeg. Resolve Studio for the live tier; any edition for the file tier. macOS and Linux.
claude mcp add --scope user --transport stdio davinci-resolve -- unofficial-davinci-mcpDaVinci Resolve Lua MCP
First: Claude Desktop only: installed as a .mcpb extension, whose manifest runs this command with ${__dirname} set to the extension folder; download the .mcpb from the GitHub release rather than writing a config by hand. Resolve 21.1 free edition with a project open, and Workspace > Scripts > resolve_mcp_bridge clicked after every launch. macOS; Windows experimental.
claude mcp add --scope user --transport stdio davinci-resolve -- node '${__dirname}/server/index.js'This server installs from source: replace the placeholder path with where you cloned or installed it.
dvr
First: pip install dvr, and Resolve Studio 18.5+ running with external scripting enabled.
claude mcp add --scope user --transport stdio davinci-resolve -- dvr mcp serveopen-fusion-mcp
First: macOS, DaVinci Resolve Studio 21.1 with External scripting using set to Local, Python 3.12, and a clone of the repository with connector/requirements.txt installed in connector/.venv. The allowlist names the only project the tools may change.
claude mcp add --scope user -e FUSION_MCP_PROJECT_ALLOWLIST=Testbed --transport stdio davinci-resolve -- /absolute/path/to/open-fusion-mcp/connector/bin/use-fusion-mcpThis server installs from source: replace the placeholder path with where you cloned or installed it.
Options go before the name and the -- keeps the server's own flags away from Claude Code; a name placed straight after -e is read as another variable, hence --transport between them. Check with claude mcp list or /mcp inside a session. Claude Code docs.
ChatGPT Not directly
Does ChatGPT work with DaVinci Resolve?
Not directly. ChatGPT only connects to remote MCP servers over HTTPS, and ResolveMCP (native, DaVinci Resolve Studio) runs on your own computer. To use it from ChatGPT you would have to expose it at a public URL through a tunnel or bridge, which also exposes DaVinci Resolve to the internet.
Blackmagic does not publish an app inside ChatGPT. The 21.1 integration targets Codex, and the server is local stdio, so ChatGPT on the web cannot reach it.
ResolveMCP (native, DaVinci Resolve Studio) · config in ChatGPT's settings on the web (Apps, shown as Plugins on newer accounts); there is no config file
ChatGPT only connects to remote MCP servers over HTTPS, and ResolveMCP (native, DaVinci Resolve Studio) runs on your own computer. To use it from ChatGPT you would have to expose it at a public URL through a tunnel or bridge, which also exposes DaVinci Resolve to the internet.
›The other 5 DaVinci Resolve MCP servers in ChatGPT
davinci-resolve-mcp
ChatGPT only connects to remote MCP servers over HTTPS, and davinci-resolve-mcp runs on your own computer. To use it from ChatGPT you would have to expose it at a public URL through a tunnel or bridge, which also exposes DaVinci Resolve to the internet.
Wasserman's Unofficial DaVinci MCP
ChatGPT only connects to remote MCP servers over HTTPS, and Wasserman's Unofficial DaVinci MCP runs on your own computer. To use it from ChatGPT you would have to expose it at a public URL through a tunnel or bridge, which also exposes DaVinci Resolve to the internet.
DaVinci Resolve Lua MCP
ChatGPT only connects to remote MCP servers over HTTPS, and DaVinci Resolve Lua MCP runs on your own computer. To use it from ChatGPT you would have to expose it at a public URL through a tunnel or bridge, which also exposes DaVinci Resolve to the internet.
dvr
ChatGPT only connects to remote MCP servers over HTTPS, and dvr runs on your own computer. To use it from ChatGPT you would have to expose it at a public URL through a tunnel or bridge, which also exposes DaVinci Resolve to the internet.
open-fusion-mcp
ChatGPT only connects to remote MCP servers over HTTPS, and open-fusion-mcp runs on your own computer. To use it from ChatGPT you would have to expose it at a public URL through a tunnel or bridge, which also exposes DaVinci Resolve to the internet.
ChatGPT only reaches servers on the public internet over HTTPS. A local stdio server needs OpenAI's Secure MCP Tunnel (the tunnel-client daemon, an OpenAI Platform tunnel and API key), or a public tunnel such as ngrok, so most people use Codex or Claude for local apps. Requires: developer mode (beta) in ChatGPT on the web; OpenAI documents full MCP, including write actions, for Business, Enterprise and Edu workspaces, where an admin must allow it. ChatGPT docs.
Codex Config below
Does Codex work with DaVinci Resolve?
Yes, through ResolveMCP (native, DaVinci Resolve Studio), the official MCP server from Blackmagic Design.
Setup AI Assistants writes a [mcp_servers.davinci_resolve] block to ~/.codex/config.toml. In the first week after 21.1, a user of the ChatGPT desktop app on Windows saw the setup succeed but no Resolve tools appear; Codex CLI connected.
ResolveMCP (native, DaVinci Resolve Studio) · config in ~/.codex/config.toml (%USERPROFILE%\.codex\config.toml on Windows), shared by the Codex CLI, IDE extension and desktop app
First: DaVinci Resolve Studio 21.1 or later, running with a project open. On Windows the executable is C:\Program Files\Blackmagic Design\DaVinci Resolve\ResolveMCP.exe. File > Setup AI Assistants writes the client config for supported clients.
[mcp_servers.davinci-resolve]
command = '/Applications/DaVinci Resolve/DaVinci Resolve.app/Contents/Applications/ResolveMCP'
args = []
env = {}[mcp_servers.davinci-resolve]
command = 'C:\Program Files\Blackmagic Design\DaVinci Resolve\ResolveMCP.exe'
args = []
env = {}›The other 5 DaVinci Resolve MCP servers in Codex
davinci-resolve-mcp
First: Run npx davinci-resolve-mcp setup first (it installs a managed Python environment), Python 3.10+, and Resolve Studio 18.5+ running with External scripting using set to Local. The free-edition bridge only works on 21.0.x and earlier.
[mcp_servers.davinci-resolve]
command = 'npx'
args = ["-y", "davinci-resolve-mcp", "server"]
env = {}Wasserman's Unofficial DaVinci MCP
First: pip install "git+https://github.com/wassermanproductions/unofficial-davinci-mcp.git", Python 3.10+ and ffmpeg. Resolve Studio for the live tier; any edition for the file tier. macOS and Linux.
[mcp_servers.davinci-resolve]
command = 'unofficial-davinci-mcp'
args = []
env = {}DaVinci Resolve Lua MCP
First: Claude Desktop only: installed as a .mcpb extension, whose manifest runs this command with ${__dirname} set to the extension folder; download the .mcpb from the GitHub release rather than writing a config by hand. Resolve 21.1 free edition with a project open, and Workspace > Scripts > resolve_mcp_bridge clicked after every launch. macOS; Windows experimental.
[mcp_servers.davinci-resolve]
command = 'node'
args = ["${__dirname}/server/index.js"]
env = {}This server installs from source: replace the placeholder path with where you cloned or installed it.
dvr
First: pip install dvr, and Resolve Studio 18.5+ running with external scripting enabled.
[mcp_servers.davinci-resolve]
command = 'dvr'
args = ["mcp", "serve"]
env = {}open-fusion-mcp
First: macOS, DaVinci Resolve Studio 21.1 with External scripting using set to Local, Python 3.12, and a clone of the repository with connector/requirements.txt installed in connector/.venv. The allowlist names the only project the tools may change.
[mcp_servers.davinci-resolve]
command = '/absolute/path/to/open-fusion-mcp/connector/bin/use-fusion-mcp'
args = []
env = { FUSION_MCP_PROJECT_ALLOWLIST = "Testbed" }This server installs from source: replace the placeholder path with where you cloned or installed it.
codex mcp add also takes a local server (name, then -- and the command), but it sets variables with --env KEY=VALUE rather than -e, so the config block is shown here. Run codex mcp list to check it is enabled, and codex mcp login with the server name for an OAuth server. Codex docs.
Cursor Config below
Does Cursor work with DaVinci Resolve?
Yes, through ResolveMCP (native, DaVinci Resolve Studio), the official MCP server from Blackmagic Design.
ResolveMCP (native, DaVinci Resolve Studio) · config in ~/.cursor/mcp.json for every project (%USERPROFILE%\.cursor\mcp.json on Windows), or .cursor/mcp.json in one project
First: DaVinci Resolve Studio 21.1 or later, running with a project open. On Windows the executable is C:\Program Files\Blackmagic Design\DaVinci Resolve\ResolveMCP.exe. File > Setup AI Assistants writes the client config for supported clients.
{
"mcpServers": {
"davinci-resolve": {
"command": "/Applications/DaVinci Resolve/DaVinci Resolve.app/Contents/Applications/ResolveMCP",
"args": [],
"env": {}
}
}
}{
"mcpServers": {
"davinci-resolve": {
"command": "C:\\Program Files\\Blackmagic Design\\DaVinci Resolve\\ResolveMCP.exe",
"args": [],
"env": {}
}
}
}›The other 5 DaVinci Resolve MCP servers in Cursor
davinci-resolve-mcp
First: Run npx davinci-resolve-mcp setup first (it installs a managed Python environment), Python 3.10+, and Resolve Studio 18.5+ running with External scripting using set to Local. The free-edition bridge only works on 21.0.x and earlier.
{
"mcpServers": {
"davinci-resolve": {
"command": "npx",
"args": [
"-y",
"davinci-resolve-mcp",
"server"
],
"env": {}
}
}
}Wasserman's Unofficial DaVinci MCP
First: pip install "git+https://github.com/wassermanproductions/unofficial-davinci-mcp.git", Python 3.10+ and ffmpeg. Resolve Studio for the live tier; any edition for the file tier. macOS and Linux.
{
"mcpServers": {
"davinci-resolve": {
"command": "unofficial-davinci-mcp",
"args": [],
"env": {}
}
}
}DaVinci Resolve Lua MCP
First: Claude Desktop only: installed as a .mcpb extension, whose manifest runs this command with ${__dirname} set to the extension folder; download the .mcpb from the GitHub release rather than writing a config by hand. Resolve 21.1 free edition with a project open, and Workspace > Scripts > resolve_mcp_bridge clicked after every launch. macOS; Windows experimental.
{
"mcpServers": {
"davinci-resolve": {
"command": "node",
"args": [
"${__dirname}/server/index.js"
],
"env": {}
}
}
}This server installs from source: replace the placeholder path with where you cloned or installed it.
dvr
First: pip install dvr, and Resolve Studio 18.5+ running with external scripting enabled.
{
"mcpServers": {
"davinci-resolve": {
"command": "dvr",
"args": [
"mcp",
"serve"
],
"env": {}
}
}
}open-fusion-mcp
First: macOS, DaVinci Resolve Studio 21.1 with External scripting using set to Local, Python 3.12, and a clone of the repository with connector/requirements.txt installed in connector/.venv. The allowlist names the only project the tools may change.
{
"mcpServers": {
"davinci-resolve": {
"command": "/absolute/path/to/open-fusion-mcp/connector/bin/use-fusion-mcp",
"args": [],
"env": {
"FUSION_MCP_PROJECT_ALLOWLIST": "Testbed"
}
}
}
}This server installs from source: replace the placeholder path with where you cloned or installed it.
Cursor has capped the number of MCP tools it sends the model (third-party guides cite 40 to 80), so disable tools you do not need in Settings > MCP. GUI apps do not inherit your shell PATH; use full paths for commands like uvx. Cursor docs.
VS Code with GitHub Copilot Config below
Does VS Code with GitHub Copilot work with DaVinci Resolve?
Yes, through ResolveMCP (native, DaVinci Resolve Studio), the official MCP server from Blackmagic Design.
ResolveMCP (native, DaVinci Resolve Studio) · config in ~/.copilot/mcp-config.json for yourself (the Copilot Global destination), or .mcp.json in the workspace root for a team
First: DaVinci Resolve Studio 21.1 or later, running with a project open. On Windows the executable is C:\Program Files\Blackmagic Design\DaVinci Resolve\ResolveMCP.exe. File > Setup AI Assistants writes the client config for supported clients.
{
"mcpServers": {
"davinci-resolve": {
"command": "/Applications/DaVinci Resolve/DaVinci Resolve.app/Contents/Applications/ResolveMCP",
"args": [],
"env": {}
}
}
}{
"mcpServers": {
"davinci-resolve": {
"command": "C:\\Program Files\\Blackmagic Design\\DaVinci Resolve\\ResolveMCP.exe",
"args": [],
"env": {}
}
}
}›The other 5 DaVinci Resolve MCP servers in VS Code with GitHub Copilot
davinci-resolve-mcp
First: Run npx davinci-resolve-mcp setup first (it installs a managed Python environment), Python 3.10+, and Resolve Studio 18.5+ running with External scripting using set to Local. The free-edition bridge only works on 21.0.x and earlier.
{
"mcpServers": {
"davinci-resolve": {
"command": "npx",
"args": [
"-y",
"davinci-resolve-mcp",
"server"
],
"env": {}
}
}
}Wasserman's Unofficial DaVinci MCP
First: pip install "git+https://github.com/wassermanproductions/unofficial-davinci-mcp.git", Python 3.10+ and ffmpeg. Resolve Studio for the live tier; any edition for the file tier. macOS and Linux.
{
"mcpServers": {
"davinci-resolve": {
"command": "unofficial-davinci-mcp",
"args": [],
"env": {}
}
}
}DaVinci Resolve Lua MCP
First: Claude Desktop only: installed as a .mcpb extension, whose manifest runs this command with ${__dirname} set to the extension folder; download the .mcpb from the GitHub release rather than writing a config by hand. Resolve 21.1 free edition with a project open, and Workspace > Scripts > resolve_mcp_bridge clicked after every launch. macOS; Windows experimental.
{
"mcpServers": {
"davinci-resolve": {
"command": "node",
"args": [
"${__dirname}/server/index.js"
],
"env": {}
}
}
}This server installs from source: replace the placeholder path with where you cloned or installed it.
dvr
First: pip install dvr, and Resolve Studio 18.5+ running with external scripting enabled.
{
"mcpServers": {
"davinci-resolve": {
"command": "dvr",
"args": [
"mcp",
"serve"
],
"env": {}
}
}
}open-fusion-mcp
First: macOS, DaVinci Resolve Studio 21.1 with External scripting using set to Local, Python 3.12, and a clone of the repository with connector/requirements.txt installed in connector/.venv. The allowlist names the only project the tools may change.
{
"mcpServers": {
"davinci-resolve": {
"command": "/absolute/path/to/open-fusion-mcp/connector/bin/use-fusion-mcp",
"args": [],
"env": {
"FUSION_MCP_PROJECT_ALLOWLIST": "Testbed"
}
}
}
}This server installs from source: replace the placeholder path with where you cloned or installed it.
VS Code now recommends the portable mcpServers file, which the Copilot harness reads directly and Copilot CLI shares; .vscode/mcp.json still works but uses "servers" and is labelled deprecated in the Add Server flow. MCP: Add Server in the Command Palette writes the same entry for you. Requires: a GitHub Copilot plan, and on Copilot Business or Enterprise the organization's "MCP servers in Copilot" policy, which is off by default. VS Code with GitHub Copilot docs.
Gemini CLI Config below
Does Gemini CLI work with DaVinci Resolve?
Yes, through ResolveMCP (native, DaVinci Resolve Studio), the official MCP server from Blackmagic Design.
ResolveMCP (native, DaVinci Resolve Studio) · config in ~/.gemini/settings.json (%USERPROFILE%\.gemini\settings.json on Windows), or .gemini/settings.json in one project
First: DaVinci Resolve Studio 21.1 or later, running with a project open. On Windows the executable is C:\Program Files\Blackmagic Design\DaVinci Resolve\ResolveMCP.exe. File > Setup AI Assistants writes the client config for supported clients.
gemini mcp add --scope user davinci-resolve '/Applications/DaVinci Resolve/DaVinci Resolve.app/Contents/Applications/ResolveMCP' --gemini mcp add --scope user davinci-resolve 'C:\Program Files\Blackmagic Design\DaVinci Resolve\ResolveMCP.exe' --›The other 5 DaVinci Resolve MCP servers in Gemini CLI
davinci-resolve-mcp
First: Run npx davinci-resolve-mcp setup first (it installs a managed Python environment), Python 3.10+, and Resolve Studio 18.5+ running with External scripting using set to Local. The free-edition bridge only works on 21.0.x and earlier.
gemini mcp add --scope user davinci-resolve npx -- -y davinci-resolve-mcp serverWasserman's Unofficial DaVinci MCP
First: pip install "git+https://github.com/wassermanproductions/unofficial-davinci-mcp.git", Python 3.10+ and ffmpeg. Resolve Studio for the live tier; any edition for the file tier. macOS and Linux.
gemini mcp add --scope user davinci-resolve unofficial-davinci-mcp --DaVinci Resolve Lua MCP
First: Claude Desktop only: installed as a .mcpb extension, whose manifest runs this command with ${__dirname} set to the extension folder; download the .mcpb from the GitHub release rather than writing a config by hand. Resolve 21.1 free edition with a project open, and Workspace > Scripts > resolve_mcp_bridge clicked after every launch. macOS; Windows experimental.
gemini mcp add --scope user davinci-resolve node -- '${__dirname}/server/index.js'This server installs from source: replace the placeholder path with where you cloned or installed it.
dvr
First: pip install dvr, and Resolve Studio 18.5+ running with external scripting enabled.
gemini mcp add --scope user davinci-resolve dvr -- mcp serveopen-fusion-mcp
First: macOS, DaVinci Resolve Studio 21.1 with External scripting using set to Local, Python 3.12, and a clone of the repository with connector/requirements.txt installed in connector/.venv. The allowlist names the only project the tools may change.
gemini mcp add --scope user -e FUSION_MCP_PROJECT_ALLOWLIST=Testbed davinci-resolve /absolute/path/to/open-fusion-mcp/connector/bin/use-fusion-mcp --This server installs from source: replace the placeholder path with where you cloned or installed it.
Without --scope user the server is written to the current project's settings. Stdio servers only connect in a trusted folder; run gemini trust, then gemini mcp list to check. Requires: a Gemini API key or Vertex AI, since consumer Google sign-ins moved to Antigravity CLI on 18 June 2026. Gemini CLI docs.
Hermes Agent Config below
Does Hermes Agent work with DaVinci Resolve?
Yes, through ResolveMCP (native, DaVinci Resolve Studio), the official MCP server from Blackmagic Design.
ResolveMCP (native, DaVinci Resolve Studio) · config in ~/.hermes/config.yaml (%LOCALAPPDATA%\hermes\config.yaml on native Windows)
First: DaVinci Resolve Studio 21.1 or later, running with a project open. On Windows the executable is C:\Program Files\Blackmagic Design\DaVinci Resolve\ResolveMCP.exe. File > Setup AI Assistants writes the client config for supported clients.
mcp_servers:
davinci-resolve:
command: '/Applications/DaVinci Resolve/DaVinci Resolve.app/Contents/Applications/ResolveMCP'
args: []
env: {}mcp_servers:
davinci-resolve:
command: 'C:\Program Files\Blackmagic Design\DaVinci Resolve\ResolveMCP.exe'
args: []
env: {}›The other 5 DaVinci Resolve MCP servers in Hermes Agent
davinci-resolve-mcp
First: Run npx davinci-resolve-mcp setup first (it installs a managed Python environment), Python 3.10+, and Resolve Studio 18.5+ running with External scripting using set to Local. The free-edition bridge only works on 21.0.x and earlier.
mcp_servers:
davinci-resolve:
command: 'npx'
args: ["-y", "davinci-resolve-mcp", "server"]
env: {}Wasserman's Unofficial DaVinci MCP
First: pip install "git+https://github.com/wassermanproductions/unofficial-davinci-mcp.git", Python 3.10+ and ffmpeg. Resolve Studio for the live tier; any edition for the file tier. macOS and Linux.
mcp_servers:
davinci-resolve:
command: 'unofficial-davinci-mcp'
args: []
env: {}DaVinci Resolve Lua MCP
First: Claude Desktop only: installed as a .mcpb extension, whose manifest runs this command with ${__dirname} set to the extension folder; download the .mcpb from the GitHub release rather than writing a config by hand. Resolve 21.1 free edition with a project open, and Workspace > Scripts > resolve_mcp_bridge clicked after every launch. macOS; Windows experimental.
mcp_servers:
davinci-resolve:
command: 'node'
args: ["${__dirname}/server/index.js"]
env: {}This server installs from source: replace the placeholder path with where you cloned or installed it.
dvr
First: pip install dvr, and Resolve Studio 18.5+ running with external scripting enabled.
mcp_servers:
davinci-resolve:
command: 'dvr'
args: ["mcp", "serve"]
env: {}open-fusion-mcp
First: macOS, DaVinci Resolve Studio 21.1 with External scripting using set to Local, Python 3.12, and a clone of the repository with connector/requirements.txt installed in connector/.venv. The allowlist names the only project the tools may change.
mcp_servers:
davinci-resolve:
command: '/absolute/path/to/open-fusion-mcp/connector/bin/use-fusion-mcp'
args: []
env: {FUSION_MCP_PROJECT_ALLOWLIST: "Testbed"}This server installs from source: replace the placeholder path with where you cloned or installed it.
Start a new session or run /reload-mcp after editing; a running gateway picks up config.yaml changes within about a minute. For an OAuth-protected remote server, add auth: oauth under it and run hermes mcp login with the server name. Hermes Agent docs.
OpenClaw Config below
Does OpenClaw work with DaVinci Resolve?
Yes, through ResolveMCP (native, DaVinci Resolve Studio), the official MCP server from Blackmagic Design.
ResolveMCP (native, DaVinci Resolve Studio) · config in ~/.openclaw/openclaw.json, under mcp.servers
First: DaVinci Resolve Studio 21.1 or later, running with a project open. On Windows the executable is C:\Program Files\Blackmagic Design\DaVinci Resolve\ResolveMCP.exe. File > Setup AI Assistants writes the client config for supported clients.
{
"mcp": {
"servers": {
"davinci-resolve": {
"command": "/Applications/DaVinci Resolve/DaVinci Resolve.app/Contents/Applications/ResolveMCP",
"args": [],
"env": {}
}
}
}
}{
"mcp": {
"servers": {
"davinci-resolve": {
"command": "C:\\Program Files\\Blackmagic Design\\DaVinci Resolve\\ResolveMCP.exe",
"args": [],
"env": {}
}
}
}
}›The other 5 DaVinci Resolve MCP servers in OpenClaw
davinci-resolve-mcp
First: Run npx davinci-resolve-mcp setup first (it installs a managed Python environment), Python 3.10+, and Resolve Studio 18.5+ running with External scripting using set to Local. The free-edition bridge only works on 21.0.x and earlier.
{
"mcp": {
"servers": {
"davinci-resolve": {
"command": "npx",
"args": [
"-y",
"davinci-resolve-mcp",
"server"
],
"env": {}
}
}
}
}Wasserman's Unofficial DaVinci MCP
First: pip install "git+https://github.com/wassermanproductions/unofficial-davinci-mcp.git", Python 3.10+ and ffmpeg. Resolve Studio for the live tier; any edition for the file tier. macOS and Linux.
{
"mcp": {
"servers": {
"davinci-resolve": {
"command": "unofficial-davinci-mcp",
"args": [],
"env": {}
}
}
}
}DaVinci Resolve Lua MCP
First: Claude Desktop only: installed as a .mcpb extension, whose manifest runs this command with ${__dirname} set to the extension folder; download the .mcpb from the GitHub release rather than writing a config by hand. Resolve 21.1 free edition with a project open, and Workspace > Scripts > resolve_mcp_bridge clicked after every launch. macOS; Windows experimental.
{
"mcp": {
"servers": {
"davinci-resolve": {
"command": "node",
"args": [
"${__dirname}/server/index.js"
],
"env": {}
}
}
}
}This server installs from source: replace the placeholder path with where you cloned or installed it.
dvr
First: pip install dvr, and Resolve Studio 18.5+ running with external scripting enabled.
{
"mcp": {
"servers": {
"davinci-resolve": {
"command": "dvr",
"args": [
"mcp",
"serve"
],
"env": {}
}
}
}
}open-fusion-mcp
First: macOS, DaVinci Resolve Studio 21.1 with External scripting using set to Local, Python 3.12, and a clone of the repository with connector/requirements.txt installed in connector/.venv. The allowlist names the only project the tools may change.
{
"mcp": {
"servers": {
"davinci-resolve": {
"command": "/absolute/path/to/open-fusion-mcp/connector/bin/use-fusion-mcp",
"args": [],
"env": {
"FUSION_MCP_PROJECT_ALLOWLIST": "Testbed"
}
}
}
}
}This server installs from source: replace the placeholder path with where you cloned or installed it.
The key is mcp.servers, not mcpServers. The Gateway hot-reloads the file; run openclaw mcp doctor with the server name and --probe to confirm it answers. Interpreter and loader variables such as NODE_OPTIONS are stripped from a stdio server's env. OpenClaw docs.
Windsurf (Devin Desktop) Config below
Does Windsurf (Devin Desktop) work with DaVinci Resolve?
Yes, through ResolveMCP (native, DaVinci Resolve Studio), the official MCP server from Blackmagic Design.
ResolveMCP (native, DaVinci Resolve Studio) · config in ~/.config/devin/mcp_config.json on macOS and Linux (%APPDATA%\devin\mcp_config.json on Windows); builds from before June 2026 used ~/.codeium/windsurf/mcp_config.json
First: DaVinci Resolve Studio 21.1 or later, running with a project open. On Windows the executable is C:\Program Files\Blackmagic Design\DaVinci Resolve\ResolveMCP.exe. File > Setup AI Assistants writes the client config for supported clients.
{
"mcpServers": {
"davinci-resolve": {
"command": "/Applications/DaVinci Resolve/DaVinci Resolve.app/Contents/Applications/ResolveMCP",
"args": [],
"env": {}
}
}
}{
"mcpServers": {
"davinci-resolve": {
"command": "C:\\Program Files\\Blackmagic Design\\DaVinci Resolve\\ResolveMCP.exe",
"args": [],
"env": {}
}
}
}›The other 5 DaVinci Resolve MCP servers in Windsurf (Devin Desktop)
davinci-resolve-mcp
First: Run npx davinci-resolve-mcp setup first (it installs a managed Python environment), Python 3.10+, and Resolve Studio 18.5+ running with External scripting using set to Local. The free-edition bridge only works on 21.0.x and earlier.
{
"mcpServers": {
"davinci-resolve": {
"command": "npx",
"args": [
"-y",
"davinci-resolve-mcp",
"server"
],
"env": {}
}
}
}Wasserman's Unofficial DaVinci MCP
First: pip install "git+https://github.com/wassermanproductions/unofficial-davinci-mcp.git", Python 3.10+ and ffmpeg. Resolve Studio for the live tier; any edition for the file tier. macOS and Linux.
{
"mcpServers": {
"davinci-resolve": {
"command": "unofficial-davinci-mcp",
"args": [],
"env": {}
}
}
}DaVinci Resolve Lua MCP
First: Claude Desktop only: installed as a .mcpb extension, whose manifest runs this command with ${__dirname} set to the extension folder; download the .mcpb from the GitHub release rather than writing a config by hand. Resolve 21.1 free edition with a project open, and Workspace > Scripts > resolve_mcp_bridge clicked after every launch. macOS; Windows experimental.
{
"mcpServers": {
"davinci-resolve": {
"command": "node",
"args": [
"${__dirname}/server/index.js"
],
"env": {}
}
}
}This server installs from source: replace the placeholder path with where you cloned or installed it.
dvr
First: pip install dvr, and Resolve Studio 18.5+ running with external scripting enabled.
{
"mcpServers": {
"davinci-resolve": {
"command": "dvr",
"args": [
"mcp",
"serve"
],
"env": {}
}
}
}open-fusion-mcp
First: macOS, DaVinci Resolve Studio 21.1 with External scripting using set to Local, Python 3.12, and a clone of the repository with connector/requirements.txt installed in connector/.venv. The allowlist names the only project the tools may change.
{
"mcpServers": {
"davinci-resolve": {
"command": "/absolute/path/to/open-fusion-mcp/connector/bin/use-fusion-mcp",
"args": [],
"env": {
"FUSION_MCP_PROJECT_ALLOWLIST": "Testbed"
}
}
}
}This server installs from source: replace the placeholder path with where you cloned or installed it.
Windsurf became Devin Desktop in June 2026 and its default agent is now Devin Local; the legacy Cascade agent expects serverUrl instead of url for remote servers and allows at most 100 tools at once. Refresh the MCP panel after editing the file. Requires: MCP left on by a Teams or Enterprise admin, who can also allowlist servers (allowlisting one blocks all others). Windsurf (Devin Desktop) docs.
DaVinci Resolve API, scripting and command line
DaVinci Resolve API
PartlyPython 3Lua 5.1The DaVinci Resolve scripting API (the DaVinciResolveScript module over fusionscript) lets an outside Python or Lua process drive a running Resolve: projects, media pool, timelines, markers, LUTs and CDLs, Fusion comps, transcription and render queues. External access needs Studio with Preferences > System > General > External scripting using set to Local (or Network, port 1144); on the free edition scriptapp("Resolve") refuses outside processes.
Cost: Studio licence only ($295 once)
import DaVinciResolveScript as dvr
resolve = dvr.scriptapp("Resolve")
project = resolve.GetProjectManager().GetCurrentProject()
timeline = project.GetCurrentTimeline()
print(timeline.GetName(), timeline.GetItemCount("video", 1))Read the current timeline from an outside Python process. On Studio 21.1, Resolve's bundled ResolvePython finds the module without environment variables.
DocumentationBlackmagic scripting README, Last Updated 24 Jul 2026 (copy in samuelgursky/davinci-resolve-mcp), read
DaVinci Resolve scripting
PartlyPython 3Lua 5.1Scripts placed in the Fusion/Scripts folders appear under Workspace > Scripts and get a live resolve object; Fusion has its own scripting for comps and tools. Since 21.1, Python scripts in that menu and the Console are Studio only, while Lua scripts still list and run on the free edition (community measurement on build 21.1.0.17; Blackmagic does not document the free Lua boundary).
Cost: Lua in the Scripts menu is free; Python and the 21.1 APIs need Studio
local project = resolve:GetProjectManager():GetCurrentProject()
local timeline = project:GetCurrentTimeline()
timeline:AddMarker(240, "Blue", "fix colour", "", 1)A Lua script saved to Fusion/Scripts/Utility and run from Workspace > Scripts adds a marker at frame 240. Lua is the scripting route the free 21.1 edition still lists.
Documentationsaadk408/davinci-resolve-lua-mcp README (free 21.1 Lua measurement), read
DaVinci Resolve command line and headless mode
PartlyShellPythonResolve has no render or edit CLI of its own, but it launches headless with -nogui and Blackmagic says the scripting APIs keep working, so a script can import, build and render with no window. That route is Studio only because it depends on external scripting. Community CLIs such as dvr wrap the API with JSON output.
Cost: Studio licence only
"/Applications/DaVinci Resolve/DaVinci Resolve.app/Contents/MacOS/Resolve" -noguiStart Resolve Studio without its interface on macOS, then connect a script. Launching through `open -a` drops the flag.
DocumentationBlackmagic scripting README, section Running DaVinci Resolve in headless mode, read
DaVinci Resolve plugins and add-ons
YesC++ (OpenFX 1.4)JavaScript (Electron)DCTLLuaPythonFour plugin layers: OpenFX image effects in C++ (loaded on Color and Fusion nodes, in both editions, though some vendors such as Topaz require Studio), Workflow Integration plugins (Electron panels under Workspace > Workflow Integrations, Studio only), DCTL colour shaders (applying a DCTL as an effect is marked Studio only; 21.1 adds ValidateDCTL and EncryptDCTL to the API), and Fusion macros and scripts. There is no official marketplace; plugins come from vendors directly.
Cost: OpenFX hosting is free; Workflow Integrations and the DCTL effect need Studio; third-party plugins are priced by their vendors
DocumentationDaVinci Resolve free vs Studio (Resolve 21 Reference Manual, Studio Version Only headings), read
DaVinci Resolve official MCP server
PartlyMCP (stdio)PythonYes, in Studio 21.1 and later: a ResolveMCP executable inside the app bundle, configured from File > Setup AI Assistants for Claude Desktop, Claude Code, Codex, Google Antigravity and Grok Build, and usable from any stdio MCP client by path. It exposes a small tool set built around running Python scripts inside Resolve. The free edition does not ship it.
Cost: Studio licence only
claude mcp add davinci-resolve -- "/Applications/DaVinci Resolve/DaVinci Resolve.app/Contents/Applications/ResolveMCP"Register the native server with Claude Code by hand when Setup AI Assistants did not detect it (macOS path).
DocumentationBlackmagic Design forum, DaVinci Resolve 21.1 AI assistants thread (staff reply listing clients), read
DaVinci Resolve project files
PartlyFCPXMLOTIOEDLSRTCUBEDRP/DRT/DRXProjects live in a database, not loose files, so an agent cannot simply edit a project on disk. Exported .drp projects, .drt timelines and .drx grade stills can be read and written offline by community tooling, and Resolve imports FCPXML, OTIO, EDL, AAF, SRT and .cube LUTs in both editions, which is how agents reach the free edition without scripting.
samuelgursky/davinci-resolve-mcp README, Advanced server section, read
Built-in AI in DaVinci Resolve
Resolve's AI runs locally on the DaVinci Neural Engine, with no credits or cloud account, and almost all of it is Studio only. Some tools need a model pack from the Extras Download Manager first. The 21.1 MCP integration is not a built-in assistant: you talk to Claude, Codex or another client, and it calls Resolve.
Magic Mask (v2 since 20)
Click a person or object to get a tracked matte for a secondary grade or a Fusion composite.
Studio only. Introduced in 17; v2 in 20, renderable in place as a matte node in 21.
DaVinci Resolve free vs Studio (Reference Manual headings), read
Audio Transcription and Text Based Editing
Transcribes dialogue so you can search it, cut by deleting words and generate subtitles from audio.
Studio only. Transcription and subtitles from audio arrived in 18.5; speaker detection in 19.
IntelliScript
Builds a timeline from a text script by matching it to transcribed takes.
Studio only. Added in 20.
AI Animated Subtitles and Multicam SmartSwitch
Animates caption words as they are spoken; switches multicam angles by speaker detection.
Studio only. Added in 20; SmartSwitch is scriptable since 21.1.
IntelliTrack
AI point tracking for windows and stabilisation, and automatic audio panning that follows a subject in Fairlight.
Studio only. Added in 19.
British Cinematographer, Blackmagic Design announces DaVinci Resolve 19, read
IntelliSearch and Slate ID
Searches clips by face, object or spoken words after a one-time analysis; reads clapperboards into metadata.
Studio only, with Extras downloads. Added in 21; scriptable with AnalyzeForIntellisearch and AnalyzeForSlate.
Blackmagic scripting README, Studio and AI Scripting APIs, read
Speech Generator and Voice Convert
Text to speech from Blackmagic's voices or a voice made from about 10 seconds of audio; converts one voice to another.
Studio only. Voice Convert added in 20, Speech Generator in 21 (Extras download); scriptable with GenerateSpeech.
AI plugins for DaVinci Resolve (Blackmagic 21 press release, 14 April 2026), read
Voice Isolation, Dialogue Separator, Music Remixer
Strips noise from dialogue, splits voice from background and room, and remixes music stems.
Studio only. Dialogue Separator and Music Remixer added in 19.
British Cinematographer, Blackmagic Design announces DaVinci Resolve 19, read
AI Audio Assistant, IntelliCut, Dialogue Matcher, Music Editor
Builds a rough mix from timeline audio, removes silences and checkerboards speakers, matches takes, and fits music to length.
Studio only. Added in 20. The Audio Assistant has no scripting call.
Relight, Depth Map, CineFocus
Adds virtual lights, builds a depth matte, and changes focus and aperture after the shot.
Studio only. Relight in 18.5, CineFocus in 21.
DaVinci Resolve free vs Studio (Reference Manual headings), read
Face tools and Object Removal
Face Refinement, Beauty, Blemish Removal, Face Reshaper and Face Age Transformer; removes objects across a tracked shot.
Studio only. Face Reshaper, Face Age Transformer and Blemish Removal added in 21.
AI plugins for DaVinci Resolve (Reference Manual headings), read
Super Scale, UltraSharpen, Motion DeBlur, Speed Warp, UltraNR
Neural upscaling, sharpening, motion-blur removal, frame interpolation for slow motion and AI spatial noise reduction.
Studio only. UltraNR in 19; UltraSharpen and Motion DeBlur in 21.
DaVinci Resolve free vs Studio (Reference Manual headings), read
Smart Reframe, Scene Cut Detection, Remove Silence, Beat Detector
Re-crops for vertical and square, splits flattened files at cuts, deletes silences and marks beats.
Studio only.
AI plugins for DaVinci Resolve (Reference Manual headings), read
Dialogue Leveler
Rides dialogue levels without compressor pumping.
Free and Studio: the manual gives it no Studio marker.
AI plugins for DaVinci Resolve (Reference Manual headings), read
AI assistant integration (MCP)
Lets Claude, Claude Code, Codex, Antigravity and Grok Build analyse projects, organise media, adjust settings and batch render by conversation.
Studio only. Added in 21.1 (8 September 2026), with 20 new scripting APIs.
DaVinci Resolve pricing
Freemium: the free edition costs nothing, and Studio is a one-time $295 licence with free updates (or a $30 a month Blackmagic Cloud rental); scripting from outside the app, the MCP server and nearly all AI tools need Studio.
| Plan | Price | What it’s for |
|---|---|---|
| DaVinci Resolve (free) | $0 | Edit, colour, Fusion and Fairlight up to UHD 60 fps; Lua scripts from Workspace > Scripts; no external scripting, Python, MCP server or most Neural Engine tools since 21.1. |
| DaVinci Resolve StudioUnlocks automation | $295 once (on sale at $236 until 20 November 2026) | External Python and Lua scripting, the native MCP server, Workflow Integrations, the Neural Engine AI tools, above UHD and 60 fps, HDR delivery. Updates have been free. |
| Studio via Blackmagic CloudUnlocks automation | $30 a month per licence | A rented Studio licence tied to a Blackmagic Cloud ID; the same features as the perpetual licence. |
| Bundled Studio licence | Included with some hardware | Blackmagic cinema cameras, the Speed Editor, Editor Keyboard and the Mini and Advanced panels include a Studio activation code. |
Voyager
Use DaVinci Resolve with Voyager
Studio uses Voyager’s CLI over the official Blackmagic MCP on supported installs or the Python SDK on older versions, with Local external scripting enabled. Free-edition in-app commands run on macOS: import requires Resolve 18.5 or later and editing requires 21.1 or later; on Windows Voyager can prepare a timeline for manual import. Voyager inspects the current timeline and preserves existing work. Free commands also support editable Fusion motion graphics and keyframed titles, framing and audio adjustments, and SRT captions for burned-in renders; advanced color controls, speed ramps and Edit-page OpenFX remain outside them. The agent can generate supporting media through your connected providers or Voyager credits. App licences and generation costs are separate.
Requirements: Install Resolve from Blackmagic Design; Mac App Store Resolve is unsupported. Enable Local external scripting for Studio. Free in-app commands require macOS, with 18.5+ for import and 21.1+ for editing; Windows uses manual timeline import. Windows and Linux Voyager builds are alpha; computer control is unavailable on Linux.
Try asking
- “Cut my interview into a 60 second highlight in Resolve, import SRT captions for a burned-in 9:16 render using the workflow supported by my edition.”
- “Build a new Resolve timeline from these clips in the order of this script and add a blue marker at the start of each scene.”
- “Apply this LUT to every clip on V1 of my Resolve timeline and render ProRes 422 HQ plus an H.264 proxy.”
- “Make a new version of my Resolve timeline with a short cross dissolve between every clip and a fade in and out.”
Frequently asked questions
Does DaVinci Resolve have an API?
Yes. Resolve has a Python and Lua scripting API (DaVinciResolveScript) that reaches projects, the media pool, timelines, markers, LUTs and CDLs, Fusion comps, transcription and the render queue. Calling it from an outside program needs Resolve Studio with Preferences > System > General > External scripting using set to Local. There is no REST or cloud API.
Is DaVinci Resolve's Python API free?
Not since 21.1. Resolve 21.1 (8 September 2026) moved Python scripting, external scripting and the 20 new APIs to Studio, which costs $295 once. On the free edition, Lua scripts run from Workspace > Scripts still list and run, according to community measurements on build 21.1.0.17; Blackmagic does not document that boundary.
Is there an official DaVinci Resolve MCP server?
Yes, in DaVinci Resolve Studio 21.1 and later. It is a ResolveMCP executable inside the application, set up from File > Setup AI Assistants for Claude Desktop, Claude Code, Codex, Google Antigravity and Grok Build, and any other stdio MCP client can point at its path. The free edition does not include it.
Does the free version of DaVinci Resolve work with AI agents?
Partly. Without Studio, no outside process can connect, so agents either use a Lua bridge script you start from Workspace > Scripts each session or write files for Resolve to import: FCPXML or OTIO timelines, SRT captions, marker CSVs and .cube LUTs. Community Python bridges for the free edition stopped working with 21.1.
Can ChatGPT control DaVinci Resolve?
Through Codex, yes; through ChatGPT on the web, no. Resolve Studio 21.1's native MCP server runs locally over stdio and its setup targets Codex, which OpenAI ships as a CLI and inside the ChatGPT desktop app. The web version of ChatGPT cannot reach a local server, and Blackmagic has not published an app inside ChatGPT.
Can Claude edit videos in DaVinci Resolve?
Yes, with Resolve Studio 21.1 or a community MCP server. Claude can build and reorder timelines, import and organise media, add markers, transitions and fades, apply LUTs, set up multicam clips, transcribe and batch render. It cannot set colour wheels, curves or retime curves, or trim clips already on a timeline, because the scripting API has no calls for them.
Does DaVinci Resolve have built-in AI?
Yes. The DaVinci Neural Engine runs Magic Mask, transcription and text-based editing, IntelliScript, IntelliTrack, IntelliSearch, Voice Isolation, Speech Generator, Smart Reframe, Super Scale and more, locally on your GPU with no credits. Nearly all of it is Studio only; Dialogue Leveler is one of the few tools without a Studio marker.
Which DaVinci Resolve AI features need Studio?
Almost all of them. The Resolve 21 manual marks Magic Mask, IntelliTrack, transcription, IntelliScript, Smart Reframe, Scene Cut Detection, IntelliSearch, Voice Isolation, Dialogue Separator, Music Remixer, Speech Generator, Voice Convert, Relight, Depth Map, the face tools, Super Scale and UltraNR as Studio Version Only, and 21.1 adds the AI assistant integration to that list.
Can DaVinci Resolve run headless or from the command line?
Yes, with Studio. Launch the Resolve binary with the -nogui flag and Blackmagic says the scripting APIs continue to work, so a script can import, build and render without a window. Resolve has no separate render CLI; community tools such as dvr add one on top of the API.
Can AI colour grade in DaVinci Resolve?
Only through looks it can express as data. An agent can apply LUTs to specific nodes, set CDL values, apply grades from DRX stills and write DCTL shaders, but primary wheels, curves, qualifiers and power windows have no scripting calls. Shot matching from a reference frame is done outside Resolve and brought back as a LUT.
Can an AI cut a video from a transcript in Resolve?
Yes. On Studio, the agent can transcribe with Resolve's own TranscribeAudio, read the words back with GetTranscription (21.1) and build a timeline from the source ranges it picks. On the free edition it transcribes with an outside model and imports the cut as an FCPXML or OTIO timeline.
What are DaVinci Resolve Workflow Integration plugins?
They are Electron apps that Resolve Studio loads under Workspace > Workflow Integrations, with JavaScript access to the same Resolve API, used for vendor panels such as asset libraries and review tools. They are Studio only. For agent control you do not need one; scripts and the MCP server reach the same API.
Can AI write DCTL for DaVinci Resolve?
Yes. DCTL is a C-like colour shader language, and an agent can write the file; Resolve 21.1 added ValidateDCTL and EncryptDCTL to the scripting API so an agent can check it compiles. Applying a DCTL as an effect is marked Studio only in the manual.
Does DaVinci Resolve support OpenFX plugins?
Yes. Resolve loads OpenFX 1.4 image-effect plugins on the Color and Fusion pages in both editions, but each vendor decides its own requirement: Colourlab AI states it runs on the free edition, while Topaz Video's OFX plugin requires Studio. Blackmagic ships an OpenFX developer kit with sample plugins.
Can AI make motion graphics in DaVinci Resolve's Fusion page?
Yes. Fusion has its own scripting API for adding tools, setting inputs, keyframes and expressions and rendering comps, and open-source servers such as open-fusion-mcp build titles and animated scenes as editable node graphs on Studio 21.1.
Can an AI agent edit DaVinci Resolve project files directly?
Not the live project, which sits in a project library database. Exported .drp projects, .drt timelines and .drx grade stills can be read and edited offline by community tools such as the advanced server in davinci-resolve-mcp, and interchange formats (FCPXML, OTIO, EDL, AAF, SRT) import into either edition.
How much does DaVinci Resolve Studio cost?
$295 as a one-time licence, with updates free so far; Blackmagic is selling it for $236 until 20 November 2026. It can also be rented through Blackmagic Cloud for about $30 a month per licence, and it comes free with several Blackmagic cameras, the Speed Editor and the larger grading panels.
Is it safe to let an AI agent run scripts in DaVinci Resolve?
With care. Blackmagic's manual says scripts the assistant creates share its access to disk, network and other resources, and the native and community servers can run arbitrary Python. Work on a duplicated timeline, keep project backups, and keep External scripting on Local unless you need network access on port 1144.
Does Voyager work with DaVinci Resolve?
Voyager supports this workflow, subject to the app, edition and platform requirements. Studio uses Voyager’s CLI over the official Blackmagic MCP on supported installs or the Python SDK on older versions, with Local external scripting enabled. Free-edition in-app commands run on macOS: import requires Resolve 18.5 or later and editing requires 21.1 or later; on Windows Voyager can prepare a timeline for manual import. Voyager inspects the current timeline and preserves existing work. Free commands also support editable Fusion motion graphics and keyframed titles, framing and audio adjustments, and SRT captions for burned-in renders; advanced color controls, speed ramps and Edit-page OpenFX remain outside them. Requirements: Install Resolve from Blackmagic Design; Mac App Store Resolve is unsupported. Enable Local external scripting for Studio. Free in-app commands require macOS, with 18.5+ for import and 21.1+ for editing; Windows uses manual timeline import. Windows and Linux Voyager builds are alpha; computer control is unavailable on Linux.
Go further
Guides on Voyager
- DaVinci Resolve MCP: Studio setup and community servers
- AI plugins for DaVinci Resolve: free, Studio and paid add-ons
- DaVinci Resolve free vs Studio: is the $295 upgrade worth it?
- Auto captions in DaVinci Resolve Free with AI
- Remove background noise in DaVinci Resolve Free with AI
- Remove a video background in DaVinci Resolve Free with AI
- Remove a green screen in DaVinci Resolve Free
- How to make vertical video in DaVinci Resolve Free
- How to stabilize video in DaVinci Resolve Free
- Smooth slow motion in DaVinci Resolve Free
Related apps
How this page is made
Every fact on this page links to the vendor documentation, pricing page, repository or announcement it was read from, with the date it was read. MCP server stars and activity are read from GitHub on the date shown. Setup steps for each AI assistant are generated from that assistant’s documented config format and the server’s own install instructions. Anything we could not verify is marked as unverified rather than guessed. Trademarks belong to their owners; Voyager isn’t affiliated with or endorsed by them.