davinci-resolve-mcp
by uncleteej
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RESOLVE_MCP_LOG_FILE | No | Path to server.log (a path, or empty for no file). | |
| DAVINCI_RESOLVE_BRIDGE | No | Set to 1 to force the in-app bridge transport. It becomes the only transport tried, so a bridge that stops answering reports its own fault rather than falling back to another transport. When unset, the bridge is used automatically only when external scripting is unavailable. | |
| RESOLVE_MCP_TRACE_FILE | No | Path to the execution-trace file. Defaults to logs/execution-traces.jsonl beside server.log. | |
| RESOLVE_MCP_RESULT_ENVELOPE | No | Sets the shape of the operation envelope per process: 'pure' or 'legacy'. Can also be changed per call via params={"envelope": ...} or persistently via setup(action="set_defaults", params={"result_envelope": ...}). | |
| DAVINCI_RESOLVE_BRIDGE_CONFIG | No | Path to the authenticated in-app bridge configuration file. Defaults to ~/.config/davinci-resolve-mcp/bridge.json. Set it while running the installer and in the MCP client environment so both sides use the same path. | |
| RESOLVE_MCP_DISABLE_TRAP_GUARD | No | Set to 1 to disable both the verified-trap refusal and the advisory push. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |