Drives DaVinci Resolve 21.1, free edition included, from Claude Code through a Lua bridge running inside the app.
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.
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.
/usr/bin/python3Install 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.
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.
confirm: true. run_lua is open-ended; set DAVINCI_MCP_DISABLE_RUN_LUA=1 to remove it.For more desktop-app bridges, browse our other integrations, or see similar connectors for creative software.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| resolve_status | Checks whether the Lua bridge inside Resolve is running. Call it first. |
| list_projects | Lists projects in the Resolve project library. |
| get_project_info | Returns information about the current project. |
| get_project_setting | Reads a project setting. |
| open_project | Opens a project. |
| save_project | Saves the current project. |
| set_project_setting | Changes a project setting. |
| open_page | Switches Resolve to a given page. |
| list_timelines | Lists the timelines in the current project. |
| get_timeline_info | Returns details of a timeline. |
| get_timeline_items | Lists the items on a timeline track. |
| get_timeline_markers | Lists the markers on a timeline. |
| set_current_timeline | Makes a timeline the current one. |
| set_timecode | Moves the playhead to a timecode (HH:MM:SS:FF). |
| create_timeline | Creates a new timeline. |
| add_marker | Adds a marker to the current timeline. |
| delete_markers | Deletes timeline markers. |
| insert_timeline_element | Inserts an element into the timeline. |
| delete_timeline_items | Deletes items from the timeline. |
| export_timeline | Exports a timeline to a file. |
| list_media_pool | Lists the contents of the media pool. |
| get_clip_properties | Reads the properties of a media pool clip. |
| create_media_pool_folder | Creates a folder in the media pool. |
| import_media | Imports media files into the media pool. |
| append_clips_to_timeline | Appends media pool clips to a timeline. |
| get_render_status | Reports the status of render jobs. |
| list_render_options | Lists available render formats and options. |
| add_render_job | Adds a job to the render queue. |
| start_render | Starts rendering queued jobs. |
| stop_render | Stops the current render. |
| delete_render_job | Removes a job from the render queue. |
| run_lua | Runs an arbitrary Lua 5.1 chunk inside Resolve for anything the named tools do not cover. Can be disabled. |
| scripting_api_docs | Searches the scripting API reference shipped with Resolve so the agent can write correct Lua. |
/plugin marketplace add kingjamesch/davinci-resolve-mcp
/plugin install davinci-resolve@davinci-resolve-mcp
/davinci-resolve:setupRun 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.
| Variable | Description | Required |
|---|---|---|
| DAVINCI_MCP_DISABLE_RUN_LUA | Set to 1 to remove the open-ended run_lua tool from the tool list. | Optional |
Run an Actual Budget ledger from your AI agent, with phone approvals for every change on paired machines.
An Odoo module that serves a read-only MCP endpoint at /mcp, scoped to each user's own access rights.
Lets coding agents run dev servers and workers as real systemd, launchd or Windows services, and read their logs.
Five npm MCP servers for Yandex Wordstat, Search, Webmaster, Metrika and Direct, for SEO and ads work in the Russian market.
Open-source screen recorder and editor whose MCP server lets an agent record, edit and export a demo video.
Agent memory that keeps every correction with its history, plus saved working state so a crashed run can resume.