Server facts
DaVinci Resolve MCP Server
Project
- Author
- samuelgursky
- License
- MIT
- Category
- Design & Creative
Tech
- Runtime / language
- pythonPython
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 3,574
- Last commit
- Data as of
Tags
- Color Grading
- Davinci Resolve
- Media Analysis
- Video Editing
Overview
DaVinci Resolve MCP Server gives AI assistants a local connection to Resolve Studio through its official scripting interface. It covers project management, media organization, timeline work, review markers, color operations, Fusion compositions, audio inspection, and render preparation. The default compound interface groups related operations behind action parameters, while a granular mode exposes individual API methods. Editors can therefore choose between a smaller tool surface and more explicit access to the underlying application. A browser-based local control panel also lets users inspect application state and review persisted analysis.
The project places particular emphasis on protecting source footage. Analysis reads originals and writes reports elsewhere; publishing metadata changes the Resolve project database rather than camera files. Workflows include checking timeline gaps, preparing multicam assemblies, validating render settings, and transferring review annotations. A separate optional Node-based advanced server works on Resolve project and grading files without a running Resolve instance, with some features needing extra installed utilities. The primary server still requires Resolve Studio to be open with external scripting enabled locally. Its npm setup command installs a managed copy, creates a Python environment, detects application paths, and can configure several MCP clients. Default operation is a local stdio process rather than a shared network service, so deployment and application prerequisites remain part of the workflow.
Install & configure
Requirements
- DaVinci Resolve Studio 18.5+
- Python 3.10+
- npx for the documented npm setup path
- An MCP-compatible client
npx davinci-resolve-mcp setupThis is the setup installer, not the final MCP process. Open Resolve Studio and enable local external scripting. The installer generates client-specific server entries.
Examples are translated from the published configuration. Supply your own credentials and verify requirements in the upstream README. Remote connectors are shown only where a supported configuration format is known.
Config file · macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Use Settings → Developer → Edit Config when available. Do not assume a Linux configuration path; check the client documentation for your platform. Remote servers use the app’s connector flow when supported, not the local stdio file shown here. Merge this example with existing settings; do not overwrite unrelated servers.
{
"mcpServers": {
"davinci-resolve-mcp": {
"command": "npx",
"args": [
"davinci-resolve-mcp",
"setup"
],
"env": {}
}
}
}Config file · Project: .cursor/mcp.json
User: ~/.cursor/mcp.json
The project path is relative to the workspace root. The tilde denotes your user home directory. Use Cursor’s MCP settings to confirm which configuration and scope your installed version is reading. Merge this example with existing settings; do not overwrite unrelated servers.
{
"mcpServers": {
"davinci-resolve-mcp": {
"command": "npx",
"args": [
"davinci-resolve-mcp",
"setup"
],
"env": {}
}
}
}Config file · Workspace: .vscode/mcp.json
For user scope, use the “MCP: Open User Configuration” command if available. Do not guess a user configuration path across operating systems, profiles, containers, or remote workspaces; check the client documentation. Merge this example with existing settings; do not overwrite unrelated servers.
{
"servers": {
"davinci-resolve-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"davinci-resolve-mcp",
"setup"
],
"env": {}
}
}
}Config file · macOS/Linux: ~/.codeium/windsurf/mcp_config.json
Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json
Open the MCP configuration through Windsurf’s settings when possible to confirm the active file. Paths can differ in managed or future releases; check the client documentation if this location is not present. Merge this example with existing settings; do not overwrite unrelated servers.
{
"mcpServers": {
"davinci-resolve-mcp": {
"command": "npx",
"args": [
"davinci-resolve-mcp",
"setup"
],
"env": {}
}
}
}Config file · Project scope: .mcp.json at the repository root
The project file uses mcpServers. For user scope, use claude mcp add --scope user rather than assuming .mcp.json in your home directory is the user configuration. Check the client documentation for managed settings and storage details. Merge this example with existing settings; do not overwrite unrelated servers.
{
"mcpServers": {
"davinci-resolve-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"davinci-resolve-mcp",
"setup"
],
"env": {}
}
}
}Examples are translated from the published configuration. Supply your own credentials and verify requirements in the upstream README. Remote connectors are shown only where a supported configuration format is known.
Tools
Source: repository README. Tool descriptions are a documented snapshot, not a live capability check.
| Tool | What it does |
|---|---|
| media_analysis | Coordinate analysis and finalize host-provided visual observations through action parameters. |
| drp | Read or edit Resolve project archive files with the optional advanced server. |
| drt | Work with Resolve timeline files through the offline advanced server. |
| drx | Inspect and modify per-clip grading files with offline grading and QC actions. |
| capabilities | Report available advanced-server features and missing dependency guidance. |
| project_read | Inspect project content using the optional offline server. |
| project_db | Apply database-level project operations through the advanced server. |
| pipeline | Compile project specifications into a SQLite-backed pipeline with validation gates and provenance. |
| deliverable | Check deliverables for quality and compliance through the advanced server. |
| provenance | Produce audit and episode provenance reports through the advanced server. |
Names, permissions, and defaults can change. Check the current upstream documentation before granting access.
Use cases
- Organize media bins and prepare editing timelines.
- Validate render settings before queueing delivery jobs.
- Inspect timeline gaps, missing media, and review markers.
- Analyze footage while preserving camera originals.
Strengths
- Offers compound and granular interfaces for different assistant workflows.
- Documents source-safe analysis and guarded operations.
- Includes a local control panel and an optional offline advanced server.
Limitations
- Live control requires Resolve Studio and local external scripting access.
- Some advanced-server features require additional utilities or modules.
- The default stdio service is not a built-in multi-user network service.
Frequently asked questions
Independent listing, not an affiliation or security review. Grant the least access needed and verify the upstream instructions before running code.
