Davinci Resolve MCP logo

Davinci Resolve MCP

by samuelgursky

Controls DaVinci Resolve from AI clients for editing, media organization, grading, rendering, and project management.

Install Davinci Resolve MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "samuelgursky-davinci-resolve-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "davinci-resolve-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

samuelgursky/davinci-resolve-mcp connects AI assistants to DaVinci Resolve through its scripting API, exposing editing, media, grading, rendering, Fusion, Fairlight, and project controls. It offers a compound mode with 37 grouped tools and a full mode with 390 granular tools, plus an optional advanced server. Use it when an agent needs to inspect or modify a live Resolve project, organize media, configure renders, or manage review and analysis workflows. A local browser control panel provides Resolve-state inspection and source-safe media analysis.

Use cases

  • Edit timelines through an AI assistant
  • Organize clips in the Resolve media pool
  • Configure renders and project settings
  • Review clips with markers and media analysis

Key features

  • 37 grouped compound tools
  • 390 granular Resolve API tools
  • Media, editing, grading, Fusion, and Fairlight controls
  • Authenticated free-edition bridge
  • Local browser control panel
  • Source-safe media analysis

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

20/24 checks healthy over the last 78d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 7d ago via OSV.dev · davinci-resolve-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars3.8kStargazers on the source repository.
npm downloads21kPackage downloads in the last 30 days.
Last commitTodayMost recent push to the default branch.
Directory activity12 viewsConfig copies, upvotes, and views on AllMCPs.

How Davinci Resolve MCP works

What samuelgursky/davinci-resolve-mcp does

samuelgursky/davinci-resolve-mcp lets MCP-compatible AI clients operate DaVinci Resolve through the official scripting API. Its coverage spans timeline and editing operations, media-pool organization, render configuration, markers for review, color work, Fusion, Fairlight, and project lifecycle actions. It also includes workflow helpers for extension authoring and source-safe media analysis.

The package supports two primary server surfaces. Compound mode groups related Resolve operations behind action parameters and exposes 37 tools, which helps limit context usage. Full mode exposes one tool for each Resolve API method, with 390 tools intended for users who need the granular interface. An optional Node-based advanced server is included for operations beyond the live scripting API.

How it works

The Python server communicates with a running Resolve installation using the official scripting interface. DaVinci Resolve Studio must be configured to permit local external scripting. On the free edition, the supported path is an in-application bridge: a script launched from Resolve exposes the live Resolve object through an authenticated loopback listener. The bridge is selected automatically when external scripting cannot be used, or can be forced with DAVINCI_RESOLVE_BRIDGE=1.

The bridge uses loopback communication, HMAC-signed requests, and one-use nonces. It is available as a documented path for free Resolve 21.0.x; Resolve 21.1 moved Python scripting to Studio, so free-edition compatibility depends on that version boundary.

A separate local control panel runs with venv/bin/python -m src.control_panel. It opens a token-protected browser interface for inspecting Resolve state, running source-safe analysis, reviewing analyzed clips and shots, and editing analysis results. Persisted analysis jobs refresh the local search index after successful slices.

Setup and configuration

The package can be installed with:

Terminal
npx davinci-resolve-mcp setup

The setup process installs a managed copy, creates a Python virtual environment, detects Resolve paths, and can configure supported clients including Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, Zed, Continue, Cline, Roo Code, Codex CLI, and JetBrains IDEs. Source installation is also available by cloning the repository and running python install.py.

Before connecting, enable local external scripting in Resolve Studio under Preferences > General > External scripting using > Local. Bridge users install it with python scripts/install_resolve_bridge.py, restart Resolve, open a project, and launch the bridge from Workspace > Scripts.

The bridge configuration defaults to ~/.config/davinci-resolve-mcp/bridge.json. Set DAVINCI_RESOLVE_BRIDGE_CONFIG in both the installer and MCP client environment to use another location. On macOS, the in-app bridge may require PYTHON3HOME to point to a Python prefix visible to Resolve.

Tools and capabilities

  • Operate Resolve through compound or granular MCP tool layouts.
  • Edit timelines and manage media-pool contents.
  • Configure renders and manage project lifecycle tasks.
  • Work with color grading, Fusion, Fairlight, and review markers.
  • Inspect Resolve state and analyze media through the local control panel.

Resolve 18.5 or newer and Python 3.10 or newer are indicated as supported prerequisites. The server and installer perform best-effort checks for newer MCP releases without blocking startup.

Limitations and notes

The free-edition bridge is an in-app workaround subject to changes in Resolve scripting behavior. Free Resolve 21.1 no longer lists Python scripts in the Workspace > Scripts menu, so the bridge path should be treated as a 21.0.x option. On macOS, Resolve only checks PYTHON3HOME and /usr/local/bin/python3 for Python 3; shell-only environment changes may not reach an application launched from the Dock.

The control panel is local-only and requires its per-launch access-token URL. The bridge holds its listener port while serving; older Windows builds could leave a stale fuscript.exe process holding the port.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Davinci Resolve MCP

samuelgursky/davinci-resolve-mcp is an MCP server that connects AI assistants to DaVinci Resolve through its scripting API. Its main tools cover timeline editing, media-pool organization, rendering, grading, Fusion, Fairlight, markers, project control, and media analysis, with grouped and granular operating modes.

Run `npx davinci-resolve-mcp setup` to install it and configure supported MCP clients. Alternatively, clone the repository and run `python install.py`. Resolve Studio must have local external scripting enabled before the client connects.

Yes, Cursor is supported by the installer configuration flow. Run `npx davinci-resolve-mcp setup`, then allow the installer to configure Cursor. The server connects to a locally running DaVinci Resolve instance through external scripting or its local bridge.

Yes, free Resolve can use the in-application bridge on the documented 21.0.x path. Install it with `python scripts/install_resolve_bridge.py`, restart Resolve, open a project, and launch the bridge from Workspace > Scripts. Resolve 21.1 moved Python scripting to Studio.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewDavinci Resolve MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/samuelgursky-davinci-resolve-mcp?style=directory)](https://allmcps.com/mcp/samuelgursky-davinci-resolve-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/samuelgursky-davinci-resolve-mcp"><img src="https://allmcps.com/api/badge/samuelgursky-davinci-resolve-mcp?style=directory" alt="Davinci Resolve MCP on AllMCPs" /></a>