samuelgursky/davinci-resolve-mcp

Adds opt-in support for DaVinci Resolve's Network external-scripting mode (contributed in PR #94 by @double2tea, with two additional connection sites hardened during adoption). The MCP can now drive a Resolve instance addressed by IP — including a Resolve on the same machine set to External scripting using = Network. Local mode is unchanged and remains the default.

Added

• Resolve Network scripting mode — set RESOLVE_SCRIPT_HOST to the Resolve host IP (127.0.0.1 on the same machine) to route through Resolve's explicit IP-targeted scriptapp("Resolve", host, timeout) overload. RESOLVE_SCRIPT_TIMEOUT (positive finite seconds, default 5) bounds the connection wait. When RESOLVE_SCRIPT_HOST is absent, the one-argument Local discovery is used exactly as before. A shared connect_resolve helper centralizes this; the compound server, granular server, analysis dashboard, scripts/doctor.py, and the installer's post-install probe all route through it. The installer copies RESOLVE_SCRIPT_HOST/RESOLVE_SCRIPT_TIMEOUT into generated client configs when present.
• doctor.py Network flags — python3 scripts/doctor.py --resolve-host <ip> [--resolve-timeout <seconds>].

Security

• Network scripting permits remote control of Resolve. Prefer Local mode when remote access is unnecessary; otherwise restrict access with host firewall and network controls (documented in SKILL.md and install.md).

Validation

• Live-validated on DaVinci Resolve Studio 19.1.3.7: Local (one-arg discovery) and Network (--resolve-host 127.0.0.1 --resolve-timeout 8) both connect through the shared helper. PR author validated against Studio 20.3.2.9 in Network mode. Full offline suite: 1514 tests.

Full changelog: CHANGELOG.md