# Resolve Fusion

Fusion composition work in the DaVinci Resolve MCP.

- Repository: https://github.com/samuelgursky/davinci-resolve-mcp (3887 stars)
- Category: AI and agents
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add samuelgursky/davinci-resolve-mcp --skill resolve-fusion -g -a claude-code -y`
Codex: `npx skills add samuelgursky/davinci-resolve-mcp --skill resolve-fusion -g -a codex -y`
Cursor: `npx skills add samuelgursky/davinci-resolve-mcp --skill resolve-fusion -g -a cursor -y`
Gemini CLI: `npx skills add samuelgursky/davinci-resolve-mcp --skill resolve-fusion -g -a gemini-cli -y`

## Description

Fusion composition work in the DaVinci Resolve MCP. Apply when building or editing Fusion comps, titles, motion graphics, VFX, merges, masks, trackers, on a timeline item live in a running Resolve OR authoring a .comp declaratively offline. Routes to the live fusion_comp tools and the offline fusion authoring tool.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Resolve Fusion
Thin router; depth stays in the kernel.

- **Live tool mechanics**, `docs/kernels/fusion-composition-kernel.md` (the
  `fusion_comp` boundary).
- **Offline authoring**, `resolve-advanced/README.md` → the `fusion` tool.

## Live subtitle effects

Discover installed factory titles/subtitle presets with
`timeline_ai.list_title_presets`. For subtitle-track effects use live
`timeline_ai.set_subtitle_preset` with a preset name or full template ID; omit
`preset` to adjust the current effect. Common literal `inputs` cover font/style,
size/position and text RGBA. Highlight/outline mappings are Word Highlight-specific.
Unmapped or connected/animated controls are refused. Other installed subtitle
presets are captured natively in a temporary title timeline and applied through
DRT interchange; the original edit remains recoverable. Ordinary Fusion titles
use `timeline.insert_fusion_title` with the full template ID, then scoped
`fusion_comp` probes/input writes. Keep Resolve open and inspect native rendered
frames. Do not route routine effects to Project.db. Unbundled dry runs need an
existing `preset_reference` to avoid live capture. Caption text/timing corrections
can use live UI; direct DB maintenance remains offline. See
`docs/guides/title-library-automation.md` and
`docs/guides/subtitle-track-editing.md`.

## Two servers, author offline, apply live

| Job | Server | Tools |
|---|---|---|
| Build/edit a comp on a **running** timeline item | `davinci-resolve` (Python, live) | `fusion_comp` (`probe_fusion_comp`, `safe_add_tool`, `safe_set_inputs`, `safe_connect_tools`, `fusion_boundary_report`) |
| Author a `.comp` from a spec/template with **no Resolve open** | `davinci-resolve-advanced` (Node) | `fusion` (`generate`, `generate_from_template`, `list_templates`, `to_api_calls`) |

## Flow

The rest: https://github.com/samuelgursky/davinci-resolve-mcp/blob/HEAD/.agents/skills/resolve-fusion/SKILL.md