cliLABSCO SUMMARY
An agent can build a stage, see it, and go live with it.
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.
What it is
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.
What you get
- 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
Requirements
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.
Setup effort
One command — curl -sSL https://dazzle.fm/install.sh | sh
USE CASES
01
Building a stream overlay by describing it
The agent lists the workspace, reads what is there, writes the new files and syncs. Because the stage is browser-rendered, the thing it is editing is ordinary web content.
02
Fixing something that looks wrong on air
Read the file, make the exact-string edit, sync, then take a screenshot and look. The screenshot is what turns a guess into a check.
03
Bringing an agent up to speed on the platform
The reference tool returns getting-started, CLI commands, content capabilities and streaming setup in one call, which is what the agent should read before it creates anything rather than after it gets it wrong.
04
Getting from a stage to a live stream
Creating the stage, activating it, adding an RTMP or Twitch destination and attaching it are all CLI commands, and the CLI is a tool, so the whole sequence runs from the assistant.
8 tools
Listed in project docs. Your client may show a different list.
edit_fileguidelist_filesread_filescreenshotsyncwrite_fileBEFORE YOU INSTALL
What to know first
Tools you get
8 tools named in the project's documentation.
Requires
dazzle on PATH
Where it runs
All 3 documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
curl -sSL https://dazzle.fm/install.sh | shMCP Clients
Claude Desktop, Other MCP clients
JSON
{
"mcpServers": {
"dazzle": {
"command": "dazzle",
"args": [
"mcp"
]
}
}
}VS Code
VS CODE · JSON
{
"servers": {
"dazzle": {
"command": "dazzle",
"args": [
"mcp"
]
}
}
}
