Claude Can Now Drive DaVinci Resolve. Python Got a $295 Gate.

TL;DR

On September 8, Blackmagic Design shipped DaVinci Resolve 21.1 with a native Model Context Protocol server built into the application. Point Claude, Claude Code or ChatGPT Codex at it and an agent can organise media, cut a timeline, grade it and start a render, without a plugin or a reverse-engineered bridge. The same release moved Python and external scripting behind the $295 Studio licence, and Blackmagic said the quiet part out loud about why.

What actually shipped

Resolve is the first application most editors would call industry standard to ship an MCP server in the box. Not a community plugin. Not an experimental branch. A menu item.

You enable it under File > Setup AI Assistants, which is roughly three clicks from a cold start. Scott Simmons at ProVideo Coalition called it "the easiest AI integration I've had with any of my NLEs," which is faint praise given the competition, but it is still the correct verdict.

Once connected, the assistant is not talking about your timeline. It is holding the scissors. Digital Production reports Blackmagic's own demonstration prompt: take a long clip from the Media Pool, turn it into a three minute highlight edit, drop every cut shorter than one second, render it as H.265 for review. Independent testing at Creative Video Tips had Claude opening projects, running automatic subtitles, applying AI smart reframing for vertical delivery, pushing a black and white grade and exporting the result.

The mechanism is unglamorous and that is the point. MCP is a standard shape for a tool description, and Resolve has had a published scripting API for years. The server is a translation layer that hands the model a menu of verified calls instead of asking it to guess. Think of it as the difference between a tourist miming at a waiter and a tourist handed a menu with photographs: same restaurant, wildly different odds of getting the thing you actually wanted.

The other half of the release

Read the release notes past the headline and the trade goes the other way too. Python and advanced scripting now require Resolve Studio. Free Resolve keeps the scripting console inside the application, but external scripting access, Workflow Integrations and the native UIManager are all Studio only, and so is the MCP server.

Blackmagic did not dress this up. Per ProVideo Coalition's account of the company's explanation:

"We have moved the ability to script in Python to the Studio version. The Python API was being used to hack studio features into the free version."

That is an honest answer to a real problem. The free build ships without the Neural Engine features, and the published API was a convenient seam for prying them open. Closing it costs Blackmagic almost nothing in goodwill because the fix is a one time $295 licence, not a subscription. The company has been loud about that distinction for years, framing Studio sales as what funds the engineering team, in contrast to competitors that "lock people's work up unless you pay monthly."

Still, if you had a free Resolve node in an automation pipeline, that node is now a licence purchase. Budget accordingly before you update the render farm.

The community got there first, as usual

None of this is a surprise to anyone who has been watching GitHub. samuelgursky/davinci-resolve-mcp has been wiring assistants into Resolve through the same official API for well over a year, and now sits at roughly 2,500 stars, 299 forks and 795 commits. A second project, barckley75/resolve-claude-mcp, does a narrower version of the same job for Claude specifically.

The community README is also more candid about limits than any vendor page will ever be. It states plainly that the project does not judge cut quality, does not choose takes, does not replace an editor, and by design never modifies source media, writing only to sidecars or the project database.

Notably, that project already required Studio Edition for direct external scripting. The free build was only reachable through an in-app bridge. So the licensing wall Blackmagic just made explicit was, for anyone doing serious external automation, already the practical reality.

What the native version changes

• Nothing to install. No Python environment, no separate server process, no version drift between the bridge and the host application after every point release.
• Blackmagic owns the surface. When the API changes, the shipped server changes with it. That is the entire maintenance burden of a third party bridge, moved off your plate.
• It is a supported path. A studio pipeline lead can now approve agent automation without approving an unsigned binary from a stranger's repository.

Where to be careful

An agent with API access to your project is an agent with API access to your project. The community project's self-imposed rule about never touching source media is a design choice, not a property of MCP, and the native server is wired to a scripting API that can absolutely rearrange a timeline you spent a week on. Version your projects, and do not point this at a client master on a Friday afternoon.

Two more practical notes. RedShark reports 20 new scripting APIs with built-in console support in this release, so the surface an agent can reach is wider than it was in 21.0. And ProVideo Coalition's Simmons flagged the unglamorous consequence of natural language driving a real application: "You may need to update your AI subscription because ... tokens." A model reading project state, reasoning about clips and issuing calls burns context per action, and a highlight reel is a lot of actions.

The rest of 21.1 is a substantial release on its own terms: over 100 new tools and controls, more than 25 new Krokodove shape and 3D tools in Fusion, expanded Photo page camera support for Fujifilm, Leica and Sony Alpha, better multicam control and an updated trim editor. It landed days before IBC opens at RAI Amsterdam on September 11, which is not an accident.

Key Takeaways

• Resolve Studio 21.1 ships a native MCP server, enabled at File > Setup AI Assistants, connecting Claude, Claude Code and ChatGPT Codex directly to the editing, grading and render APIs.
• Python and external scripting are now Studio only. Blackmagic's stated reason: the free Python API "was being used to hack studio features into the free version."
• Free Resolve keeps console scripting but loses external scripting access, Workflow Integrations, the native UIManager and MCP. Automation nodes in a pipeline now need a $295 licence each.
• The community shipped this first. samuelgursky/davinci-resolve-mcp has about 2,500 stars and already required Studio for external scripting, so the wall is newly explicit rather than newly built.
• Treat it as a power tool, not an assistant. The agent holds real API calls against real timelines. Version your projects before you let it cut.
• Budget tokens, not just licences. Every clip inspected and every call issued is context, and a highlight reel is hundreds of them.

Sources: CG Channel: Blackmagic Design releases Resolve 21.1, Digital Production: Resolve 21.1 Adds MCP and Presets for Automation, ProVideo Coalition: DaVinci Resolve 21.1 is a huge update, RedShark News: DaVinci Resolve 21.1 new features and release, Newsshooter: Blackmagic Design DaVinci Resolve 21.1, Creative Video Tips: What's new in DaVinci Resolve 21.1, AlternativeTo: DaVinci Resolve 21.1 changes scripting and editing tools, Blackmagic Design: DaVinci Resolve product page, GitHub: samuelgursky/davinci-resolve-mcp, Model Context Protocol