DaVinci Resolve MCP (free edition) runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 31 Oct 2026.
Control DaVinci Resolve 21.1 (free edition included) from Claude via a Lua bridge. See README.
We read the source, 23 h ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
local fn, lerr = loadstring("return " .. payload, "=request")
out = subprocess.run(["pgrep", "-f", _RESOLVE_PROCESS], stdout=subprocess.PIPE,
path = os.path.join(scripts_dir, name)
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Control the free edition of DaVinci Resolve 21.1 from Claude through a Lua script inside Resolve.
Control DaVinci Resolve, including the free Lite edition. Manual setup only — see README.
Control DaVinci Resolve from any AI assistant. 215 MCP tools covering the full Resolve API.
Assistant editor for Premiere Pro and DaVinci Resolve: logs, transcribes, rough cuts, subtitles, QC
Remote-control Unity Editor from any AI IDE via file-based IPC. 62 tools, zero dependencies.
Control the Unity Editor from MCP hosts through a local Rust server and C# Unity bridge.
Bridges AI chat interfaces with Claude Code CLI via shared markdown control files.
Create, edit and publish scored quizzes and read results from any MCP client. Free plan included.
Answers built from our own checks of this server.