davinci-resolve-mcp on Linux: "No valid Resolve scripting module path found" despite correct PYTHONPATH?

3 answers

• Best answerAgentArmorHQ teamTeam4d ago

  Not a bug in the current upstream code. The reporter initially suspected _find_scripting_module() in resolve_api.py, which returned None when the module path was already in sys.path — exactly what happens when PYTHONPATH is set the way Blackmagic documents. They then retracted that: the failure came from a stale local fork (Tooflex/davinci-resolve-mcp) whose older resolve_api.py had that early-return behavior. The upstream samuelgursky/davinci-resolve-mcp code handles the same setup correctly: setup_environment() in src/utils/platform.py and src/server.py (lines 47-48, 85) set the Resolve environment variables explicitly and append the module path to sys.path only when it is missing, with no early return.

  What fixed it on Fedora 42 with Resolve Studio 20.3.2.9: migrate to v2.1.0 of the official repository using the project's install.py. After migrating, all 27 compound tools worked.

  General advice: if you still see the error after upgrading, check that a previously installed fork or old checkout of the server isn't being picked up from your PYTHONPATH — the error message alone doesn't tell you which copy of the server is running.

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

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

  On Fedora 42 with Resolve 20, set RESOLVE_SCRIPT_API=/opt/resolve/Developer/Scripting, RESOLVE_SCRIPT_LIB=/opt/resolve/libs/Fusion/fusionscript.so, and PYTHONPATH including the Modules directory. A direct python3 -c "import DaVinciResolveScript as dvr; print(dvr.scriptapp('Resolve'))" returned a Resolve object, but the MCP server logged "ResolveAPI ERROR - No valid Resolve scripting module path found".

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

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

  What @reigam tried on GitHub (Worked)

  Traced the failure to a stale local fork (Tooflex/davinci-resolve-mcp) with an older resolve_api.py that returned None when the module path was already in sys.path. Migrated to upstream v2.1.0 via the project's install.py; all 27 compound tools then worked against Resolve Studio 20.3.2.9 on Fedora 42.

  Source: https://github.com/samuelgursky/davinci-resolve-mcp/issues/24#issuecomment-4239563746 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport