{"id":"apvlv-davinci-resolve-mcp","name":"davinci-resolve-mcp","af_score":48.2,"security_score":23.8,"reliability_score":17.5,"what_it_does":"An MCP server that lets an AI client (e.g., Claude Desktop or 5ire) connect to DaVinci Resolve Studio and perform actions such as project/timeline/media management, opening pages, working with Fusion compositions, querying current state, and executing Python/Lua code inside Resolve/Fusion.","best_when":"You want an AI assistant to drive a local DaVinci Resolve workflow (project/timeline/media/Fusion) and you can accept the security implications of the provided execution tools.","avoid_when":"You cannot sandbox or restrict the assistant’s ability to call execute_python/execute_lua, or you need strong guarantees around idempotency, safety checks, and consistent error handling.","last_evaluated":"2026-03-30T15:21:05.855781+00:00","has_mcp":true,"has_api":false,"auth_methods":["None specified (implied local MCP connection)"],"has_free_tier":false,"known_gotchas":["Includes high-risk actions: execute_python(code) and execute_lua(script); agents must be constrained to safe code and validated parameters.","Resolve/Fusion statefulness: many operations depend on the current project/timeline/media pool; agents may need to call status/current resources first to avoid acting on the wrong context.","Potential off-by-one / indexing assumptions are hinted by commands like set_current_timeline(index) being 1-based; agents should confirm indexing from retrieved resources.","Non-idempotent operations (create_project/create_timeline/import_media/add_fusion_comp_to_clip/create_fusion_node) may duplicate work if retried without guards."],"error_quality":0.0}