AGENTS.md
+51 −24
https://raw.githubusercontent.com/captrauti/ResolveMCP-ext/HEAD/AGENTS.md
− Ten tools, one entry point, pure Python. No compiled parts.− ### The Resolve MCP landscape — three servers, no overlap− Before installing anything, understand that Resolve is covered by three− needs all three**; installing one and finding a capability missing is the usual− | **community** (`samuelgursky/davinci-resolve-mcp`) | npm or git | 37 (390 with `--full`) | The workhorse: granular tools for editing, media pool, render, markers, grading, Fusion. Plus a second `davinci-resolve-advanced` server (18 Node tools) for source-safe media analysis. |− | **this project** (`resolve-ext`) | pip | 10 | The gaps the other two leave: clip effects and their properties, Paste Attributes, frame export, photo albums, node-graph labelling, and the multi-camera comparison layouts. |− They coexist. All three talk to the same Resolve through the same scripting API,− which is **single-client** — so register them together, but know they share one− Resolve.− "the Resolve MCP", ask which of these they mean, or install all three.− ## Full setup — install all three− Do these in order. Steps 1 and 2 are independent; step 3 assumes step 2 exists,− ### Server 3 — this project− pip install https://github.com/CaptRauti/ResolveMCP-ext/releases/download/v1.0.0/resolve_ext-1.0.0-py3-none-any.whl− ### Finally — check all three are live− present. The three name-spaces are distinguishable at a glance:− pip install https://github.com/CaptRauti/ResolveMCP-ext/releases/download/v1.0.0/resolve_ext-1.0.0-py3-none-any.whl− pipx install https://github.com/CaptRauti/ResolveMCP-ext/releases/download/v1.0.0/resolve_ext-1.0.0-py3-none-any.whl− `/reload-mcp`). Then confirm all ten tools are present:− `camera_comparison`, `clip_attrs`, `clip_position`, `effects`, `export_frame`,− `folder_ops`, `node_graph`, `photo_albums`, `project_extras`,− `resolve_ext_status`− | Only some of the three servers' tools are present | That is normal until all three are registered | They are separate servers; see "Full setup" |− commands, and all ten tools. One file on purpose; it is a companion server,+ Fifteen tools, one entry point, pure Python. No compiled parts.+ ### The Resolve MCP landscape — four servers, no overlap+ Before installing anything, understand that Resolve is covered by four+ needs all four**; installing one and finding a capability missing is the usual+ | **community** (`samuelgursky/davinci-resolve-mcp`) | npm or git | 36 (349 with `--full`) | The workhorse: editing, media pool, render, markers, grading, Fusion — related operations grouped behind action parameters. The `--full` variant is the same API surface, one tool per method; it costs context, not capability. |+ | **community, advanced** (`davinci-resolve-advanced-mcp`) | same package, Node | 18 | **Beyond the scripting API.** Reads and edits Resolve *files* — `.drp`/`.drt`/`.drx` and the project's SQLite `Project.db` — **with no Resolve running**. Offline grade/QC catalog, conform/relink QC, node-graph relayout, provenance. The optional deps `better-sqlite3`, `sharp`, `js-yaml`, `pg` are what unlock `project_read`, `conform.verify` and `pipeline`; install with `--include=optional`. |+ | **this project** (`resolve-ext`) | pip | 15 | The gaps the other three leave: clip effects and their properties, Paste Attributes, frame export and thumbnail grids, auto colour, ASC CDL, photo albums, J-cut/L-cut audio offsets, camera-comparison layouts, job status, the media Clone Tool. |+ They coexist. The live servers talk to the same Resolve through the same+ scripting API, which is **single-client** — so register them together, but know+ they share one Resolve. The advanced server talks to Resolve's *files* instead,+ so it works even when Resolve is closed.+ "the Resolve MCP", ask which of these they mean, or install all four.+ ## Full setup — install all four+ Do these in order. Steps 1 and 2 are independent; step 4 assumes step 2 exists,+ ### Server 3 — the community server's advanced sibling (offline file access)+ This is the one server that does **not** talk to Resolve. It reads and edits+ Resolve's files directly — `.drp` / `.drt` / `.drx` projects and the SQLite+ `Project.db` — so it works with Resolve closed, and it is the only way to+ inspect a project without opening it. 18 Node tools.+ ```bash+ git clone https://github.com/samuelgursky/davinci-resolve-mcp.git+ cd davinci-resolve-mcp+ # The four dependencies that matter are OPTIONAL deps — a plain `npm install`+ # skips them and project_read / conform.verify / pipeline then refuse to run.+ npm install --prefix resolve-advanced --include=optional+ # Register it (this project's own doctor prints the exact block for this machine):+ resolve-ext doctor+ # or by hand:+ # command: node+ # args: <checkout>/bin/davinci-resolve-advanced-mcp.mjs+ ```+ Needs only Node ≥18 — no Python, no Resolve, no scripting-API environment+ variables. Because it never touches the scripting API, it does not compete for+ the single client slot the other three share.+ **Tool-call shape:** `{"action": "<name>", "args": {…}}` — the action name goes+ in `action`, its parameters in `args`. A flat argument object fails validation.+ The action list lives in each tool's *description*, not its schema (which is+ generically `{action, args}`), so read the description before the first call.+ ### Server 4 — this project+ pip install https://github.com/CaptRauti/ResolveMCP-ext/releases/download/v1.0.4/resolve_ext-1.0.4-py3-none-any.whl