Davinci Resolve MCP Server

Control DaVinci Resolve Studio from MCP clients such as Claude Desktop. Exposed over MCP by the davinci resolve mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

• 32 MCP tools for editing and controlling Resolve;
• 6 read-only MCP resources describing the current Resolve state;
• automatic discovery of the DaVinci Resolve scripting API on Windows, macOS,
• a protected native-module probe, so a broken fusionscript import does not
• Windows runtime isolation to prevent Resolve from loading an incompatible

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Its toolset

Everything the assistant can do here goes through one of these:

• Windows — Use a regular 64-bit Python from python.org. Do not use a uv-managed standalone Python on Windows: Resolve's fusionscript.dll is known to crash with
• macOS — The standard Resolve API locations are detected automatically:
• Linux — The default Linux scripting path is /opt/resolve/Developer/Scripting/Modules

Configuration

You will need 3 environment variables: RESOLVE_SCRIPT_PATH, RESOLVE_SCRIPT_API, RESOLVE_SCRIPT_LIB. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• DaVinci Resolve Studio 18 or newer. External scripting must be enabled. - 64-bit CPython 3.10 or 3.11. Resolve's scripting module still imports imp, which was removed from Python 3.12. - The DaVinci Resolve scripting API installed with Resolve. - An MCP client such as Claude Desktop. Before starting the server, open Resolve and set: **Preferences → System → General → External

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the davinci resolve mcp mcp server does with a few real requests.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Davinci Resolve MCP's toolset — Windows, macOS, Linux — is a fair guide to whether it matches your workflow. It is maintained by Tooflex; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.