DaVinci Resolve MCP Server
Related Servers
Alternatives to DaVinci Resolve MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseBqualityBmaintenanceControl DaVinci Resolve Studio from MCP clients. Provides tools and resources for editing, color grading, Fusion compositing, audio, playback, and rendering.32-
- AlicenseNot gradedqualityFmaintenanceComprehensive MCP server for DaVinci Resolve with 295+ tools to control projects, timelines, editing, color grading, rendering, and more via natural language.106 PyPI6MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that exposes the complete DaVinci Resolve scripting API, enabling AI assistants to control DaVinci Resolve programmatically with over 440 tools for project management, timeline editing, color grading, rendering, and more.8MIT
- AlicenseBqualityAmaintenanceLets AI clients inspect and control DaVinci Resolve projects via MCP tools.44406 npm23MIT
- AlicenseNot gradedqualityCmaintenanceExposes 20 tools for project, media, render, and timeline control in DaVinci Resolve 18+ via stdio MCP, enabling AI agents to operate the software through natural language.52MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to control DaVinci Resolve Studio through the official Scripting API, with full API coverage plus workflow helpers for editing, grading, Fusion, Fairlight, and project lifecycle tasks. Includes a compound tool mode for low context usage, a granular 341-tool mode, a local control panel, and an optional advanced offline server for working with Resolve project files.13,874 npmMIT
TDQS
Scored across 212 tools
Tool names use clear resource prefixes (project_, timeline_, clip_, item_, render_, media_pool_) that make most purposes obvious. A few pairs blur together—clip_get_metadata vs clip_get_properties, clip_transcribe_audio vs media_transcribe, and storage_import_to_pool vs media_pool_import_media—but the descriptions clarify the distinctions.
The set is uniformly snake_case with verb_noun structure and heavy resource prefixes, so naming is predictable. Minor inconsistencies like list/get/read interchange, project_folder_goto_parent vs project_folder_goto_root, and standalone media_probe/media_streams/cdl_read keep it from being perfect.
212 tools is far beyond the 3–15 well-scoped range and would overwhelm an agent's context and tool-selection process. Even for DaVinci Resolve's broad surface, many atomic operations could be grouped into parameterized tools (e.g. one marker tool with an action parameter).
Coverage is remarkably extensive: project lifecycle, media pool, clips, timelines, items, color, Fusion, Fairlight, gallery, render, extensions, and media analysis are all represented. It misses a few useful controls such as undo/redo, arbitrary timeline-insert positioning, and deeper Fairlight mixing operations, but there are no major dead ends.