davinci-resolve-mcp
Related Servers
Alternatives to davinci-resolve-mcp
No user-submitted related servers found.
Related Servers
- 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.40 PyPI53MIT
- AlicenseAqualityAmaintenanceEnables AI assistants to control DaVinci Resolve (Free and Studio) through 215 MCP tools covering the full Resolve scripting API, including projects, timelines, media, Fusion, color, and rendering.174 PyPI1MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to control DaVinci Resolve Studio via MCP, providing full scripting API coverage plus workflow helpers for editing, media organization, rendering, grading, and more.7,055 npmMIT
- AlicenseNot gradedqualityFmaintenanceAn 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.22MIT
- AlicenseBqualityBmaintenanceLets AI clients inspect and control DaVinci Resolve projects via MCP tools.4668 npm38MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to control DaVinci Resolve's project, media pool, timeline, color, Fusion, Fairlight and render functions through MCP tools, including an in-app bridge for the free edition. It also runs local Whisper transcription and vision analysis on footage and renders Remotion/Three.js motion graphics straight onto the timeline.7,055 npm3MIT
TDQS
Scored across 20 tools
Each tool maps to a clearly distinct resource or action: project management, timeline control, marker operations, media import, and render control are separated cleanly. The only potentially broad tool, get_status, is distinct from ping because it returns project/timeline/page context rather than just bridge health.
Most tools follow a predictable snake_case verb_noun pattern such as create_project, get_timelines, set_current_time, and delete_marker. Minor deviations exist: ping is a standalone health-check verb, and get_timelines is plural while create_timeline is singular.
Twenty tools is slightly above the ideal compact range, but the server covers several distinct DaVinci Resolve areas: projects, pages, timelines, playhead, markers, media, and rendering. Each tool has a plausible role, so the count is reasonable though somewhat heavy.
The surface covers important project, timeline, marker, media import, and render basics, but has notable gaps. There are no delete/update operations for projects or timelines, no media pool listing or clip-level editing, and render queue job creation/configuration is missing, which can leave start_render as a partial dead end.