ResolveMCP-ext MCP server
ResolveMCP-ext is a community-driven Model Context Protocol server that extends DaVinci Resolve 21.1.2 scripting capabilities. It fills gaps left by official and other community servers by exposing tools for managing clip effects, copying attributes between clips, exporting frames, looking up media pool folders, and handling camera comparisons. It is designed to coexist with other Resolve MCP servers without overlap.
Package and access
Local package with source-attributed installation metadata. Koskamo does not execute packages during review.
What you can do with it
- Apply, list, remove, toggle, or reorder clip effects
- Copy attributes between clips using Paste Attributes
- Export still frames from clips or media pool items
- Look up which bin a clip or folder resides in
Source and maintenance
- Last repository push
- Latest release
- v1.0.1
- Maintenance checked
Packages and installation
Source-provided package data. Koskamo has not executed or live-probed this package.
resolve-ext 1.0.1
{
"version": "1.0.1",
"transport": "stdio",
"identifier": "resolve-ext",
"runtimeHint": "uvx",
"registryType": "pypi",
"registryBaseUrl": "https://pypi.org",
"environmentVariables": [
{
"name": "RESOLVE_SCRIPT_API",
"description": "Path to the DaVinci Resolve scripting API folder. Optional: the server locates it automatically on Windows, macOS and Linux, and only uses this when set to an existing path."
},
{
"name": "RESOLVE_SCRIPT_LIB",
"description": "Path to fusionscript.dll / fusionscript.so. Optional for the same reason."
}
]
}Tools
Reported by the attributed source; not independently observed by Koskamo.
Maintenance history
Public check and source-refresh events. Editorial and ownership records remain private.
- · repository · passed · metadata changed · updated
- · backfill · recorded · Pre-expansion baseline; unobserved rich metadata remains unknown
Connect from your client
Each snippet configures the same source-provided package; replace placeholders before use.
Cursor
{
"mcpServers": {
"resolvemcp-ext": {
"command": "uvx",
"args": [
"resolve-ext==1.0.1"
],
"env": {
"RESOLVE_SCRIPT_API": "<YOUR_RESOLVE_SCRIPT_API>",
"RESOLVE_SCRIPT_LIB": "<YOUR_RESOLVE_SCRIPT_LIB>"
}
}
}
}Cline
{
"mcpServers": {
"resolvemcp-ext": {
"command": "uvx",
"args": [
"resolve-ext==1.0.1"
],
"env": {
"RESOLVE_SCRIPT_API": "<YOUR_RESOLVE_SCRIPT_API>",
"RESOLVE_SCRIPT_LIB": "<YOUR_RESOLVE_SCRIPT_LIB>"
}
}
}
}VS Code
{
"servers": {
"resolvemcp-ext": {
"type": "stdio",
"command": "uvx",
"args": [
"resolve-ext==1.0.1"
],
"env": {
"RESOLVE_SCRIPT_API": "<YOUR_RESOLVE_SCRIPT_API>",
"RESOLVE_SCRIPT_LIB": "<YOUR_RESOLVE_SCRIPT_LIB>"
}
}
}
}Claude Desktop
{
"mcpServers": {
"resolvemcp-ext": {
"command": "uvx",
"args": [
"resolve-ext==1.0.1"
],
"env": {
"RESOLVE_SCRIPT_API": "<YOUR_RESOLVE_SCRIPT_API>",
"RESOLVE_SCRIPT_LIB": "<YOUR_RESOLVE_SCRIPT_LIB>"
}
}
}
}Let your agent find its tools
Find servers like ResolveMCP-ext from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.