DaVinci Resolve 21.1 Ships Native MCP Server for Claude and ChatGPT Automation

On September 8, 2026, Blackmagic Design officially rolled out DaVinci Resolve 21.1, introducing a built-in native Model Context Protocol (MCP) server that establishes direct bidirectional communication between the NLE and modern AI coding agents. Through this integration, video editors and pipeline engineers can connect MCP-compliant clients such as Claude Code and ChatGPT to execute end-to-end post-production tasks—from project initialization and rough cuts to speaker-diarized subtitling, baseline color grading, and batch rendering—entirely through natural language commands.

Image source: Blackmagic Design / @EHuanglu on X

Native MCP Architecture: 88 Tools and 20 State Resources

Unlike third-party wrapper scripts or fragile external macro bridges, the MCP server in DaVinci Resolve 21.1 is implemented natively within the application core. The server exposes a comprehensive development interface comprising 88 operational tools and 20 read-only state resources across every primary post-production workspace.

Agents gain programmatic control over project lifecycle operations, Media Pool asset ingestion, cut and edit timeline assembly, Color page grading parameters, Fairlight audio track routing, and Deliver page render queues. Meanwhile, the 20 read-only resources allow agents to inspect real-time timeline track structures, clip timecodes, and node tree hierarchies, enabling accurate, context-aware decisions before modifying any active sequence.

Workflow Automation via Claude Code and ChatGPT

The practical breakthrough of native MCP integration lies in condensing repetitive, time-intensive editing chores into conversational prompts. By interfacing directly with DaVinci Resolve's native AI toolset, external agents can autonomously orchestrate complex multi-step pipelines without manual GUI interaction.

For example, an agent can initiate speaker-diarized transcription across raw interview footage to generate synchronized subtitle tracks on the timeline, or deploy Smart Reframe and IntelliSearch algorithms to automatically reformat 16:9 widescreen footage into 9:16 vertical video optimized for short-form platforms. Editors can also instruct agents to apply monochrome color passes, trigger motion deblur processing, and queue export deliverables using standardized rendering presets in a single continuous session.

Studio License Prerequisites and Operational Scope

Deploying the DaVinci Resolve 21.1 MCP server into production requires clear understanding of its licensing and operational boundaries. Because the MCP bridge relies on DaVinci Resolve's external scripting API architecture, native MCP server functionality is supported exclusively within the commercial DaVinci Resolve Studio environment ($295 perpetual license). The free standard version restricts external scripting access.

Additionally, studios should align agent deployment with appropriate editorial workloads. MCP automation excels at structured, procedural tasks such as rough-cut assembly, bulk transcription, aspect ratio conversion, and batch rendering queues rather than nuanced artistic grading or frame-accurate creative cut decisions. Before running automated sessions, technical directors must configure client-side MCP settings and verify local scripting environment variable linkages.

Sources

• Blackmagic Design Official Release: DaVinci Resolve 21.1 Software Update and Studio Developer API Reference
• @EHuanglu on X: DaVinci Resolve 21.1 Native MCP Server Architecture and Workflow Breakdown