通过MCP客户端如Claude Desktop控制达芬奇Resolve Studio。

该项目展示了Resolve项目、时间线、媒体、Fusion、色彩、音频， 通过本地程序进行播放和渲染操作 模型上下文协议服务器。

它的作用

服务器提供：

• 32 个用于编辑和控制 Resolve 的 MCP 工具;
• 6个只读MCP资源，描述当前的Resolve状态;
• 在Windows、macOS上自动发现达芬奇Resolve脚本API， 以及Linux;
• 受保护的本地模块探针，因此损坏的fusionscript导入不会 导致MCP服务器崩溃;
• Windows运行时隔离以防止Resolve加载不兼容的 Python DLL。

MCP客户端的示例请求：

创建一个名为“产品发布”的项目。

导入这三个片段，创建一个名为“粗剪”的时间线。

在第240帧添加一个蓝色标记，注明“Review transition”。

将当前成绩保存为“Approved Looks”相册中的静态照片。

要求

• DaVinci Resolve Studio 18 或更新版本。 必须启用外部脚本。
• 64位 CPython 3.10 或 3.11. Resolve 的脚本模块仍然会导入 imp，该功能已从 Python 3.12 中移除。

DaVinci Resolve MCP Server

Control DaVinci Resolve Studio from MCP clients such as Claude Desktop.

This project exposes Resolve projects, timelines, media, Fusion, color, audio, playback, and rendering operations through a local Model Context Protocol server.

What it does

The server provides:

• 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, and Linux;
• a protected native-module probe, so a broken fusionscript import does not crash the MCP server;
• Windows runtime isolation to prevent Resolve from loading an incompatible Python DLL.

Example requests from an MCP client:

Create a project called “Product Launch”.

Import these three clips and create a timeline called “Rough Cut”.

Add a blue marker at frame 240 with the note “Review transition”.

Save the current grade as a still in the “Approved Looks” album.

Requirements

• 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 scripting using → Local

The free edition of Resolve does not expose the external scripting connection used by this server. The MCP process can start, but it will remain disconnected.

Installation

Clone the repository first:

git clone https://github.com/Tooflex/davinci-resolve-mcp.git
cd davinci-resolve-mcp

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 those builds.

Install Python 3.10:

winget install --id Python.Python.3.10 -e

Create the environment and install the dependencies:

& "$env:LOCALAPPDATA\Programs\Python\Python310\python.exe" -m venv .venv310
.\.venv310\Scripts\python.exe -m pip install --upgrade pip
.\.venv310\Scripts\python.exe -m pip install -e .

Start the server through the Windows launcher:

.\run_server.ps1

Always use run_server.ps1 on Windows. It pins Resolve to the correct Python runtime, isolates PATH, and configures the scripting API paths before starting the server.

macOS

Create a virtual environment with CPython 3.10 or 3.11:

python3.11 -m venv .venv
./.venv/bin/python -m pip install --upgrade pip
./.venv/bin/python -m pip install -e .

Start the server:

./.venv/bin/davinci-resolve-mcp

The standard Resolve API locations are detected automatically:

• /Library/Application Support/Blackmagic Design/DaVinci Resolve/Developer/Scripting/Modules