DaVinci Resolve MCP — Control Resolve via AI

Main

• Use compound mode first: README recommends the 31-tool surface unless you need the full one-tool-per-method set.

• Treat source media as immutable: README documents a “source media safety” posture and sidecar analysis outputs.

• Validate Resolve settings: external scripting must be set to Local (Preferences → General) before connecting.

• Keep context low: compound actions group operations behind parameters to reduce token use and tool chatter.

Source-backed notes

• README shows python install.py as the primary installer and notes it can configure multiple MCP clients.
• README lists two server modes: 31 compound tools vs 328 granular tools, with 100% API coverage claims in its stats section.
• README documents Resolve requirements: Studio edition and external scripting enabled.

FAQ

• Does it work with the free Resolve edition?: README states external scripting requires DaVinci Resolve Studio.
• Which mode should I use?: Start with compound mode (31 tools). Switch to granular (328) only if you need method-level control.
• What’s a safe first task?: List projects/timelines and read metadata first, then do writes like render settings after you’re confident.