FilmCraft

Operate FilmCraft through its structured automation interface, using the user's intended project and sequence.

Protocol reference

Read the relevant sections of references/control-protocol.md before constructing calls. This is an unmodified upstream snapshot downloaded on 2026-10-08.

Source: FilmCraft control protocol. The upstream MIT license is included in references/LICENSE-MIT.

Search the reference for Desktop control channel, Selection or explicit targets, Moving clips, Trim mode, Replace With Clip, Audio mixing, Essential Sound, Colour, Keyboard shortcuts, and MCP as relevant. Relative links resolve against https://github.com/storytold/filmcraft/blob/main/docs/. For MCP argument schemas, CLI persistence, and export progress/cancellation, consult upstream agent documentation, Part 1. For save, recovery, relinking, and proxy commands, consult project-files.md when needed. If installed behavior differs, inspect the installed command registry and tool schemas rather than inventing parameters.

Choose the session

Discover available FilmCraft tools and executables, and reuse an appropriate existing session. A user's open project requires the desktop bridge; a headless session is a separate in-process project and cannot edit the live window. For file-based unattended work, use headless MCP or CLI.

Desktop control and bridge examples (adapt executable paths and port):