Davinci MCP Server

NPM bootstrapper for the DaVinci Resolve MCP Server.

Local serverstdioPython

What is the Davinci MCP server?

Davinci MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. NPM bootstrapper for the DaVinci Resolve MCP Server.

What you get

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.

Configuration and credentials

You will need one environment variable: DAVINCI_RESOLVE_BRIDGE. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

  • DaVinci Resolve 18.5+ on macOS, Windows, or Linux. Studio supports external scripting directly. The free edition does not — Blackmagic gates external scripting to Studio — but it is still reachable through the in-app bridge, which runs inside Resolve from the ungated Workspace ▸ Scripts menu. - Python 3.10+ (3.10-3.12 is the lowest-risk range). Python

Setting it up

davinci-resolve-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the davinci mcp server does with a few real requests.

How to install the Davinci MCP server

{
  "mcpServers": {
    "davinci-resolve": { "command": "<python>", "args": ["<path>/src/server.py"] },
    "davinci-resolve-advanced": { "command": "node", "args": ["<path>/bin/davinci-resolve-advanced-mcp.mjs"] }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • DaVinci Resolve 18.5+ on macOS, Windows, or Linux. Studio supports external scripting directly. The free edition does not — Blackmagic gates external scripting to Studio — but it is still reachable through the in-app bridge, which runs inside Resolve from the ungated Workspace ▸ Scripts menu. - Python 3.10+ (3.10-3.12 is the lowest-risk range). Python
VariableDescriptionRequired
DAVINCI_RESOLVE_BRIDGEConfiguration value read at startup.Optional

Frequently asked questions

It connects Davinci to MCP-compatible AI assistants such as Claude and Cursor. Instead of copying data back and forth by hand, the assistant works with Davinci directly.