DaVinci Resolve MCP
local-only server
The server can only run on the client’s local machine because it depends on local resources.
Integrations
Enables AI-assisted video editing in DaVinci Resolve, allowing access to timeline, media, and project information, manipulation of edits, automation of workflows, and color grading capabilities.
DaVinci Resolve MCP Server
A Model Context Protocol (MCP) server that connects AI coding assistants (Cursor, Claude Desktop) to DaVinci Resolve, enabling them to query and control DaVinci Resolve through natural language.
Features
For a comprehensive list of implemented and planned features, see docs/FEATURES.md.
Requirements
- macOS or Windows with DaVinci Resolve installed
- Python 3.6+
- DaVinci Resolve running in the background
- (Optional) Node.js/npm for some features
Installation Guide
For detailed installation instructions, please see INSTALL.md. This guide covers:
- Prerequisites and system requirements
- Step-by-step installation process
- Configuration details
- Common troubleshooting steps
Platform Support
Platform | Status | One-Step Install | Quick Start |
---|---|---|---|
macOS | ✅ Stable | ./install.sh | ./run-now.sh |
Windows | ✅ Stable | install.bat | run-now.bat |
Linux | ❌ Not supported | N/A | N/A |
Quick Start Guide
New One-Step Installation (Recommended)
The easiest way to get started is with our new unified installation script. This script does everything automatically:
- Clone the repository:Copy
- Make sure DaVinci Resolve Studio is installed and running
- Run the installation script:
macOS/Linux:Windows:CopyCopy
This will:
- Automatically detect the correct paths on your system
- Create a Python virtual environment
- Install the MCP SDK from the official repository
- Set up environment variables
- Configure Cursor/Claude integration
- Verify the installation is correct
- Optionally start the MCP server
Alternative Quick Start
You can also use the original quick start scripts:
Windows Users:
macOS Users:
Configuration
For configuration of DaVinci Resolve MCP with different AI assistant clients like Cursor or Claude, see the config-templates directory.
Troubleshooting
For detailed troubleshooting guidance, refer to the INSTALL.md file which contains solutions to common issues.
Common Issues
Path Resolution
- The installation scripts now use more robust path resolution, fixing issues with
run-now.sh
looking for files in the wrong locations - Always let the scripts determine the correct paths based on their location
DaVinci Resolve Detection
- We've improved the process detection to reliably find DaVinci Resolve regardless of how it appears in the process list
- Make sure DaVinci Resolve is running before starting the MCP server
Environment Variables
- Make sure all required environment variables are set correctly
- Review the log file at
scripts/cursor_resolve_server.log
for troubleshooting
Windows
- Make sure to use forward slashes (/) in configuration files
- Python must be installed and paths configured in configs
- DaVinci Resolve must be running before starting the server
macOS
- Make sure scripts have execute permissions
- Check Console.app for any Python-related errors
- Verify environment variables are set correctly
- DaVinci Resolve must be running before starting the server
Support
For issues and feature requests, please use the GitHub issue tracker.
Launch Options
After installation, you have several ways to start the server:
Client-Specific Launch Scripts
The repository includes dedicated scripts for launching with specific clients:
These specialized scripts:
- Set up the proper environment for each client
- Verify DaVinci Resolve is running
- Configure client-specific settings
- Start the MCP server with appropriate parameters
Pre-Launch Check
Before connecting AI assistants, verify your environment is properly configured:
These scripts will:
- Verify DaVinci Resolve is running (and offer to start it)
- Check environment variables are properly set
- Ensure the Python environment is configured correctly
- Validate Cursor/Claude configuration
- Optionally launch Cursor
Universal Launcher
For advanced users, our unified launcher provides full control over both Cursor and Claude Desktop servers:
Additional options:
- Force mode (skip Resolve running check):
--force
- Project selection:
--project "Project Name"
Full Installation
For a complete manual installation:
- Clone this repository:Copy
- Create a Python virtual environment:Copy
- Set up DaVinci Resolve scripting environment variables:For macOS:For Windows:CopyAlternatively, run the pre-launch check script which will set these for you:CopyCopy
- Configure Cursor to use the server by creating a configuration file:For macOS (
~/.cursor/mcp.json
):For Windows (Copy%APPDATA%\Cursor\mcp.json
):Copy - Start the server using one of the client-specific scripts:Copy
Usage with AI Assistants
Using with Cursor
- Start the Cursor server using the dedicated script:Or use the universal launcher:CopyCopy
- Start Cursor and open a project.
- In Cursor's AI chat, you can now interact with DaVinci Resolve. Try commands like:
- "What version of DaVinci Resolve is running?"
- "List all projects in DaVinci Resolve"
- "Create a new timeline called 'My Sequence'"
- "Add a marker at the current position"
Using with Claude Desktop
- Create a
claude_desktop_config.json
file in your Claude Desktop configuration directory using the template in theconfig-templates
directory. - Run the Claude Desktop server using the dedicated script:Or use the universal launcher:CopyCopy
- In Claude Desktop, you can now interact with DaVinci Resolve using the same commands as with Cursor.
Available Features
General
- Get DaVinci Resolve version
- Get/switch current page (Edit, Color, Fusion, etc.)
Project Management
- List available projects
- Get current project name
- Open project by name
- Create new project
- Save current project
Timeline Operations
- List all timelines
- Get current timeline info
- Create new timeline
- Switch to timeline by name
- Add marker to timeline
Media Pool Operations
- List media pool clips
- Import media file
- Create media bin
- Add clip to timeline
Windows Support Notes
Windows support is stable in v1.3.3 and should not require additional troubleshooting:
- Ensure DaVinci Resolve is installed in the default location
- Environment variables are properly set as described above
- Windows paths may require adjustment based on your installation
- For issues, please check the logs in the
logs/
directory
Troubleshooting
DaVinci Resolve Connection
Make sure DaVinci Resolve is running before starting the server. If the server can't connect to Resolve, check that:
- Your environment variables are set correctly
- You have the correct paths for your DaVinci Resolve installation
- You have restarted your terminal after setting environment variables
Project Structure
License
MIT
Acknowledgments
- Blackmagic Design for DaVinci Resolve and its API
- The MCP protocol team for enabling AI assistant integration
Author
Samuel Gursky (samgursky@gmail.com)
- GitHub: github.com/samuelgursky
Future Plans
- Windows and Linux support
- Additional DaVinci Resolve features
- Support for Claude Desktop
Development
If you'd like to contribute, please check the feature checklist in the repo and pick an unimplemented feature to work on. The code is structured with clear sections for different areas of functionality.
License
MIT
Acknowledgments
- Blackmagic Design for DaVinci Resolve and its API
- The MCP protocol team for enabling AI assistant integration
Project Structure
After cleanup, the project has the following structure:
resolve_mcp_server.py
- The main MCP server implementationrun-now.sh
- Quick start script that handles setup and runs the serversetup.sh
- Complete setup script for installationcheck-resolve-ready.sh
- Pre-launch check to verify DaVinci Resolve is readystart-server.sh
- Script to start the serverrun-server.sh
- Simplified script to run the server directly
Key Directories:
src/
- Source code and modulesassets/
- Project assets and resourceslogs/
- Log files directoryscripts/
- Helper scripts
When developing, it's recommended to use ./run-now.sh
which sets up the environment and launches the server in one step.
Changelog
See docs/CHANGELOG.md for a detailed history of changes.
This server cannot be installed
A server that enables LLM applications to interact directly with DaVinci Resolve video editing software, allowing AI-assisted capabilities like accessing timeline information and automating editing workflows.
- Features
- Requirements
- Installation Guide
- Platform Support
- Quick Start Guide
- Configuration
- Troubleshooting
- Support
- Launch Options
- Full Installation
- Usage with AI Assistants
- Available Features
- Windows Support Notes
- Troubleshooting
- Project Structure
- License
- Acknowledgments
- Author
- Future Plans
- Development
- License
- Acknowledgments
- Project Structure
- Changelog