davinci-resolve-mcp
Provides tools to control DaVinci Resolve (including the free Community edition) via a bridge script, enabling project management, media import, timeline operations, and more.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@davinci-resolve-mcp import video from Downloads to current project"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
DaVinci Resolve MCP — Free / Community edition
Drive DaVinci Resolve from Claude Code (or any MCP client) to edit videos — on the free Community edition, which blocks normal external scripting.
Why this is different
DaVinci Resolve Free does not allow an external process to connect via the
scripting API (scriptapp("Resolve") returns nil); the permission toggle that
Studio exposes is absent. Verified on Resolve 21.0.0.48 across Python 3.9–3.14.
However, scripts running inside Resolve have full API access. So this project uses a bridge:
Claude Code ──MCP──► server.py (this repo) ──files──► resolve_bridge.lua (inside Resolve) ──► live `resolve` objectbridge/resolve_bridge.lua— runs inside Resolve, polls a request file, executes against theresolveobject, writes a JSON response.davinci_mcp/— the external MCP server; each tool sends one RPC to the bridge.
Request/response are exchanged via files in ~/.davinci-mcp-bridge/.
Related MCP server: Resolve Claude MCP
Setup
Install deps and the bridge helper:
uv sync python3 scripts/install_bridge.pyThe installer copies the bridge into Resolve's Scripts folder and prints the exact start/registration commands for your machine.
Start the bridge inside Resolve (it must be running for any tool to work):
Workspace ▸ Scripts ▸ Comp ▸ MCP_Bridge (after restarting Resolve once), or
Workspace ▸ Console, switch to Lua, and run
dofile("<repo>/bridge/resolve_bridge.lua").
You should see
[bridge] UPandops registered=.... It keeps running and does not freeze the Resolve UI.Register the MCP server with Claude Code:
claude mcp add davinci-resolve -- uv run --directory <repo> davinci-resolve-mcpThen in Claude Code, call
bridge_statusto confirm the connection.
Tools
resolve_info, list_projects, current_project, open_project,
create_project, save_project, import_media, list_media,
list_timelines, current_timeline, create_timeline,
append_all_to_timeline, add_marker, and resolve_eval (run arbitrary Lua —
escape hatch for anything not yet wrapped).
Limitations (Free edition)
Studio-only API calls return errors: transcription, subtitles-from-audio, AutoSync, Magic Mask, IntelliSearch, motion-deblur, speech gen, Dolby Vision.
Render limits: 8-bit, ≤ UHD 3840×2160, ≤ 60 fps. Applying a Studio-only effect watermarks the export.
Credits
Architecture and Studio-edition tool designs informed by samuelgursky/davinci-resolve-mcp (MIT). This project is a from-scratch Free-edition rework using the bridge approach.
Available Tools
67 toolsadd_color_versionB
Add a color version to the current video item (0=local, 1=remote).
Inputs: name (required), version_type.
add_fusion_generatorC
Insert a Fusion generator at the playhead of the current timeline.
Inputs: name (required).
add_fusion_titleA
Insert a Fusion title (e.g. 'Text+') at the playhead of the current timeline.
Inputs: name (required).
add_generatorA
Insert a generator (e.g. 'Solid Color', 'Grey Scale') at the playhead.
Inputs: name (required).
add_markerC
Add a marker to the current timeline at a frame.
Inputs: frame (required), color, name, note, +2 more.
add_render_jobA
Add the current render settings to the render queue; returns the job id.
Inputs: no named parameters.
add_titleB
Insert a title generator (e.g. 'Text', 'Text+') at the playhead of the current timeline.
Inputs: text_or_title.
add_trackA
Add a track of the given type (video, audio, subtitle).
Inputs: track_type.
append_clipsA
Append media pool clips to the current timeline (all clips if names omitted).
Inputs: clip_names.
assemble_rough_cutB
One-shot rough cut: (optionally create+select a bin) import the media files, create a timeline, and append every imported clip to it.
Inputs: media_paths (required), timeline_name (required), bin_name.
bridge_statusA
Check whether the in-Resolve bridge is running and reachable. Use this when other tools report 'bridge_not_running'.
Inputs: no named parameters.
close_projectA
Close the current project (prompts to save in Resolve if needed).
Inputs: no named parameters.
create_binB
Create a new bin (sub-folder) in the media pool root.
Inputs: name (required).
create_projectC
Create and open a new project.
Inputs: name (required).
create_timelineC
Create a new empty timeline.
Inputs: name (required).
create_timeline_from_clipsB
Create a timeline pre-filled with the named media pool clips.
Inputs: name (required), clip_names (required).
current_projectA
Current project's name and timeline count.
Inputs: no named parameters.
current_timelineB
Current timeline name, frame range and track counts.
Inputs: no named parameters.
delete_clipsB
Delete media pool clips (root folder) by name.
Inputs: names (required).
delete_markerC
Delete the marker at a frame.
Inputs: frame (required).
delete_markers_by_colorA
Delete all markers of a color ('All' deletes every marker).
Inputs: color (required).
delete_render_jobC
Remove a render job from the queue.
Inputs: job_id (required).
delete_timelineC
Delete a timeline by name.
Inputs: name (required).
delete_trackB
Delete the track at index (1-based) of the given type.
Inputs: track_type (required), index (required).
duplicate_timelineC
Duplicate a timeline under a new name.
Inputs: name (required), new_name (required).
export_timelineC
Export a timeline. export_type is a Resolve constant name, e.g. EXPORT_EDL, EXPORT_FCPXML_1_10, EXPORT_OTIO, EXPORT_AAF, EXPORT_DRT.
Inputs: file_path (required), export_type (required), timeline_name.
free_render_checkA
Advisory: flag render settings that exceed DaVinci Resolve Free limits (8-bit, <= UHD 3840x2160, <= 60fps). Does not change anything.
Inputs: width (required), height (required), fps (required), bit_depth.
get_clip_propertyB
Get a media pool clip's property by clip name (empty property = all).
Inputs: name (required), property.
get_markersA
All markers on the current timeline, keyed by frame.
Inputs: no named parameters.
get_num_nodesC
Number of color nodes on the current video item.
Inputs: no named parameters.
get_project_settingA
Read a project setting (empty key returns all settings).
Inputs: key.
get_render_codecsC
Available codecs for a render format.
Inputs: format (required).
get_render_formatsA
Map of available render formats to file extensions.
Inputs: no named parameters.
get_render_job_listB
List queued render jobs.
Inputs: no named parameters.
get_render_job_statusC
Status/progress of a render job.
Inputs: job_id (required).
get_timeline_itemsB
List clips on a track (name, start, end, duration).
Inputs: track_type, index.
get_timeline_settingB
Read a current-timeline setting (empty key = all).
Inputs: key.
get_track_countB
Number of tracks of a type: video, audio, or subtitle.
Inputs: track_type.
import_mediaA
Import media files (absolute paths on the Resolve machine) into the current media pool folder.
Inputs: paths (required).
import_timelineC
Import a timeline from AAF/EDL/XML/FCPXML/DRT/OTIO. Returns the new timeline name.
Inputs: file_path (required), options.
is_renderingB
Whether a render is in progress.
Inputs: no named parameters.
list_binsB
List sub-folder (bin) names in the media pool root.
Inputs: no named parameters.
list_mediaA
List clips in the media pool root (name, type, fps, duration, resolution).
Inputs: no named parameters.
list_projectsA
List project names in the current project-manager folder.
Inputs: no named parameters.
list_render_presetsB
List available render presets.
Inputs: no named parameters.
list_timelinesB
List timeline names in the current project.
Inputs: no named parameters.
load_render_presetC
Load a render preset by name.
Inputs: name (required).
open_pageA
Switch the active page: media, cut, edit, fusion, color, fairlight, deliver.
Inputs: page (required).
open_projectB
Open an existing project by name.
Inputs: name (required).
place_clipB
Place a media pool clip onto the current timeline with precise framing. start_frame/end_frame = in/out within the source; record_frame = where it lands on the timeline; media_type 1=video only, 2=audio only.
Inputs: clip_name (required), record_frame, start_frame, end_frame, +2 more.
render_to_fileA
Queue and start rendering the current timeline to target_dir/custom_name. Optionally load a render preset first (e.g. 'YouTube - 1080p', 'H.264 Master'). Free-edition limits apply: 8-bit, <= UHD 3840x2160, <= 60fps.
Inputs: target_dir (required), custom_name (required), preset.
resolve_evalA
Run arbitrary Lua inside Resolve against the live resolve object. Code MUST
return a value, e.g. 'return resolve:GetProjectManager():GetCurrentProject():GetName()'.
Escape hatch for operations not yet wrapped as a dedicated tool.
Inputs: lua_code (required).
resolve_infoA
Resolve product name, version, current page. Call first to confirm the bridge is connected.
Inputs: no named parameters.
save_projectB
Save the current project.
Inputs: no named parameters.
set_cdlC
Apply CDL (slope/offset/power as 'R G B' strings) to a node on the current item.
Inputs: node_index (required), slope (required), offset (required), power (required), +1 more.
set_clip_colorC
Set the clip color label of a timeline item (Orange, Apricot, Yellow, Lime, Olive, Green, Teal, Navy, Blue, Purple, Violet, Pink, Tan, Beige, Brown, Chocolate).
Inputs: track_type (required), track_index (required), item_index (required), color (required).
set_current_timelineC
Make the named timeline the current one.
Inputs: name (required).
set_item_propertyB
Set a timeline item property (Pan, Tilt, ZoomX, ZoomY, Opacity, CompositeMode, RetimeProcess, CropLeft, ...). Items are 1-based per track.
Inputs: track_type (required), track_index (required), item_index (required), property (required), +1 more.
set_lutC
Apply a LUT to a node (1-based) on the current video item.
Inputs: node_index (required), lut_path (required).
set_project_settingB
Set a project setting, e.g. timelineFrameRate, timelineResolutionWidth.
Inputs: key (required), value (required).
set_render_format_and_codecC
Set the current render format and codec.
Inputs: format (required), codec (required).
set_render_settingsB
Set render settings, e.g. {"TargetDir": "/out", "CustomName": "v1", "FormatWidth": 1920, "FormatHeight": 1080, "MarkIn": 0, "MarkOut": 240}.
Inputs: settings (required).
set_timeline_settingC
Set a current-timeline setting.
Inputs: key (required), value (required).
set_track_enableC
Enable or disable a track.
Inputs: track_type (required), index (required), enabled (required).
set_track_nameD
Rename a track.
Inputs: track_type (required), index (required), name (required).
start_renderB
Start rendering the queue.
Inputs: no named parameters.
stop_renderC
Stop rendering.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 67 tools
Most tools have clearly distinct purposes with detailed descriptions. However, there is some overlap between add_generator, add_title, add_fusion_generator, and add_fusion_title, which could cause confusion. Overall, the majority are well-disambiguated.
Tool names follow a verb_noun pattern generally, but there are inconsistencies such as 'list' vs 'get' (e.g., list_projects vs get_timeline_items), and some names like 'assemble_rough_cut' or 'resolve_eval' deviate. The mix is readable but not fully consistent.
With 67 tools, the server is very large for an MCP server. While DaVinci Resolve is complex, this number exceeds typical scope and may overwhelm agents. Several tools could be consolidated or are redundant (e.g., multiple render start/stop tools).
The tool set covers a wide range of operations: project management, media import, timeline editing, color grading, rendering, etc. It includes an escape hatch (resolve_eval) for missing functionality. Only minor gaps exist, such as lack of detailed audio editing tools.
Maintenance
Related MCP Connectors
MCP server for Clipkit — gives AI agents a video toolbox via the Clipkit schema.
Transcribe audio and video with Speechmatics speech-to-text from Claude and any MCP client.
AI video editor for agents and humans: timeline, captions, color, audio and generation as MCP tools.
Autonomous AI video editor over MCP: viral clips, captions, reframe, chroma key, MP4 export.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceConnects AI coding assistants (Cursor, Claude Desktop) to DaVinci Resolve, enabling control of video editing workflows through natural language commands for project management, timeline operations, and media pool tasks.MIT
- AlicenseBqualityDmaintenanceConnects DaVinci Resolve Studio to Claude AI via the Model Context Protocol, enabling natural language control over video editing, color grading, Fusion compositing, AI features, and more.53399MIT
- FlicenseAqualityBmaintenanceAn MCP server that gives Claude Code hands inside DaVinci Resolve Studio, enabling project management, status checks, snapshots, and arbitrary Python scripting via the Resolve API.51-
- AlicenseNot gradedqualityBmaintenanceEnables AI clients such as Claude Code to control DaVinci Resolve, including the free Lite edition, through a local HTTP server that runs inside Resolve's Scripts menu. It exposes 163 tools for editing, color, rendering, media pool, and Fusion title styling.8MIT