Claude 데스크톱과 같은 MCP 클라이언트에서 DaVinci Resolve Studio를 제어합니다.

이 프로젝트는 Resolve 프로젝트, 타임라인, 미디어, 융합, 색상, 오디오, 재생, 로컬를 통해 렌더링 작업 모형 Context 의정서 서버.

무엇 그것

서버 제공:

• 수정 및 제어를위한 32 MCP 도구;
• 현재 해결 상태를 설명하는 6개의 read-only MCP 자원;
• Windows, macOS에서 DaVinci Resolve 스크립트 API의 자동 발견 그리고 리눅스;
• 보호 된 네이티브 모듈 프로브, 그래서 깨진 fusionscript import does not MCP 서버 충돌;
• Windows 런타임 고립은 incompatible 적재에서 녹을 막기 위하여 파이썬 DLL.

MCP 클라이언트의 예 요청:

“제품 출시”라는 프로젝트 만들기

이 세 개의 클립을 가져 와서 "Rough Cut"라는 타임 라인을 만듭니다.

메모 "Review transition"로 프레임 240에서 파란색 마커를 추가하십시오.

“Approved Looks” 앨범에서 여전히 현재 등급을 저장하십시오.

요구 사항

• **DaVinci Resolve Studio 18 또는 더 새로운. ** 외부 스크립트가 활성화되어야 합니다.
• 64비트 CPython 3.10 또는 3.11. Resolve의 scripting 모듈은 여전히 가져올 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