Chisle
코딩 에이전트 플러그인, 20개 실시간 작업에서 기본 모델 52% 활용, 간결한 페르소나와 출력 압축 제공
DaVinci Resolve Studio용 MCP 서버 통합
MCP server integration for DaVinci Resolve Studio
개발 도구Python · JavaScriptGitHub @samuelgursky직접 설치운영자 미확인
써 보셨어요? 한 번만 눌러 주세요. 로그인은 필요 없어요.
메이커가 쓴 소개는 위의 한 줄이 전부입니다. 더 자세한 내용은 저장소 README에서 읽을 수 있습니다. 저장소 README ↗
README 전체를 불러오는 중입니다.
README 전문 보기 ↗English | 简体中文
A Model Context Protocol (MCP) server that lets AI assistants control DaVinci Resolve Studio through the official Scripting API. It provides full API coverage plus guarded workflow helpers for editing, media pool organization, render setup, review markers, grading, Fusion, Fairlight, project lifecycle tasks, extension authoring, and source-safe media analysis.
A local browser control panel ships with the server for inspecting Resolve state, running source-safe analysis, drilling into analyzed clips and shots, and editing analysis output inline. See the Control Panel Guide for the full tour.
npx davinci-resolve-mcp setup
Before connecting, open DaVinci Resolve Studio and set Preferences > General > External scripting using to Local. (On the free edition that preference does not help — see Free edition below.) The npm launcher installs a managed copy under your user application-data directory, then runs the universal Python installer. The installer creates a virtual environment, detects Resolve paths, and can configure Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, Zed, Continue, Cline, Roo Code, OpenCode, Codex CLI, and JetBrains IDEs.
For source installs:
git clone https://github.com/samuelgursky/davinci-resolve-mcp.git
cd davinci-resolve-mcp
python install.py
For platform paths, client-specific config, and manual setup, see Installation and Configuration.
The installer and server check the latest GitHub release for MCP updates. Checks are best-effort and throttled; the server never blocks MCP startup for a prompt. The installer can prompt, snooze, ignore a release, disable checks, or apply an opt-in safe auto-update for clean git checkouts.
Blackmagic gates external scripting to Studio: on the free edition
scriptapp("Resolve") refuses a foreign process, whatever the preference says.
Through Resolve 21.0.x the Workspace ▸ Scripts menu was not gated — a script
launched from it is handed the live resolve object (measured on free 21.0.3.7) —
so the server can reach the free edition through a small script that runs inside
Resolve and re-exports it over an authenticated loopback listener. Resolve 21.1
moved Python scripting to Studio. On free 21.1 the Scripts menu no longer lists
.py files at all (reported on Fedora 44 in #203; a Lua script in the same folder
lists normally). Whether the Console still runs Python there is unconfirmed, so
treat the bridge as a 21.0.x path until that is measured.
python scripts/install_resolve_bridge.py
# restart Resolve, open a project, then: Workspace > Scripts > resolve_bridge
The installer and MCP client use ~/.config/davinci-resolve-mcp/bridge.json
by default. To keep the authenticated bridge config elsewhere, set
DAVINCI_RESOLVE_BRIDGE_CONFIG while running the installer and in the MCP
client environment; both sides will use that path.
Once that listener is running it is used automatically whenever external
scripting is unavailable — no environment variable required. Setting
DAVINCI_RESOLVE_BRIDGE=1 forces the bridge instead: it becomes the only
transport tried, so a bridge that stops answering reports its own fault rather
than quietly falling back to another transport. Use it when the bridge is the
path you intend to depend on.
On macOS, Resolve looks for Python 3 in exactly two places: the
PYTHON3HOME environment variable, then /usr/local/bin/python3. Homebrew,
pyenv, uv and conda land in neither, so the script silently never appears in the
menu. A python.org install works because its installer creates
/usr/local/bin/python3 — but you do not need one: point Resolve at the
interpreter you already have, no sudo required.
launchctl setenv PYTHON3HOME "$(python3 -c 'import sys; print(sys.prefix)')"
Use launchctl setenv, not export — Resolve is launched from the Dock and
never sees your shell's environment. Restart Resolve afterwards. A Lua canary is
installed alongside so you can tell "Python not detected" apart from a wrong
folder.
여기까지가 README 앞부분입니다. 나머지는 원문에서 읽을 수 있습니다. README 전문 보기 ↗