A side-by-side look at the DaVinci Resolve Local Bridge MCP and Davinci Resolve AI 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 Local Bridge MCP for multimedia process work as a local process; choose Davinci Resolve AI Bridge MCP for multimedia process as a local process. You can also run both side by side in one mcpServers block.
resolve_health.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Multimedia Process | Multimedia Process |
| Quality signal | 55/100 · Good | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 33 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 1 | Not listed |
| Full listing | View DaVinci Resolve Local Bridge MCP | View Davinci Resolve AI Bridge MCP |
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.No tool names declared yet. Check the project README from the listing page.
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-local-bridge-mcp": {
"command": "uvx",
"args": [
"davinc-resolve-local-bridge-mcp"
]
}
}
}
{
"mcpServers": {
"flamexnreal-davinci-resolve-ai-bridge-mcp": {
"command": "npx",
"args": [
"-y",
"davinci-resolve-ai-bridge-mcp"
]
}
}
}