Davinci Resolve MCP vs Upres Cli
A side-by-side look at the Davinci Resolve MCP and Upres Cli 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 Upres Cli for multimedia process as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Davinci Resolve MCP when
- You need dedicated capabilities in the Multimedia Process domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Choose Upres Cli when
- You need dedicated capabilities in the Multimedia Process domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
UPRES_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Multimedia Process | Multimedia Process |
| Quality signal | 64/100 · Good | 39/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 | UPRES_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3,394 | 0 |
| 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 Upres Cli |
Tools & capabilities
Davinci Resolve MCP tools
No tool names declared yet. Check the project README from the listing page.
Upres Cli tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
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.
Davinci Resolve MCP
{
"mcpServers": {
"samuelgursky-davinci-resolve-mcp": {
"command": "npx",
"args": [
"-y",
"davinci-resolve-mcp"
]
}
}
}
Upres Cli
{
"mcpServers": {
"upres-cli": {
"command": "npx",
"args": [
"-y",
"upres-cli"
],
"env": {
"UPRES_API_KEY": "YOUR_UPRES_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Davinci Resolve MCP is categorized under Multimedia Process and uses a local stdio subprocess. Upres Cli belongs to Multimedia Process and uses a local stdio subprocess. Pick Davinci Resolve MCP for multimedia process work and Upres Cli for multimedia process.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Davinci Resolve MCP is listed as free. Auth: no auth required. Upres Cli has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add samuelgursky-davinci-resolve-mcp and upres-cli as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Davinci Resolve MCP has a quality signal of 64/100 (Good) with 6 views, 0 installs and 3,394 GitHub stars. Upres Cli has 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.