Data as of

DaVinci Resolve MCP Server for Claude Desktop: Setup

Claude Desktop: Control DaVinci Resolve Studio from an AI assistant through its scripting API.

What you can do with DaVinci Resolve in Claude Desktop

Bring guarded editing, grading, and source-safe analysis into a local Resolve Studio workflow.

  • Organize media bins and prepare editing timelines.
  • Validate render settings before queueing delivery jobs.

Before you start: DaVinci Resolve in Claude Desktop

  • DaVinci Resolve Studio 18.5+
  • Python 3.10+
  • npx for the documented npm setup path
  • An MCP-compatible client

This is the setup installer, not the final MCP process. Open Resolve Studio and enable local external scripting. The installer generates client-specific server entries.

DaVinci Resolve Claude Desktop configuration

  1. Choose Claude Desktop configuration scope

    For DaVinci Resolve MCP Server, open macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json. Merge under mcpServers via Settings → Developer → Edit Config when available.

  2. Add DaVinci Resolve MCP Server to Claude Desktop

    Use the davinci-resolve-mcp entry below in mcpServers. Keep DaVinci Resolve MCP Server's documented stdio connection fields and your other Claude Desktop entries.

  3. Check DaVinci Resolve MCP Server in Claude Desktop

    DaVinci Resolve MCP Server: Fully quit and reopen Claude Desktop; check developer diagnostics.

Config file · macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Windows: %APPDATA%\Claude\claude_desktop_config.json

JSON
{
  "mcpServers": {
    "davinci-resolve-mcp": {
      "command": "npx",
      "args": [
        "davinci-resolve-mcp",
        "setup"
      ],
      "env": {}
    }
  }
}

DaVinci Resolve tools available to Claude Desktop

DaVinci Resolve's stored tool list documents 10 tools; compare it with Claude Desktop's connected tool list, because the stored list is not a live check.

media_analysis

When Claude Desktop requests media_analysis from DaVinci Resolve, review the action before approving it.

Coordinate analysis and finalize host-provided visual observations through action parameters.

drp

When Claude Desktop requests drp from DaVinci Resolve, review the action before approving it.

Read or edit Resolve project archive files with the optional advanced server.

drt

When Claude Desktop requests drt from DaVinci Resolve, review the action before approving it.

Work with Resolve timeline files through the offline advanced server.

drx

When Claude Desktop requests drx from DaVinci Resolve, review the action before approving it.

Inspect and modify per-clip grading files with offline grading and QC actions.

capabilities

When Claude Desktop requests capabilities from DaVinci Resolve, review the action before approving it.

Report available advanced-server features and missing dependency guidance.

project_read

When Claude Desktop requests project_read from DaVinci Resolve, review the action before approving it.

project_db

When Claude Desktop requests project_db from DaVinci Resolve, review the action before approving it.

pipeline

When Claude Desktop requests pipeline from DaVinci Resolve, review the action before approving it.

deliverable

When Claude Desktop requests deliverable from DaVinci Resolve, review the action before approving it.

provenance

When Claude Desktop requests provenance from DaVinci Resolve, review the action before approving it.

DaVinci Resolve: full stored tool descriptions

Troubleshooting DaVinci Resolve in Claude Desktop

  • Fully quit and reopen Claude Desktop for DaVinci Resolve MCP Server. If npx davinci-resolve-mcp (Node.js/npm) is missing, check the desktop process's PATH, which may differ from your terminal.
  • DaVinci Resolve MCP Server uses stdio here: Claude Desktop must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
  • Known limitation: Live control requires Resolve Studio and local external scripting access.
  • Known limitation: Some advanced-server features require additional utilities or modules.
  • Known limitation: The default stdio service is not a built-in multi-user network service.
  • General Claude Desktop troubleshooting lives in the /clients/claude-desktop guide.

DaVinci Resolve MCP Server — details. Claude Desktop guide

Frequently asked questions

Claude Desktop loads DaVinci Resolve MCP Server from claude_desktop_config.json: ~/Library/Application Support/Claude/ on macOS, or %APPDATA%\Claude\ on Windows. Open it via Settings → Developer → Edit Config when available.

Claude Desktop's davinci-resolve-mcp example uses stdio.

DaVinci Resolve MCP Server's Claude Desktop configuration invokes npx davinci-resolve-mcp (Node.js/npm).

DaVinci Resolve MCP Server's stored list contains 10 tools, including media_analysis, drp, drt. Compare those names with Claude Desktop's connected tool list; the stored list is not a live check.

Yes. The live Python integration controls Resolve Studio through its scripting API and requires local external scripting access.

The compound mode presents 34 grouped tools, while the full mode exposes 341 granular tools according to the README.