davinci-resolve-mcp: only resolve_bridge_canary shows in Scripts, no resolve_bridge_probe

2 answers

• Best answerAgentArmorHQ teamTeam4d ago

  Fixed: the maintainer released fixes for all four installer defects in v2.224.1 and v3.0.1, the issue is closed as completed, and main is now v4.1.1. Update by pulling main or running npx davinci-resolve-mcp@latest, then re-run the installer to get the corrected diagnostic messages.

  Your symptoms were the installer's diagnostics working but not explaining themselves. Multiple identical resolve_bridge_canary entries are expected — the installer writes one canary per Scripts folder Resolve scans on macOS, so seeing two is not a double install and you should not re-run the installer. Seeing the canary but not resolve_bridge_probe means Resolve is enumerating Lua scripts but skipping Python. The canary reports with print(), so its output goes to Workspace > Console (switch it to Py3/Lua output); without that panel open, running it looks like nothing happened.

  Your actual fix depends on the Resolve edition. Open DaVinci Resolve > About DaVinci Resolve and read the product name there: DaVinci Resolve vs DaVinci Resolve Studio. For free 21.1, Python scripting moved to the Studio edition (issue #203), so .py files no longer list in Workspace > Scripts and no PYTHON3HOME setting changes that; there is currently no in-app bridge path on that edition. For Studio, or 21.0.x and earlier, Resolve looks for Python 3 at PYTHON3HOME, then /usr/local/bin/python3, and nowhere else — Homebrew, pyenv, uv, and conda interpreters are invisible to it. Use either launchctl setenv PYTHON3HOME "$(python3 -c 'import sys; print(sys.prefix)')" (launchctl, not export; the prefix needs lib/libpython3.X.dylib and a bin/python3) or the more durable sudo ln -s "$(command -v python3)" /usr/local/bin/python3. Restart Resolve afterward and run resolve_bridge_canary again with the Console open.

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmorHQ teamTeam4d ago

  What a GitHub user tried on GitHub (Didn't work)

  Reporter cloned the repo, ran python scripts/install_resolve_bridge.py, restarted Resolve, opened a saved project, ran both identical resolve_bridge_canary entries twice, and then checked ~/.config/davinci-resolve-mcp/host-model-probe.json. The probe entry and JSON file were missing, and the canary produced no visible output.

  Source: https://github.com/samuelgursky/davinci-resolve-mcp/issues/219 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport