Data as of

DaVinci Resolve MCP Server for Claude Code: Setup & Config

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

What you can do with DaVinci Resolve in Claude Code

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

  • Organize media bins and prepare editing timelines.
  • Analyze footage while preserving camera originals.

Before you start: DaVinci Resolve in Claude Code

  • 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 Code configuration

  1. Choose Claude Code configuration scope

    For DaVinci Resolve MCP Server, open Project scope: .mcp.json at the repository root. Project JSON: merge into mcpServers; user scope: use the CLI.

  2. Add DaVinci Resolve MCP Server to Claude Code

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

  3. Check DaVinci Resolve MCP Server in Claude Code

    DaVinci Resolve MCP Server: Inspect claude mcp list and /mcp status.

Config file · Project scope: .mcp.json at the repository root

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

CLI (POSIX shell)
claude mcp add-json --scope project 'davinci-resolve-mcp' '{"type":"stdio","command":"npx","args":["davinci-resolve-mcp","setup"],"env":{}}'

DaVinci Resolve tools available to Claude Code

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

media_analysis

For DaVinci Resolve's media_analysis, review the permission request and arguments in Claude Code before approval.

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

drp

For DaVinci Resolve's drp, review the permission request and arguments in Claude Code before approval.

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

drt

For DaVinci Resolve's drt, review the permission request and arguments in Claude Code before approval.

Work with Resolve timeline files through the offline advanced server.

drx

For DaVinci Resolve's drx, review the permission request and arguments in Claude Code before approval.

capabilities

For DaVinci Resolve's capabilities, review the permission request and arguments in Claude Code before approval.

project_read

For DaVinci Resolve's project_read, review the permission request and arguments in Claude Code before approval.

project_db

For DaVinci Resolve's project_db, review the permission request and arguments in Claude Code before approval.

pipeline

For DaVinci Resolve's pipeline, review the permission request and arguments in Claude Code before approval.

Compile project specifications into a SQLite-backed pipeline with validation gates and provenance.

deliverable

For DaVinci Resolve's deliverable, review the permission request and arguments in Claude Code before approval.

Check deliverables for quality and compliance through the advanced server.

provenance

For DaVinci Resolve's provenance, review the permission request and arguments in Claude Code before approval.

DaVinci Resolve: full stored tool descriptions

Troubleshooting DaVinci Resolve in Claude Code

  • If DaVinci Resolve MCP Server fails to start, check npx davinci-resolve-mcp (Node.js/npm), the working directory, and Claude Code's selected scope; inspect claude mcp list and /mcp.
  • DaVinci Resolve MCP Server uses stdio here: Claude Code 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 Code troubleshooting lives in the /clients/claude-code guide.

DaVinci Resolve MCP Server — details. Claude Code guide

Frequently asked questions

Register DaVinci Resolve MCP Server with the displayed claude mcp add-json --scope project command, or merge the JSON into .mcp.json at the repository root.

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

DaVinci Resolve MCP Server's Claude Code 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 Code'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 documented default treats source media as immutable and places analysis artifacts outside the original files. Derivatives require an explicit request.