About DaVinci Resolve MCP Server
The DaVinci Resolve MCP Server is an MCP server that lets MCP clients control and inspect DaVinci Resolve and Fusion through tools and resources. It targets users who edit and composite video in Resolve and want to automate project work. It requires Python 3.10+ and is released under the MIT license.
Key features
- 01Project, timeline and media pool operations
- 02Fusion composite and node chain creation
- 03Resolve page navigation
- 04Python and Lua script execution
- 05Read-only resources for project and system status
Use cases
- 01Importing media and building timelines from clips
- 02Creating Fusion node chains from an MCP client
- 03Switching Resolve to a specific workspace page
MCP support
This project is an MCP server that exposes DaVinci Resolve tools and resources, including project, timeline, media pool and Fusion operations, to clients such as Claude Desktop.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEDaVinci Resolve MCP Server
Model Context Protocol (MCP) server that lets MCP clients control and inspect DaVinci Resolve (including Fusion) through tools and resources.
What it provides
- Project management (create, load, save)
- Timeline operations (create timeline, switch timeline, build from clips)
- Media pool operations (import media, create folders, inspect folders)
- Fusion helpers (add comp to clip, create nodes, create node chains)
- Resolve page navigation
- Advanced scripting (
execute_python,execute_lua)
Requirements
- Python 3.10+
- DaVinci Resolve with scripting API available
- An MCP-compatible client (for example Claude Desktop)
Install
git clone https://github.com/apvlv/davinci-resolve-mcp.git
cd davinci-resolve-mcp
uv sync --all-extras --dev
Run the server
uv run davinci-resolve-mcp
The server will try to connect to Resolve on startup. Make sure DaVinci Resolve is running.
MCP client setup
Configure your MCP client to launch the server command:
{
"mcpServers": {
"davinci-resolve": {
"command": "uv",
"args": ["run", "davinci-resolve-mcp"]
}
}
}
Resources
system://statusproject://currentproject://timelinestimeline://currentmediapool://foldersmediapool://currentstorage://volumes
Tools
Project
create_project(name)load_project(name)save_project()
Timeline
create_timeline(name)set_current_timeline(index)
Media
import_media(file_paths)create_folder(name)create_timeline_from_clips(name, clip_indices)
Fusion
add_fusion_comp_to_clip(timeline_index, track_type, track_index, item_index)create_fusion_node(node_type, parameters)create_fusion_node_chain(node_chain)
Resolve UI
open_page(page_name)where page name is one of:media,edit,fusion,color,fairlight,deliver
Advanced
execute_python(code)execute_lua(script)
Development
make install # install deps and pre-commit hooks
make lint-check # ruff check
make format-check # ruff format check
make test # pytest with coverage
make check # lint + format + tests
Example usage ideas
- "Create a project named
My Documentary" - "List timelines in the current project"
- "Import these files into the media pool"
- "Open the Color page"
- "Create a Fusion node chain Blur -> ColorCorrector"
License
MIT (see LICENSE)
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.