Can AI Control DaVinci Resolve? Scripting, MCP and Limits

In short

Official: Resolve 21.1 supports AI assistants and adds about 20 scripting APIs. The Python and Lua scripting API controls projects, media, timelines, rendering and parts of the Color page.
Possible in a grade: apply LUTs and CDL values, copy grades between clips, apply saved grades, label and color nodes, export frames, assign color groups.
Not in the API: creating nodes, setting individual wheels, curves, qualifiers or windows, and pressing Auto color or Shot Match.
The hard part is not control: deciding what the numbers should be needs a system that can see and judge the picture.

What Blackmagic announced in 21.1

Blackmagic's DaVinci Resolve 21.1 release (8 September 2026) states that Resolve now supports AI assistants and names Claude, Claude Code and ChatGPT Codex. The examples given are practical project tasks: analyzing projects, organizing media, adjusting settings and batch rendering. The same release lists 20 new scripting APIs with built-in console support. Blackmagic frames the purpose as removing repetitive tasks so that people can focus on creative decisions.

Blackmagic's Studio 21 feature list includes "AI Assistants" with the note that it requires an MCP-compatible AI assistant. MCP (Model Context Protocol) is a standard way for an AI assistant to call tools in another application.

Trade press has reported further details: that with 21.1 external Python scripting and Workflow Integrations require DaVinci Resolve Studio, while scripts in the built-in console keep working in the free version. Treat that as reported rather than official. Blackmagic's own scripting README does describe the external-scripting preference as a DaVinci Resolve Studio setting.

The scripting API, from the documentation

An AI assistant does not reach into Resolve by magic. It uses the same scripting interface that pipeline developers have used for years. The README installed with Resolve (Developer/Scripting) describes:

Languages: Lua and Python 3, plus Workflow Integrations built on Electron and JavaScript.
Where scripts run: inside Resolve (the Workspace › Console window and the Scripts menu), locally from the Terminal on the same machine, or from the local network if that is configured.
External access: a preference in Resolve Studio decides whether external scripts may connect at all: None, Local or Network.
Headless use: Resolve can start without its interface (-nogui) and the scripting APIs keep working.

The API reference that ships with 21.1.2 lists objects for the project manager, project, media pool, timeline, timeline items, galleries, color groups and node graphs.

What a script can do on the Color page

Task	In the 21.1.2 API?	Notes
Apply a LUT to a node	Yes	On an existing node, by node number.
Set CDL values (slope, offset, power, saturation)	Yes	Per node. This is the main way to write a primary correction by script.
Copy a grade to other clips	Yes	Copies one clip's grade to a list of target clips.
Apply a saved grade (DRX still)	Yes	Replaces the clip's node graph with the saved one.
Enable or disable, label and color nodes	Yes	Labels and colors were added in 21.1.2.
Export a frame or a LUT of the grade	Yes	Frames can be exported for analysis outside Resolve.
Assign clips to color groups; reset grades	Yes
Create a new node	No	No node-creation function is listed. Scripts work with the nodes that exist, or apply a saved grade that has the nodes.
Set lift, gamma, gain, curves, qualifiers or windows directly	No	Only through CDL values, LUTs or a saved grade.
Press Auto color, Shot Match or Color Match	No	Not listed in the API reference.

This table is based on the API reference installed with Resolve 21.1.2. The API changes with almost every release, so check the CHANGELOG in your own Developer/Scripting folder before building on it.

Control is not the hard part. Judgment is.

Suppose an assistant can set any number in Resolve. To balance a shot it still needs to know what the number should be. That requires:

Seeing the picture as the colorist sees it, through the project's color management and output transform, not the raw camera file.
Measuring the right thing: skin, black level, the key light, the parts of the frame a viewer compares at a cut.
Knowing the intent: which differences between shots are mistakes and which are the story.
Checking the result in the picture after writing it, because a correction that is right in one color space can land differently in another.

A language model that changes settings on request is useful for project work: "make a timeline of all selects from day 3," "render these with the review preset." Asking the same assistant to "match these shots" without a vision and measurement step is asking it to guess.

Official, reported and experimental

Official and documented: the scripting API (README, API reference, changelog), the console, the Scripts menu, Workflow Integrations, and the 21.1 AI assistant support named in Blackmagic's release and feature list.
Reported by trade press: which scripting routes require Studio from 21.1.
Experimental: community MCP servers for older Resolve versions, and assistants that drive the interface by clicking on screen. Interface automation breaks when a layout, a dialog or a version changes, and it can click the wrong thing in a live project.

Safety on a real project

Blackmagic's README warns about the security implications of running scripts from unknown origins and of allowing access from outside the application. For a project you are paid to protect:

Keep external scripting at Local unless you have a reason for Network.
Test any script or assistant on a copy of the project first. Some actions, such as applying a saved grade, replace a clip's whole node graph.
Know where the assistant runs. A cloud assistant that reads your project receives project data: clip names, metadata, sometimes frames. Whether that is allowed depends on your contract.
Make sure an open Resolve dialog cannot leave a script half-finished. In our experience a modal window can stop scripted actions until it is closed.

How AutoBalance uses this

AutoBalance is a Workflow Integration panel for DaVinci Resolve Studio, in private beta. It uses Resolve's documented scripting interface to read the project and write its corrections to the clips, and it uses Resolve's own Copy Grade to carry a colorist's hero grade. Its grading engine runs locally on the Mac; it is not an AI assistant connected to a cloud service. The colorist presses the buttons and checks the result.

FAQ

Can ChatGPT or Claude color grade in DaVinci Resolve?

From 21.1 they can control Resolve through its AI assistant support and scripting. They can apply LUTs, CDL values and saved grades. Choosing good values for a grade needs measurement of the picture and a colorist's judgment. A general assistant does not provide that by itself.

Does the free version of Resolve support scripting?

The built-in console supports scripting. Trade press reports that external scripting and Workflow Integrations require Studio from 21.1; check Blackmagic's documentation for your version.

Can a script add nodes in Resolve?

Not in the 21.1.2 API reference. A common workaround is to apply a saved grade (a DRX still) or copy a grade from a clip that already has the node structure you want.

Is MCP the same as the scripting API?

No. MCP is a protocol that lets an AI assistant call tools. The scripting API is what those tools use to act on Resolve.

Sources

Blackmagic Design: DaVinci Resolve 21.1 press release, 8 September 2026
Blackmagic Design: DaVinci Resolve Studio 21 feature list (PDF)
Blackmagic Design: DaVinci Resolve Scripting README, API reference (DaVinciResolveScript.pyi) and changelog, installed with Resolve 21.1.2 in the Developer/Scripting folder
CineD: DaVinci Resolve 21.1 released (secondary report on MCP and Studio-only scripting)
Digital Production: Resolve 21.1 adds MCP (secondary report)

Product names belong to their owners. Features change between releases; check the current documentation for your version.