DaVinci Resolve MCP Server for VS Code: Setup & Config

What you can do with DaVinci Resolve in VS Code

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

• Organize media bins and prepare editing timelines.
• Inspect timeline gaps, missing media, and review markers.

Before you start: DaVinci Resolve in VS 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 VS Code configuration

1. Choose VS Code configuration scope

   For DaVinci Resolve MCP Server, open Workspace: .vscode/mcp.json. Merge into servers; preserve existing inputs.

2. Add DaVinci Resolve MCP Server to VS Code

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

3. Check DaVinci Resolve MCP Server in VS Code

   DaVinci Resolve MCP Server: Start in VS Code’s MCP controls; inspect output and trust prompts.

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

DaVinci Resolve tools available to VS Code

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

media_analysis

Look for media_analysis among VS Code's agent-mode tools after starting DaVinci Resolve through the MCP controls.

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

drp

Look for drp among VS Code's agent-mode tools after starting DaVinci Resolve through the MCP controls.

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

drt

Look for drt among VS Code's agent-mode tools after starting DaVinci Resolve through the MCP controls.

Work with Resolve timeline files through the offline advanced server.

drx

Look for drx among VS Code's agent-mode tools after starting DaVinci Resolve through the MCP controls.

capabilities

Look for capabilities among VS Code's agent-mode tools after starting DaVinci Resolve through the MCP controls.

project_read

Look for project_read among VS Code's agent-mode tools after starting DaVinci Resolve through the MCP controls.

Inspect project content using the optional offline server.

project_db

Look for project_db among VS Code's agent-mode tools after starting DaVinci Resolve through the MCP controls.

Apply database-level project operations through the advanced server.

pipeline

Look for pipeline among VS Code's agent-mode tools after starting DaVinci Resolve through the MCP controls.

deliverable

Look for deliverable among VS Code's agent-mode tools after starting DaVinci Resolve through the MCP controls.

provenance

Look for provenance among VS Code's agent-mode tools after starting DaVinci Resolve through the MCP controls.

DaVinci Resolve: full stored tool descriptions

Troubleshooting DaVinci Resolve in VS Code

• Make npx davinci-resolve-mcp (Node.js/npm) available in the workspace, container, or remote environment hosting DaVinci Resolve MCP Server. Start through VS Code's MCP controls; inspect output and trust prompts.
• DaVinci Resolve MCP Server uses stdio here: VS 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 VS Code troubleshooting lives in the /clients/vscode guide.

Frequently asked questions