video-harness
Related Servers
Alternatives to video-harness
No user-submitted related servers found.
Related Servers
- 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
- AlicenseNot gradedqualityFmaintenanceComprehensive MCP server for DaVinci Resolve with 295+ tools to control projects, timelines, editing, color grading, rendering, and more via natural language.137 PyPI6MIT
- AlicenseCqualityBmaintenanceA stdio MCP server for DaVinci Resolve on macOS, enabling project control, timeline navigation, frame capture, grade application, and validation through the official Resolve scripting API.64MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that connects AI coding assistants to DaVinci Resolve, enabling query and control through natural language.MIT
- FlicenseNot gradedqualityBmaintenanceMCP server for DaVinci Resolve video editing, enabling AI agents to execute editing operations, manage creative libraries, and analyze media content.-
- FlicenseBqualityBmaintenanceControl DaVinci Resolve Studio from MCP clients. Provides tools and resources for editing, color grading, Fusion compositing, audio, playback, and rendering.32-
TDQS
Scored across 15 tools
Most tools target clearly distinct resources and actions, with clear prefixes for media, timeline, markers, and clips. The main overlap is between marker_upsert and markers_from_metadata, plus timeline_assemble combining functions that individual tools already provide, but descriptions make the intended use reasonably clear.
The dominant pattern is resource-first names like timeline_place and markers_query, which is predictable and readable. Minor inconsistencies exist: standalone verbs like reconnect, doctor, and inspect, plus singular/plural mixing between marker_upsert and markers_query/clear.
At 15 tools, the set stays within the well-scoped range and each tool serves a distinct purpose in the video editing workflow. The count feels appropriate for covering connection diagnostics, project inspection, media import, timeline assembly, clip styling, markers, and metadata without bloat.
The core lifecycle for building a rough cut is well covered: import media, ensure timelines, place/lift clips, set colors, and manage markers. However, there is no media deletion/rename, metadata write support, or render/export capability, so full end-to-end project management is not possible.