SSyncDev

DaVinci Resolve MCP Server

Drives DaVinci Resolve 21.1, free edition included, from Claude Code through a Lua bridge running inside the app.

Local server

What is the DaVinci Resolve MCP Server?

Resolve 21.1's free edition quietly broke most automation. Python scripts vanished from the Workspace > Scripts menu and external scripting is blocked, but Lua menu scripts still run. This DaVinci Resolve MCP server is built around that one remaining opening, and it works on Studio too.

How the bridge works

There are two halves. A small Lua script, started by hand from the Scripts menu, runs inside Resolve with the live resolve object. A standard-library Python server runs outside and talks MCP over stdio to Claude Code. The server never opens a network socket. Instead it writes requests as hex-encoded folder names in a private state directory; the bridge polls that directory every 30 ms, runs the Lua and returns the answer through Resolve's own preferences file, which the server reads. A round trip measures roughly 80 to 95 ms. Several Claude Code sessions can share one Resolve, because a lock serialises their requests.

What you need

  • macOS (Windows is not supported yet)
  • DaVinci Resolve 21.1.2, free or Studio
  • Claude Code, and Python 3.9 or newer at /usr/bin/python3
  • No pip packages

Install either through the Claude Code plugin marketplace or from a clone with ./install.sh, not both, or you will end up with two servers called davinci. The installer copies the Lua scripts into Resolve's Fusion scripts folder, creates the state directory with mode 0700 and registers the server. An optional --claude-desktop flag adds it to Claude Desktop as well. Restart Resolve once afterwards, since it only scans the Scripts folder at launch, then click Claude_MCP_Bridge in each session.

What Claude can do

The DaVinci Resolve MCP server has 33 named tools covering projects and settings, timelines and markers, the media pool, and the render queue. Typical requests: list timelines, drop a coloured marker at a timecode, import a folder of footage into a new timeline, or queue an MP4 render and report when it finishes. For everything else, run_lua executes arbitrary Lua inside Resolve, and scripting_api_docs searches the API reference that ships with the app so the agent writes that Lua correctly.

Caveats worth knowing

  • Destructive tools require confirm: true. run_lua is open-ended; set DAVINCI_MCP_DISABLE_RUN_LUA=1 to remove it.
  • A dialog in Resolve, such as a Studio upsell or a frame-rate prompt, blocks the bridge until you dismiss it.
  • Studio-only features should not be called on the free edition.
  • Not covered yet: color-page nodes, Fairlight, Fusion and compound clips, gallery stills, project archives, and automatic bridge start.
  • Anyone able to write to the state directory can run Lua as you.

For more desktop-app bridges, browse our other integrations, or see similar connectors for creative software.

Recorded tools

Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.

ToolWhat it does
resolve_statusChecks whether the Lua bridge inside Resolve is running. Call it first.
list_projectsLists projects in the Resolve project library.
get_project_infoReturns information about the current project.
get_project_settingReads a project setting.
open_projectOpens a project.
save_projectSaves the current project.
set_project_settingChanges a project setting.
open_pageSwitches Resolve to a given page.
list_timelinesLists the timelines in the current project.
get_timeline_infoReturns details of a timeline.
get_timeline_itemsLists the items on a timeline track.
get_timeline_markersLists the markers on a timeline.
set_current_timelineMakes a timeline the current one.
set_timecodeMoves the playhead to a timecode (HH:MM:SS:FF).
create_timelineCreates a new timeline.
add_markerAdds a marker to the current timeline.
delete_markersDeletes timeline markers.
insert_timeline_elementInserts an element into the timeline.
delete_timeline_itemsDeletes items from the timeline.
export_timelineExports a timeline to a file.
list_media_poolLists the contents of the media pool.
get_clip_propertiesReads the properties of a media pool clip.
create_media_pool_folderCreates a folder in the media pool.
import_mediaImports media files into the media pool.
append_clips_to_timelineAppends media pool clips to a timeline.
get_render_statusReports the status of render jobs.
list_render_optionsLists available render formats and options.
add_render_jobAdds a job to the render queue.
start_renderStarts rendering queued jobs.
stop_renderStops the current render.
delete_render_jobRemoves a job from the render queue.
run_luaRuns an arbitrary Lua 5.1 chunk inside Resolve for anything the named tools do not cover. Can be disabled.
scripting_api_docsSearches the scripting API reference shipped with Resolve so the agent can write correct Lua.

How to install the DaVinci Resolve MCP Server

/plugin marketplace add kingjamesch/davinci-resolve-mcp
/plugin install davinci-resolve@davinci-resolve-mcp
/davinci-resolve:setup

Run inside Claude Code. Alternatively clone the project and run ./install.sh (add --claude-desktop to register it in Claude Desktop too). Use one method, not both. Restart Resolve once, then start Workspace > Scripts > Claude_MCP_Bridge each session.

Configuration

VariableDescriptionRequired
DAVINCI_MCP_DISABLE_RUN_LUASet to 1 to remove the open-ended run_lua tool from the tool list.Optional

Frequently asked questions

Yes. It targets Resolve 21.1.2 free or Studio, using a Lua bridge because the free edition blocks Python and external scripting.