davinci-resolve-mcp
MCP server integration for DaVinci Resolve Studio
Runssource: GitHubPythonMITcommit 6337d8cf7068
Python, MIT licensed. The project labels itself: blackmagic, blackmagic design, blackmagicdesign, davinci resolve, davinciresolve, mcp and mcp server.
davinci-resolve-mcp runs. An Argusic agent installed it in 35 minutes and hit 2 errors on a clean machine with no GPU, and the whole session was recorded.
Python compound MCP server starts and answers MCP initialize/tools/list returning 37 tools. Python test suite: 3554 offline tests pass. Node.js resolve-advanced test suite: 913/961 pass (remaining failures from Node.js version gap v18 vs >=20.9). npm install and venv install complete. DaVinci Resolve not available in container so live Resolve tests are skipped.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 80 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- DaVinci Resolve not installed - scripting API paths not found; install.py warns but proceeds5 minutes
- Node.js v18.19.1 < 20.9 required by resolve-advanced; 17/961 tests fail5 minutes
- Install time
- 35 minutes
- Cold machine to finish
- 22 minutes
- Errors hit and fixed
- 2 hit, 0 fixed with no human help
- How the result was proved
- venv/bin/python -m pytest tests/: 3554 passed, 42 skipped; MCP stdio handshake returned 37 tools; resolve-advanced npm run test: 913/961 pass
- Model tokens used
- 112,433
- Exact commit tested
- 6337d8cf7068
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
2. Node.js v18.19.1 < 20.9 required by resolve-advanced — not fixable without system Node upgrade tokens used 112,433 Here's my assessment — I have all the evidence I need: **Install**: Python dependencies and npm packages install successfully. The install.py runs but can… **Launch**: Both Python compound server and Node.js advanced server start. The Python MCP server an… **Tests**: - Python: 3554 passed, 42 skipped (offline-capable tests) - Node.js resolve-advanced: 913 passed, 17 failed (due to Node.js v18 < required 20.9, plus optiona… **Errors encountered**: 1. DaVinci Resolve scripting API not found in the container — expected, not fixable without the act… 2. Node.js v18.19.1 < 20.9 required by resolve-advanced — not fixable without system Node upgrade
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 35 minutes.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Hit 2 errors during setup, 2 of which were not solved.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
blackmagicblackmagic-designblackmagicdesigndavinci-resolvedavinciresolvemcpmcp-server
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/davinci-resolve-mcp)Questions
- Does davinci-resolve-mcp run?
- Yes. davinci-resolve-mcp runs. Argusic installed and launched it on a clean machine in 35 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test davinci-resolve-mcp?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 6337d8cf7068. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test davinci-resolve-mcp?
- The run that produced this verdict cost $0.08: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does davinci-resolve-mcp take to install?
- 35 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does davinci-resolve-mcp need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing davinci-resolve-mcp?
- 2 things broke in the recorded run. Each one, and the time it cost, is listed on this page.
- Where is the evidence for davinci-resolve-mcp?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.