A side-by-side look at the DaVinci Resolve Lite MCP and DaVinci Resolve Local Bridge MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose DaVinci Resolve Lite MCP for multimedia process work as a local process; choose DaVinci Resolve Local Bridge MCP for multimedia process as a local process. You can also run both side by side in one mcpServers block.
DAVINCI_MCP_LOG_DIR.resolve_health.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Multimedia Process | Multimedia Process |
| Quality signal | 40/100 · Fair | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | DAVINCI_MCP_LOG_DIR | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 5 | 1 |
| Directory activity | 2 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 1 |
| Full listing | View DaVinci Resolve Lite MCP | View DaVinci Resolve Local Bridge MCP |
No tool names declared yet. Check the project README from the listing page.
resolve_healthCheck if DaVinci Resolve bridge is running. The bridge script must be running inside Resolve via Workspace > Scripts > DaVinciResolveBridge. If this returns an error, the bridge is not running.Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
{
"mcpServers": {
"davinci-resolve-lite-mcp": {
"command": "uvx",
"args": [
"davinci-resolve-lite-mcp"
],
"env": {
"DAVINCI_MCP_LOG_DIR": "YOUR_DAVINCI_MCP_LOG_DIR_HERE"
}
}
}
}
{
"mcpServers": {
"davinci-resolve-local-bridge-mcp": {
"command": "uvx",
"args": [
"davinc-resolve-local-bridge-mcp"
]
}
}
}