The resolve-mcp server provides programmatic control over DaVinci Resolve Studio, enabling AI-driven editorial and media management tasks directly inside Resolve. Key capabilities:
Session & project management: Check connection state, Resolve version, current project/timeline (get_status); list available projects (list_projects); open a specific project by exact name (open_project); create .drp backup snapshots (snapshot_project).
Media pool operations: Import files and image sequences (import_media); list clips with offline state (list_media); inspect clip properties, metadata, markers, and time bounds (inspect_clip); batch update clip metadata (set_clip_metadata); organize media by creating nested bins and moving clips (organize_media); relink offline clips to new paths (relink_media).
Escape hatch: Run arbitrary DaVinci Resolve scripting‑API Python code (run_python) with resolve, project_manager, project, and timeline pre‑bound in the namespace, returning the last expression's value and captured stdout.
All tools return structured JSON and echo context (project/timeline) for confirmation.
Enables interaction with DaVinci Resolve Studio, providing tools to manage projects and timelines, create snapshots, and run Python scripting API commands for editorial automation.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@resolve-mcp open project 'Docu' and snapshot before render"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
An MCP server that gives Claude Code hands inside DaVinci Resolve Studio — so the musical and editorial reasoning happens in Claude and the mechanical work happens in Resolve.
Build contract: issue #22.
P1 in progress. Shipped so far: the server skeleton, the session/project tools, the media
pool tools, and the run_python escape hatch.
Tool | What it does |
| Connection state, Resolve version, current project + timeline, fps |
| Project names in the current database folder |
| Loads a project by name; the result echoes the new context |
| Writes an opaque |
| Imports files and image sequences into a bin, still-duration workaround applied |
| Summarises media pool clips, with offline state; spills big listings to disk |
| One clip in full: properties, metadata, audio mapping, markers, dual-time bounds |
| Batch metadata writes, each field routed by what the clip reports |
| Batch bin operations: create nested bins, move clips |
| Points offline clips at media that moved (folder relink or file replace) |
| Escape hatch: runs scripting-API Python in the server process |
Bin paths are slash-separated from the media pool root (Concert/Angles) and
case-sensitive. A clip counts as offline when it has a file path that is not on
disk — Resolve's scripting API exposes no offline flag.
Related MCP server: DaVinci MCP Professional
Windows 11, DaVinci Resolve Studio 21.0.3 (external scripting must be enabled: Preferences > System > General > External scripting using = Local)
CPython 3.12 x64 installed from python.org — not a uv-managed interpreter. See ADR 0001: the Resolve scripting library crashes the process outright on a standalone build, so the server refuses to attach on one. uv still manages the venv and the lockfile.
Resolve running, with a project open, before the first Resolve-touching tool call
uv venv --python "C:/Users/<you>/AppData/Local/Programs/Python/Python311/python.exe"
uv syncuv sync alone will pick a uv-managed interpreter, which runs the unit suite fine but
cannot attach to Resolve.
uv run resolve-mcpThe server speaks MCP over stdio and logs to stderr only. Register it with Claude Code:
claude mcp add resolve -- uv --directory C:/Users/Daniel/repos/resolve-mcp run resolve-mcpZero-config by default; every path has an environment override.
Variable | Default | Purpose |
|
| Scripting API root (holds |
|
| Scripting library |
|
| Cache root: snapshots, analysis artifacts, model weights |
|
| Log level for the stderr logger |
| unset | Bypass the interpreter check (see ADR 0001) |
uv run pytest # unit suite — runs with Resolve closed, against the fake seam
uv run pytest -m live # live smoke tier — needs real Resolve running, on a python.org interpreter
uv run mypy # type check
uv run ruff check . # lintTests exercise external behaviour only: they call the tool functions in-process (no stdio transport) against a fake Resolve API object substituted at the connection singleton.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Hosted MCP server connecting claude.ai, ChatGPT and other AI apps to your own computer
Augments MCP Server - A comprehensive framework documentation provider for Claude Code
MCP server for Google Veo AI video generation
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/danielbaldwin47/resolve-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server