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