No user-submitted related servers found.
Scored across 132 tools
Most tools are organized around distinct Resolve subdomains (media pool, timeline, color, render, Fusion, UI), and descriptions clearly separate timeline markers from clip markers, or gallery stills from frame export. The main ambiguity is the cluster of code-execution tools (resolve_exec, fusion_lua, fusion_page_lua, resolve_inspect) and similar-sounding pairs like clip_relink/proxy_link or still_export/frame_export, but these are adequately differentiated in text.
The set overwhelmingly follows a resource_action pattern (clip_delete, timeline_create, project_save, render_start, track_add, version_load), which is easy to predict. It is not a perfect 5 because retrieval operations alternate between _list, _get, and bare plural nouns (clip_list vs markers_get vs timeline_items vs storage_volumes), and a few actions invert to verb_object (insert_title, detect_scene_cuts).
132 tools is far beyond even the 16-25 'heavy' band and will overwhelm an agent's tool-selection and context budget. Although the domain (DaVinci Resolve) is broad and each tool maps to a real API operation, the surface should be split into smaller focused servers or curated to the core workflows.
The tool surface covers the full lifecycle across projects, media pool bins/clips, timelines/tracks, markers, color grading, Fusion comps, render queue, and even UI automation, so there are no obvious dead ends. Minor gaps remain, such as no dedicated timeline clip move/trim or undo/audio-mix tools, though resolve_exec can fill those gaps.