DaVinci Resolve MCP Server for Cursor: Setup & Config

What you can do with DaVinci Resolve in Cursor

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

• Inspect timeline gaps, missing media, and review markers.
• Analyze footage while preserving camera originals.

Before you start: DaVinci Resolve in Cursor

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

1. Choose Cursor configuration scope

   For DaVinci Resolve MCP Server, open Project: .cursor/mcp.json User: ~/.cursor/mcp.json. Merge into mcpServers at project or user scope.

2. Add DaVinci Resolve MCP Server to Cursor

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

3. Check DaVinci Resolve MCP Server in Cursor

   DaVinci Resolve MCP Server: Enable in Cursor’s MCP settings; inspect tools.

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

DaVinci Resolve tools available to Cursor

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

media_analysis

Find media_analysis under DaVinci Resolve in Cursor's MCP settings; inspect its arguments when the agent requests a call.

drp

Find drp under DaVinci Resolve in Cursor's MCP settings; inspect its arguments when the agent requests a call.

drt

Find drt under DaVinci Resolve in Cursor's MCP settings; inspect its arguments when the agent requests a call.

drx

Find drx under DaVinci Resolve in Cursor's MCP settings; inspect its arguments when the agent requests a call.

capabilities

Find capabilities under DaVinci Resolve in Cursor's MCP settings; inspect its arguments when the agent requests a call.

project_read

Find project_read under DaVinci Resolve in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Inspect project content using the optional offline server.

project_db

Find project_db under DaVinci Resolve in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Apply database-level project operations through the advanced server.

pipeline

Find pipeline under DaVinci Resolve in Cursor's MCP settings; inspect its arguments when the agent requests a call.

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

deliverable

Find deliverable under DaVinci Resolve in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Check deliverables for quality and compliance through the advanced server.

provenance

Find provenance under DaVinci Resolve in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Produce audit and episode provenance reports through the advanced server.

DaVinci Resolve: full stored tool descriptions

Troubleshooting DaVinci Resolve in Cursor

• Cursor must find npx davinci-resolve-mcp (Node.js/npm) for DaVinci Resolve MCP Server. Enable the project/user entry in MCP settings and inspect its tools.
• DaVinci Resolve MCP Server uses stdio here: Cursor 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 Cursor troubleshooting lives in the /clients/cursor guide.

Frequently asked questions