samuelgursky/davinci-resolve-mcp: README-based editorial guide

samuelgursky/davinci-resolve-mcp describes itself in the README as "MCP server integration for DaVinci Resolve Studio". This article keeps to facts that can be checked in the repository. Stars, forks, and promotional badges are signals of attention, not proof of quality. Under "DaVinci Resolve MCP Server", the README says: A Model Context Protocol (MCP) server that lets AI assistants control DaVinci Resolve Studio through the official Scripting API. It provides full API coverage plus guarded workflow helpers for editing, media pool organization, render. That establishes the project's stated boundary, not a production test.

The README's "Bradford Post Assistant , managed application (closed beta)" section gives a useful starting point for deciding whether the project fits: Memory , persistent, encrypted on-device assistant memory plus cross-episode learning. If that problem is not yours, popularity is a poor reason to adopt it. Project names, commands, and component names are kept as written so a reader can return to the primary source without guessing at terminology. Another checkable README item is: A post-production copilot , a desktop app that sits alongside DaVinci Resolve and. It can shape a first test, but it does not replace testing in the intended environment.

The operating model is spread across sections such as "Quick Start". The source evidence includes: Before connecting, open DaVinci Resolve Studio and set Preferences > General > External scripting using to Local. (On the free edition that preference does not help , see Free edition The npm launcher installs a managed copy under your. This article does not turn missing architecture, performance, or security details into claims. A real deployment still needs a look at the repository layout, configuration files, and release history.