DaVinci Resolve 21.1 added a native MCP server. If you are deciding whether that unlocks anything for you, the version of Resolve you own settles most of it before any of the interesting questions come up.
What Blackmagic actually shipped
Resolve Studio 21.1 exposes an MCP server natively. Blackmagic names Claude, Claude Code and ChatGPT Codex as supported assistants, and the company's own examples are creating highlight edits from long-form video, removing unwanted clips, and rendering deliverables.
The architecture is worth noticing, because it is the opposite of the assistant panels being added to other editing suites. Those live inside the application and see what the vendor lets them see. Resolve is opening a door outward: whatever assistant you already run on your desktop can reach in. What it can reach is defined by the scripting API underneath, which is why the twenty new API calls in 21.1 matter more than they look — among them multicam create and flatten, timeline auto-align, transitions, audio normalisation, render presets, and media pool clip transcriptions with speaker and timing data.
Read that list with an assistant in mind and the shape is clear: transcription plus multicam plus auto-align plus render presets is most of what “build a rough cut of the interview and render a review copy” needs.
The gate, stated precisely
Three separate things get confused here, so it is worth separating them.
External scripting has always been Studio-only. This did not change in 21.1. On the free edition a foreign process asking for the Resolve object is refused regardless of what the External Scripting preference is set to. Any MCP server that runs as its own process — official or third-party — sits on that side of the gate.
21.1 moved Python scripting itself to Studio. Blackmagic's release notes are unusually direct about why: the Python API was being used to hack Studio features into the free version, and Studio license sales fund the engineering. Python 2 support is gone entirely at the same time.
The free-edition workaround is now uncertain rather than confirmed dead. The route that used to work was a script running inside Resolve, launched from Workspace ▸ Scripts, re-exporting the live object over a local listener — measured working on free 21.0.3.7. On free 21.1 the Scripts menu has been reported as no longer listing .py files at all. The maintainers of the most-used third-party server say plainly that whether the console still runs Python there is unconfirmed, and advise treating the bridge as a 21.0.x path until somebody measures it. That is the honest state of it today.
Official server or third-party
Both exist and they are not the same thing. The official server is built in to Studio 21.1 and needs no install. Third-party servers predate it, cover the scripting API broadly, and ship installers that configure a long list of clients — Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, Zed, Continue, Cline, Roo Code, OpenCode, Codex CLI and JetBrains IDEs among them.
They share the same prerequisite. A third-party server does not get you past the Studio gate, because it is an external process too.
What this is not
- Not an editor. The MCP server is a control surface for Resolve. The work still happens in Resolve, with Resolve's own limits.
- Not a way to skip the license. If the gate is the problem, an assistant is not the answer to it.
- Not a substitute for reviewing the result. Blackmagic's own framing is conversational control over project operations, not judgement about which take is better.
Connecting Claude Code, Codex or another desktop agent
On Studio 21.1 the official route comes first. Resolve connects the assistants Blackmagic names — Claude, Claude Code and ChatGPT Codex — from File ▸ Setup AI Assistants, with no third-party server in between. If the assistant you already use is on that list, that is the whole setup, and nothing below is required.
An MCP server is consumed by an MCP client, and the connection is ordinary: a local server is launched over stdio with a command, arguments and environment; a remote one is reached over streamable HTTP with a URL and headers.
Orkas is an MCP client and accepts custom servers through that same form — name, transport, then command and arguments for stdio, or URL and headers for HTTP, with anything secret stored encrypted rather than in the clear. The same desktop also runs Claude Code, Codex, OpenCode, OpenClaw and Hermes as local CLI sessions, which is relevant here only because those are the assistants this ecosystem is already written for.
To be exact about our own testing: we have verified both ends separately — that Resolve Studio 21.1 exposes an official MCP server, and that Orkas accepts arbitrary MCP servers as custom connectors. We have not run the pair end to end, and this page does not claim a validated integration.
If you are on the free edition
No MCP route above reaches the free edition of 21.1: the official server is Studio-only, and so is external scripting access. What is left is narrower, and all of it is manual or file-based:
- Stay on 21.0.x if the in-app bridge matters to you. That is where the Workspace ▸ Scripts route was measured working; 21.1 stopped listing .py files in that menu.
- Use the Console by hand. Digital Production reports that the scripting API remains available from the Console in the free edition — one pasted snippet at a time, not an assistant connection. Whether that includes Python is the part nobody has confirmed yet.
- Import a timeline you built elsewhere. File ▸ Import ▸ Timeline accepts an FCPXML or OTIO file, which is how free-edition helper projects hand over a rough cut.
What still works without touching Resolve's API at all is a pipeline that operates on the media directly — evidence from the footage, an edit decision list you approve, then deterministic assembly. That is the approach described in how to automate video editing, and it is what Orkas's VideoStudio does on its own: it renders the finished video itself rather than working inside Resolve.