Report connection state, Resolve version, and the current project and timeline.

Call this first in a session, and again whenever you are unsure what Resolve has open. The result — like every result from this server — echoes context: connected, Resolve version, project, timeline and fps.

List the project names in Resolve's current database folder.

Use it to find the exact name to hand to open_project — names must match exactly.

Open the named project, making it the one every later tool call acts on.

The name must match exactly; list_projects shows what is available. The result echoes the new context, so you can confirm the switch landed.

Write an opaque .drp backup of the open project, and return where it landed.

Take a snapshot before any big operation — a build, a bulk media change, a risky escape-hatch script — so a mistake is a restore rather than a rebuild. Without a path, the snapshot goes to a timestamped file in the cache directory.

Run DaVinci Resolve scripting-API Python in the server process.

Prefer the real tools: they wrap known API footguns, echo context, and return structured results. Reach for this only where no tool fits — an API corner the catalog does not cover yet, or a one-off inspection.

The namespace has resolve, project_manager, project and timeline pre-bound. The returned value is the trailing expression, or a result variable if you set one; stdout is captured and returned alongside it. Long values are truncated.