DaVinci Resolve MCP Server

Control DaVinci Resolve Studio from AI assistants via the official Scripting API, with source-safe media tooling.

Unverified

stdio (local)

No auth

Python

View repo 1.3k npm

Add to your client

Copy the config for your MCP client and paste it into its config file.

Install / run

npx davinci-resolve-mcp setup

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "davinci-resolve-mcp-server": {
      "command": "/path/to/venv/bin/python",
      "args": [
        "/path/to/davinci-resolve-mcp/src/server.py"
      ],
      "env": {
        "RESOLVE_SCRIPT_API": "/path/to/DaVinci Resolve/Developer/Scripting",
        "RESOLVE_SCRIPT_LIB": "/path/to/fusionscript.so-or-dll",
        "PYTHONPATH": "/path/to/DaVinci Resolve/Developer/Scripting/Modules"
      }
    }
  }
}

Step-by-step guides: Add to Claude Desktop · Add to Cursor · Add to Windsurf

Before you start

DaVinci Resolve Studio 18.5+ on macOS, Windows, or Linux (the free edition does not support external scripting)
Python 3.10+ (3.10-3.12 is the lowest-risk range)
Resolve external scripting set to Local (Preferences > General > External scripting using > Local)

About DaVinci Resolve MCP Server

DaVinci Resolve MCP Server bridges AI assistants and DaVinci Resolve Studio through Blackmagic's official Scripting API, exposing 336 covered API methods (98.5% live-tested against Resolve 19.1.3 and 20.3.2 Studio). It offers a low-context compound mode that groups operations behind action parameters, plus a granular mode with one tool per API method. Capabilities span app/project control, media pool ingest, source-safe media analysis (FFprobe/FFmpeg/Whisper, 2-pop/slate-clap sync detection, metadata writeback), timeline editing and conform, review markers, color grading, Fusion comps, Fairlight audio, render/deliver, and extension authoring. A universal Python installer auto-detects platform and Resolve paths and configures Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, Zed, Continue, Cline, Roo Code, and JetBrains IDEs.

Tools & capabilities (11)

resolve_control

App and project control: launch/reconnect, page switching, version info (including local MCP version and update-check status), and update-status checks.

media_pool

Media pool and ingest: safe import, image sequences, multicam prep timelines, bin organization, metadata normalization, metadata field inventory, marks/annotations, and relink/proxy/full-resolution guards.

media_analysis / analyze_media

Source-safe file/clip/bin/project analysis: 2-pop and slate-clap sync-event detection, default Resolve metadata and Media Pool marker writeback, persisted analysis artifacts, host_chat_paths visual analysis finalized via commit_vision, and transcription (all opt-out).

timeline / timeline_item

Timeline editing and conform plus per-item actions: track/item probing, title text key scans/writes, copy/move/duplicate helpers, range operations, gap/overlap detection, source ranges, and interchange exports/imports. Includes retime, transform, crop, composite, audio, and keyframe actions.

review markers

Review annotations: timeline/item/clip markers, custom data, flags, clip color, copy/move/sync cleanup, review reports, and marker thumbnail review.

color / grading

Color and grading: node graph probing, CDL validation, grade copy, DRX/LUT helpers, grade versions, Gallery stills, and color groups.

fusion

Fusion: timeline-item comps, safe tool creation, input writes, port inspection, validated connections, and scoped bulk writes.

audio / fairlight

Audio and Fairlight: track/item probes, source mapping, guarded audio property writes, voice isolation, auto-sync planning, and transcription/subtitle probes.

render / deliver

Render and deliver: format/codec matrix probing, render settings validation, queued job lifecycle checks, and guarded Quick Export.

extension authoring

Fuse, DCTL, ACES DCTL, and Resolve-page Lua/Python script lifecycle helpers with safe MCP-marked install/remove.

setup

Manage local defaults from chat (get_defaults / set_defaults), including MCP update policy and intervals.

When to use it

List all projects and open a specific one, then create a timeline from clips in the current bin
Build a multicam prep timeline from selected camera angles while preserving source media
Detect 2-pops or slate claps and suggest record offsets for sync prep
Probe a timeline for gaps, overlaps, missing media, and source frame ranges
Build and validate a ProRes 422 HQ render plan and queue the job
Snapshot a clip's grade, validate a CDL update, and export a temp LUT
Create a Fusion TextPlus overlay on a clip and verify graph connections

Security notes

The default server is a local stdio process launched by your MCP client; it does not expose a network listener or built-in multi-user auth surface. Tool metadata includes MCP client-safety hints for read-only, destructive, idempotent, and external-resource operations. Source media is treated as immutable — the server must not modify, transcode, proxy, or create derivatives of source media unless the user explicitly asks. DaVinci Resolve external scripting must be set to 'Local'. See SECURITY.md for operational boundaries and confirmation guidance.

DaVinci Resolve MCP Server FAQ

Does this work with the free edition of DaVinci Resolve?

No. Only DaVinci Resolve Studio 18.5+ supports the external Scripting API. The free edition does not support external scripting.

Which Python versions are supported?

Python 3.10+, with 3.10-3.12 being the lowest-risk range. 3.13/3.14 also work on recent Resolve builds (verified on Studio 20.3.2), but older builds may fail to connect on 3.13+, in which case use 3.10-3.12.

What is the difference between compound and full server modes?

Compound mode (src/server.py, ~32-34 tools) groups related Resolve operations behind action parameters to keep context usage low and is recommended for most assistants. Full/granular mode (src/server.py --full or src/resolve_mcp_server.py, 341 tools) exposes one MCP tool per Resolve API method for power users.

Will it modify or transcode my source media?

No. The project treats camera originals as immutable. Analysis tools read source files and write reports only to sidecar, scratch, or project analysis directories; the server will not modify, transcode, proxy, or create derivatives of source media unless you explicitly ask.

#davinci-resolve #blackmagic #video-editing #color-grading #fusion #fairlight #media #post-production

Alternatives to DaVinci Resolve MCP Server

Compare all alternatives →

Figma Context MCP (figma-developer-mcp)

Design & Media

15k

Popular community server that feeds Figma layout data to coding agents via a Figma API token.

Verified

stdio (local)

API key

TypeScript

2 tools

Updated 23 days agoRepo

21st.dev Magic MCP

Design & Media

5.2k

Generate beautiful, modern UI components from natural-language descriptions inside your IDE.

Unverified

stdio (local)

API key

TypeScript

4 tools

Updated 4 months agoRepo

Shadcn UI v4 MCP Server

Design & Media

2.8k

Give AI assistants full access to shadcn/ui v4 components, blocks, demos, and metadata across React, Svelte, Vue, and React Native.

Unverified

stdio (local)

API key

TypeScript

7 tools

Updated 1 month agoRepo

Compare DaVinci Resolve MCP Server with:

vs Figma Context MCP (figma-developer-mcp)vs 21st.dev Magic MCP vs Shadcn UI v4 MCP Server vs MiniMax MCP Server (Official)