B — Some risk signals Graded October 16, 2026Minor concerns worth a quick check.Based on public adoption and transparency signals as of October 16, 2026. Our opinion, not a code audit or security guarantee.
App connector · Cloud & infrastructure
davinci-resolve-mcp
MCP server integration for DaVinci Resolve Studio
Bottom line: Signal-based grade (5/7 points): well starred on GitHub, listed in several sources, public source code. This reflects adoption and transparency, not a code audit.
- Popularity score
- 70/100
- Rank
- #16 of 500
- GitHub stars
- 3.6k
- Weekly downloads
- 5.6k
What it does
davinci-resolve-mcp is an MCP server that integrates DaVinci Resolve Studio—professional video editing software—with AI agents and Claude, enabling programmatic control of editing tasks, timeline manipulation, and project workflows. It bridges the gap between AI systems and a complex desktop application, allowing agents to automate or assist with video production work.
Who it’s for
Video editors, production teams, and builders integrating AI automation into post-production pipelines who want AI agents to interact with DaVinci Resolve without manual intervention. Organizations seeking to reduce repetitive editing tasks or experiment with AI-assisted video workflows.
Copy-paste setup
Check these steps against the project’s own instructions before running anything.
Verify against the repo README at https://github.com/samuelgursky/davinci-resolve-mcp (opens external site) for the latest installation method. Typically installed via npm (npm install davinci-resolve-mcp) and configured in Claude Desktop's mcpServers config or used programmatically. Exact setup depends on your MCP client and whether DaVinci Resolve is running locally.
Risks
- Local file/project access: The MCP connector likely has broad access to DaVinci Resolve projects and associated media files; compromised agents could read, modify, or delete video projects and assets.
- Prompt injection: Without strict input validation, malicious prompts could inject commands that manipulate video timelines, export sensitive content, or trigger unintended edits.
- Application-level abuse: An agent with resolve control could export projects in unencrypted formats, make unauthorized copies, or expose embedded metadata/licenses.
- Dependency chain risk: npm package and GitHub repo maintenance history should be verified; no verified publisher signal.
- Credential scope unclear: Verify whether credentials for cloud export (Dropbox, Frame.io, etc.) are required and how they're scoped within the connector.
How to stay secure
Least-privilege permissions
- Run the MCP connector and DaVinci Resolve under a dedicated, non-admin user account with read-only access to archived projects; grant write access only to a single working directory.
- Disable or restrict cloud export credentials (Dropbox, Frame.io, etc.) to specific folders with expiring tokens; never store permanent API keys in connector config.
- Implement file system ACLs to block the connector process from accessing sensitive directories outside the active project workspace.
Network isolation
- Run the MCP connector in an isolated container or VM with no internet access; use an allowlist for only required internal communication with the DaVinci Resolve application.
- Disable any automatic update mechanisms for the connector; vet and manually deploy updates after security review.
- Block outbound connections to cloud services unless explicitly needed; proxy cloud exports through a gateway that logs and validates all requests.
Monitoring
- Log all file access, modifications, and deletions performed by the connector; alert on bulk operations or access to non-project directories.
- Monitor MCP message traffic for suspicious patterns: commands with encoded payloads, repeated failed operations, or requests to export/copy projects outside standard workflows.
- Track authentication events and credential usage; alert if cloud export tokens are used outside normal export times or to unexpected destinations.
Red flags to watch for
- Unusual prompt patterns: requests with shell metacharacters, base64-encoded strings, or commands to modify timelines without context.
- File operations: reads of unrelated media libraries, writes to system directories, or bulk exports of projects to external storage.
- Dependency concerns: unverified npm package updates, forks from unmaintained repos, or added transitive dependencies with poor security history.
Alternatives
- FFmpeg MCP / video processing servers: Lower-level, headless video processing without GUI app integration; better suited for batch automation.
- Adobe Premiere Pro API / UME integrations: Proprietary but potentially more mature enterprise video editing automation.
- Custom Python/Node.js scripting with DaVinci Resolve's Lua/Python API: More control and transparency, but requires bespoke integration work.
- Cloud-native video APIs (e.g., Mux, Cloudinary, AWS MediaConvert): SaaS-based, no local app dependency; less suited to interactive editing workflows.