The file tools give it the workspace and the screenshot closes the loop, so it checks what the stage actually renders rather than assuming its edit worked. Authentication and destinations run through the same CLI surface, which means nothing has to leave the conversation.
The MCP side of the Dazzle binary. dazzle mcp runs a stdio server for Dazzle's cloud stages, which are browser-rendered scenes you can stream to Twitch, Kick or any RTMP destination, and it exposes the stage workspace plus the full CLI to an agent.
- The stage workspace listed as relative paths, one per line (list_files), and any file in it read back (read_file)
- Exact-string edits to a stage file, where the old string has to match exactly once (edit_file)
- Files written into the stage workspace (write_file)
- A screenshot of the stage's current browser output, returned as a PNG
- The workspace synced to the stage, so a change becomes what viewers see
- Any dazzle CLI command run, with the output returned as JSON
- A complete platform reference the agent can read before it starts building
The dazzle binary, from the install script, from go install github.com/dazzle-labs/cli/cmd/dazzle@latest, or from the release binaries for macOS, Linux and Windows. Then dazzle mcp as the command in your client. The server starts without credentials; the agent signs in through the CLI tool, which opens a browser.
One command — curl -sSL https://dazzle.fm/install.sh | sh