DaVinci Resolve MCP server

The DaVinci Resolve MCP server enables AI coding assistants like Cursor and Claude Desktop to interact with DaVinci Resolve through natural language. This server creates a bridge allowing you to query and control DaVinci Resolve without leaving your AI assistant interface.

Installation

Quick Start (Recommended)

The easiest way to get started is with the one-step installation script:

1. Clone the repository:

   git clone https://github.com/samuelgursky/davinci-resolve-mcp.git
   cd davinci-resolve-mcp
   

2. Make sure DaVinci Resolve is installed and running

3. Run the installation script:

   macOS:

   ./install.sh
   

   Windows:

   install.bat
   

This automatic process will:

• Detect the correct paths on your system
• Create a Python virtual environment
• Install the MCP SDK
• Set up environment variables
• Configure AI assistant integration
• Verify the installation

Alternative Quick Start

You can also use the original quick start scripts:

Windows:

run-now.bat

macOS:

chmod +x run-now.sh
./run-now.sh

Manual Installation

For a complete manual installation:

1. Clone the repository:

   git clone https://github.com/samuelgursky/davinci-resolve-mcp.git
   cd davinci-resolve-mcp
   

2. Create a Python virtual environment:

   # Create virtual environment
   python -m venv venv
   
   # Activate it (macOS/Linux)
   source venv/bin/activate
   # Or on Windows
   venv\Scripts\activate
   
   # Install dependencies
   pip install -r requirements.txt
   

3. Set up DaVinci Resolve scripting environment variables:

   macOS:

   export RESOLVE_SCRIPT_API="/Library/Application Support/Blackmagic Design/DaVinci Resolve/Developer/Scripting"
   export RESOLVE_SCRIPT_LIB="/Applications/DaVinci Resolve/DaVinci Resolve.app/Contents/Libraries/Fusion/fusionscript.so"
   export PYTHONPATH="$PYTHONPATH:$RESOLVE_SCRIPT_API/Modules/"
   

   Windows:

   set RESOLVE_SCRIPT_API=C:\ProgramData\Blackmagic Design\DaVinci Resolve\Support\Developer\Scripting
   set RESOLVE_SCRIPT_LIB=C:\Program Files\Blackmagic Design\DaVinci Resolve\fusionscript.dll
   set PYTHONPATH=%PYTHONPATH%;%RESOLVE_SCRIPT_API%\Modules
   

4. Configure your AI assistant (Cursor or Claude Desktop) to use the server

Launch Options

After installation, you can start the server in several ways:

Client-Specific Launch Scripts

# For Cursor integration (macOS)
chmod +x scripts/mcp_resolve-cursor_start
./scripts/mcp_resolve-cursor_start

# For Claude Desktop integration (macOS)
chmod +x scripts/mcp_resolve-claude_start
./scripts/mcp_resolve-claude_start

Pre-Launch Check

Verify your environment is properly configured:

# On macOS
./scripts/check-resolve-ready.sh

# On Windows
./scripts/check-resolve-ready.bat

Universal Launcher

For advanced users, the unified launcher provides full control:

# Make executable (macOS only)
chmod +x scripts/mcp_resolve_launcher.sh

# Run in interactive mode
./scripts/mcp_resolve_launcher.sh

# Or use command line options
./scripts/mcp_resolve_launcher.sh --start-cursor    # Start Cursor server
./scripts/mcp_resolve_launcher.sh --start-claude    # Start Claude Desktop server
./scripts/mcp_resolve_launcher.sh --start-both      # Start both servers
./scripts/mcp_resolve_launcher.sh --stop-all        # Stop all running servers
./scripts/mcp_resolve_launcher.sh --status          # Show server status

Using with AI Assistants

Cursor Integration

1. Start the Cursor server:

   ./scripts/mcp_resolve-cursor_start
   

2. Start Cursor and open a project.

3. In Cursor's AI chat, interact with DaVinci Resolve using natural language:

   • "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"

Claude Desktop Integration

1. Start the Claude Desktop server:

   ./scripts/mcp_resolve-claude_start
   

2. In Claude Desktop, interact with DaVinci Resolve using the same natural language commands.

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

Troubleshooting

Common Issues

Connection Problems

• Make sure DaVinci Resolve is running before starting the MCP server
• Check the log file at scripts/cursor_resolve_server.log for errors

Windows-Specific Issues

• Use forward slashes (/) in configuration files
• Ensure Python paths are configured correctly

macOS-Specific Issues

• Make sure scripts have execute permissions
• Check Console.app for Python-related errors
• Verify environment variables are set correctly

How to add this MCP server to Cursor

There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json file so that it is available in all of your projects.

If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json file.

Adding an MCP server to Cursor globally

To add a global MCP server go to Cursor Settings > MCP and click "Add new global MCP server".

When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:

{
    "mcpServers": {
        "cursor-rules-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "cursor-rules-mcp"
            ]
        }
    }
}

Adding an MCP server to a project

To add an MCP server to a project you can create a new .cursor/mcp.json file or add it to the existing one. This will look exactly the same as the global MCP server example above.

How to use the MCP server

Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.

The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.

You can also explictly ask the agent to use the tool by mentioning the tool name and describing what the function does.