Higgsfield DaVinci Resolve MCP

Local MCP server for working with the Color page in DaVinci Resolve Studio. The package includes a bridge to the official Python Scripting API and an offline davinci-film-colorist skill with references and LUT/DCTL assets.

Requirements

• Node.js 24 or later.
• DaVinci Resolve Studio 21.1 with a valid Studio license, running on the MCP host.
• In Resolve, set Preferences → System → General → External scripting → Local and restart if prompted.
• A project with a timeline and selected video clip on the Color page.

The bundled ResolvePython executable is used by default on macOS. On other installations, set RESOLVE_PYTHON to the full path of the official ResolvePython executable.

Installation

npm install --global @higgsfield_org/davinci-resolve-mcp
fnf-davinci doctor
fnf-davinci config

Add the printed server entry to your MCP client's configuration and reconnect the client. Use fnf-davinci config --format toml for Codex. The stdio executable is fnf-davinci-mcp.

doctor checks the live Studio session. After connecting the MCP client, call dr_status and confirm it returns the current project, timeline and clip IDs.

Tools

• dr_status and dr_inspect_color inspect the active Color-page context.
• dr_create_version, dr_set_cdl, dr_set_lut and dr_save_project change the project.
• dr_get_skill reads bundled film-colorist guidance; dr_get_skill_asset locates bundled files on the local MCP host.

Use the exact IDs from a recent dr_status for writes. Install LUTs through the bundled helper or Resolve UI and refresh Resolve's LUT list before calling dr_set_lut.

Troubleshooting and limits

A timed-out write blocks further writes until you inspect Resolve and call dr_acknowledge_uncertain for the same project. This acknowledgement does not retry the write. dr_set_cdl has no readback API; check the actual frame and scopes. An asset path alone does not mean its LUT is installed in Resolve. Free Resolve may expose the Python module but does not establish Studio scripting access.