io.github.Airta-Admin/davinc-resolve-local-bridge-mcp
Related Servers
Alternatives to io.github.Airta-Admin/davinc-resolve-local-bridge-mcp
No user-submitted related servers found.
Related Servers
- 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.11,225 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to control DaVinci Resolve Studio through the official Scripting API, covering editing, media pool, render, grading, Fusion, Fairlight, and project lifecycle tasks.11,225 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to control DaVinci Resolve Studio through the official Scripting API, covering editing, media pool management, rendering, grading, Fusion, Fairlight, and project lifecycle tasks.11,225 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to automate DaVinci Resolve Free through MCP by creating timelines, managing clips and markers, importing media, adjusting properties, and queueing or starting renders via a local Lua bridge. It also allows arbitrary Lua execution inside Resolve for advanced project automation.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible AI assistants to inspect and automate DaVinci Resolve Studio projects, timelines, markers, media pool assets, and render jobs through natural language.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to control DaVinci Resolve (Free and Studio) through natural language, providing 162 tools for timeline editing, color grading, rendering, and more. Includes local AI replacements for Studio-only features like voice isolation, background removal, and transcription.1MIT
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion or overlapping purposes. The tool's purpose is unambiguous.
The single tool name follows a clear verb_noun pattern (resolve_health), which is consistent and descriptive. With only one tool, naming consistency is inherently strong.
A single health-check tool is far too few for a server presumably meant to bridge to DaVinci Resolve. Even as a minimal health-only server, one tool feels extremely thin and provides little value beyond a ping.
The server only provides a health check, with no ability to interact with DaVinci Resolve projects, timelines, renders, or any other meaningful operations. This is a severely incomplete surface for a bridge to a complex application.