Dazzle

io.github.dazzle-labsPublished by GitHub account dazzle-labsv0.7.1Updated Oct 24, 2026

Cloud stages for AI agents and live streaming. Create, manage, and broadcast content.

VerifiedSTDIODesktop onlyFiles & StorageDeveloper ToolsMedia & Design

Overview

AI-generated overview

Dazzle's local MCP server lets an AI assistant build content in a cloud stage workspace, sync it to a live browser stage, screenshot it, and manage streaming.

What you can do
Run Dazzle CLI commands through a single tool, including login, stage and destination management, and help discovery, with JSON output. Read the platform guide before authoring content. List, read, write and edit files in the stage workspace by exact string replacement. Sync the workspace to the live stage and capture a PNG screenshot of the stage's browser output. Read the bundled Dazzle reference resources.
When to use it
Use it from sandboxed MCP clients such as Claude Desktop or VS Code when you want an assistant to author pre-built HTML/CSS/JS content, push it to a Dazzle cloud stage, verify it visually, and manage live streaming destinations. Agents with full shell and filesystem access are pointed to the CLI instead.
Requirements
Runs locally over stdio via npx from the npm package @dazzle-labs/cli, on desktop only. Authentication is either interactive login through the cli tool or the DAZZLE_API_KEY environment variable for headless use. DAZZLE_STAGE optionally pins a stage; otherwise a single stage is auto-selected. Network access to the Dazzle service is needed.
Before you install
The cli tool can run any Dazzle command, including creating and deleting stages, activating or stopping streaming, sending live chat messages, and adding or removing broadcast destinations. The DAZZLE_API_KEY secret is stored in a credentials file and sent as a Bearer token. Workspace files are written under the user's home directory. No shell or build tools are available in the workspace.

Installation

In SourceWeft

  1. Open Dazzle in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

dazzle

The official CLI and MCP server for Dazzle — cloud stages for AI agents and live streaming.

One binary, two interfaces:

  • CLI — full shell access for coding agents (Claude Code, Cursor, terminals) and automation
  • MCP server (dazzle mcp) — stdio integration for sandboxed clients (Claude Desktop, VS Code, any MCP host)

[Dazzle CLI demo]

Installation

macOS / Linux

bash
curl -sSL https://dazzle.fm/install.sh | sh

Windows (PowerShell)

powershell
irm https://dazzle.fm/install.ps1 | iex

Other options

bash
go install github.com/dazzle-labs/cli/cmd/dazzle@latest

Pre-built binaries for macOS (arm64/amd64), Linux (amd64/arm64), and Windows (amd64/arm64) are on the releases page.

Quick Start (CLI)

bash
dazzle login                              # authenticate (opens browser)dazzle stage create my-stage              # create a stagedazzle stage up                           # activate — starts streamingdazzle stage sync ./my-app --watch        # push content, auto-refresh on changesdazzle stage screenshot -o preview.png    # verify outputdazzle destination add                    # add Twitch/Kick/custom RTMPdazzle destination attach my-destination  # go live

Quick Start (MCP)

Add to your MCP client config:

json
{  "mcpServers": {    "dazzle": {      "command": "dazzle",      "args": ["mcp"]    }  }}

The MCP server starts without credentials — agents can call guide to learn the platform and cli ["login"] to authenticate.

MCP Tools

ToolDescription
cliRun a dazzle CLI command. Use ["--help"] to discover available commands. Output is JSON.
edit_fileEdit a file in the stage workspace by exact string replacement. The old_string must match exactly once in the file. Use read_file first to see the current content.
guideGet the complete Dazzle reference — getting started, CLI commands, content capabilities, and streaming setup. Read this before creating or modifying stage content.
list_filesList all files in the stage workspace (~/.dazzle/stages/{stage}/). Returns relative paths, one per line.
read_fileRead a file from the stage workspace (~/.dazzle/stages/{stage}/{path}).
screenshotCapture a screenshot of the stage's current browser output. Returns a PNG image.
syncSync the stage workspace (~/.dazzle/stages/{stage}/) to the live stage. Run this after writing files to push content. Equivalent to 'dazzle stage sync {workspace-dir}'.
write_fileWrite a file to the stage workspace (~/.dazzle/stages/{stage}/{path}). Creates parent directories as needed. Use this to build up content that can then be synced to the stage.

Workspace tools

The workspace tools (write_file, read_file, edit_file, list_files, sync) store files in ~/.dazzle/stages/{stage-id}/ on the host filesystem. This bridges sandboxed environments (e.g. Claude Desktop) where the agent's bash runs in an isolated container and can't share files with the CLI process.

Workflow: write_file → edit_file (iterate) → sync → screenshot (verify)

Limitations: No shell/exec — can't run build tools (npm, tailwind, etc.) in the workspace. Content must be pre-built HTML/CSS/JS. Agents with full filesystem and shell access (e.g. Claude Code) should use dazzle stage sync directly for the full experience.

MCP Resources

URIDescription
https://dazzle.fm/llms-full.txtComplete Dazzle reference — getting started, CLI help, and content authoring guide.
https://dazzle.fm/llms.txtDazzle quick-start guide — platform overview, setup, CLI basics, and doc links.

CLI vs MCP — which to use?

CLIMCP
Best forCoding agents, terminals, CI/CDClaude Desktop, VS Code, sandboxed clients
FilesystemFull access — write anywhere, run build toolsWorkspace only (~/.dazzle/stages/{id}/)
ShellYes — npm, tailwind, any toolchainNo — pre-built content only
Content syncdazzle stage sync ./dirwrite_file + sync
Screenshotdazzle stage screenshot -o file.pngscreenshot tool (returns JPEG)
Authdazzle login or DAZZLE_API_KEYcli ["login"] via MCP

CLI Reference

Usage: dazzle <command> [flags]
Dazzle — cloud stages for streaming.
A stage is a cloud browser environment that renders and streams your content.Sync a local directory (must contain an index.html) and everything visible inthe browser window is what gets streamed to viewers.
Your content runs in a real browser with full access to standard web APIs (DOM,Canvas, WebGL, Web Audio, fetch, etc.). localStorage is persisted across stagerestarts — use it to store app state that should survive between sessions.
Workflow: 1. dazzle login # authenticate (one-time) 2. dazzle s new my-stage # create a stage 3. dazzle s up # bring it up — starts streaming to Dazzle 4. dazzle s sync ./my-app -w # sync + auto-refresh on changes 5. dazzle s ss -o preview.png # take a screenshot to verify 6. dazzle s down # stop streaming and shut down
Auth: dazzle login, or set DAZZLE_API_KEY for headless/CI use. Stage selection:use -s <name>, DAZZLE_STAGE env, or auto-selected if only one.
https://dazzle.fm
Flags:  -h, --help              Show context-sensitive help.  -j, --json              Output as JSON.  -s, --stage=STRING      Stage name or ID ($DAZZLE_STAGE).      --api-url=STRING    API URL ($DAZZLE_API_URL).
Commands:  version                          Print version information.  update                           Update dazzle to the latest release.  guide                            Show content authoring guide (rendering tips,                                   performance, best practices).  login                            Authenticate with Dazzle (opens browser).  logout                           Clear stored credentials.  whoami                           Show current user.  stage (s) list (ls)              List stages.  stage (s) create (new)           Create a stage.  stage (s) delete (rm)            Delete a stage.  stage (s) up                     Activate a stage.  stage (s) down                   Deactivate a stage.  stage (s) status (st)            Show stage status.  stage (s) stats                  Show live pipeline stats.  stage (s) preview                Show the shareable preview URL for a running                                   stage.  stage (s) sync (sy)              Sync a local directory to the stage. This is                                   the primary way to push content — use --watch                                   for live development.  stage (s) refresh (r)            Reload the stage entry point.  stage (s) event (ev) emit (e)    Push a named event with JSON data to                                   the running page — dispatched as a DOM                                   CustomEvent. Use this to send real-time data                                   from external processes (other agents, APIs,                                   etc.) without re-syncing or reloading.  stage (s) logs (l)               Retrieve stage console logs.  stage (s) screenshot (ss)        Capture a screenshot of the stage.  stage (s) info                   Get current stream title and category.  stage (s) title                  Set the stream title (not supported for                                   Restream).  stage (s) category               Set the stream category or game (not                                   supported for Restream).  stage (s) chat send              Send a message to live chat (not supported                                   for Restream).  destination (dest) list (ls)     List broadcast destinations.  destination (dest) add (create,new)                                   Add a broadcast destination.  destination (dest) delete (rm)                                   Remove a broadcast destination.  destination (dest) attach (set)                                   Attach a destination to a stage.  destination (dest) detach (unset)                                   Detach a destination from a stage.
Run "dazzle <command> --help" for more information on a command.
Stage subcommands 
Usage: dazzle stage (s) <command> [flags]
Manage stages — create, sync content, screenshot, stream.
Flags:  -h, --help              Show context-sensitive help.  -j, --json              Output as JSON.  -s, --stage=STRING      Stage name or ID ($DAZZLE_STAGE).      --api-url=STRING    API URL ($DAZZLE_API_URL).
Commands:  stage (s) list (ls)              List stages.  stage (s) create (new)           Create a stage.  stage (s) delete (rm)            Delete a stage.  stage (s) up                     Activate a stage.  stage (s) down                   Deactivate a stage.  stage (s) status (st)            Show stage status.  stage (s) stats                  Show live pipeline stats.  stage (s) preview                Show the shareable preview URL for a running                                   stage.  stage (s) sync (sy)              Sync a local directory to the stage. This is                                   the primary way to push content — use --watch                                   for live development.  stage (s) refresh (r)            Reload the stage entry point.  stage (s) event (ev) emit (e)    Push a named event with JSON data to                                   the running page — dispatched as a DOM                                   CustomEvent. Use this to send real-time data                                   from external processes (other agents, APIs,                                   etc.) without re-syncing or reloading.  stage (s) logs (l)               Retrieve stage console logs.  stage (s) screenshot (ss)        Capture a screenshot of the stage.  stage (s) info                   Get current stream title and category.  stage (s) title                  Set the stream title (not supported for                                   Restream).  stage (s) category               Set the stream category or game (not                                   supported for Restream).  stage (s) chat send              Send a message to live chat (not supported                                   for Restream).
stage sync flags
Usage: dazzle stage (s) sync (sy) <dir> [flags]
Sync a local directory to the stage. This is the primary way to push content —use --watch for live development.
Arguments:  <dir>    Local directory to sync (must contain an index.html entry point).
Flags:  -h, --help                  Show context-sensitive help.  -j, --json                  Output as JSON.  -s, --stage=STRING          Stage name or ID ($DAZZLE_STAGE).      --api-url=STRING        API URL ($DAZZLE_API_URL).
  -w, --watch                 Watch for file changes and automatically re-sync.      --entry="index.html"    HTML entry point file (default: index.html).
stage screenshot flags
Usage: dazzle stage (s) screenshot (ss) [flags]
Capture a screenshot of the stage.
Flags:  -h, --help              Show context-sensitive help.  -j, --json              Output as JSON.  -s, --stage=STRING      Stage name or ID ($DAZZLE_STAGE).      --api-url=STRING    API URL ($DAZZLE_API_URL).
  -o, --out=STRING        Output file path (default: temp file).
stage event subcommands
Usage: dazzle stage (s) event (ev) <command>
Send real-time data to the running page without reloading. Events are dispatchedas DOM CustomEvents — use this for async updates from subagents, APIs, or otherprocesses.
Flags:  -h, --help              Show context-sensitive help.  -j, --json              Output as JSON.  -s, --stage=STRING      Stage name or ID ($DAZZLE_STAGE).      --api-url=STRING    API URL ($DAZZLE_API_URL).
Commands:  stage (s) event (ev) emit (e)    Push a named event with JSON data to                                   the running page — dispatched as a DOM                                   CustomEvent. Use this to send real-time data                                   from external processes (other agents, APIs,                                   etc.) without re-syncing or reloading.
Destination subcommands 
Usage: dazzle destination (dest) <command> [flags]
Manage broadcast destinations (Twitch, YouTube, etc).
Flags:  -h, --help              Show context-sensitive help.  -j, --json              Output as JSON.  -s, --stage=STRING      Stage name or ID ($DAZZLE_STAGE).      --api-url=STRING    API URL ($DAZZLE_API_URL).
Commands:  destination (dest) list (ls)    List broadcast destinations.  destination (dest) add (create,new)                                  Add a broadcast destination.  destination (dest) delete (rm)                                  Remove a broadcast destination.  destination (dest) attach (set)                                  Attach a destination to a stage.  destination (dest) detach (unset)                                  Detach a destination from a stage.

Stage Resolution

For stage-scoped commands, the stage is resolved in this order:

  1. -s / --stage flag or DAZZLE_STAGE environment variable
  2. Auto-select if you have exactly one stage
bash
dazzle stage sync ./app --stage my-stage   # explicitexport DAZZLE_STAGE=my-stage               # or set for your session

Configuration

Environment variables (override config files and stored credentials):

VariablePurposeDefault
DAZZLE_API_KEYAPI key — skip dazzle login for CI, scripting, one-off commandsstored credentials
DAZZLE_API_URLAPI base URLhttps://dazzle.fm
DAZZLE_STAGEStage name or IDauto-selects if only one

Config files (~/.config/dazzle/, 0600 permissions):

config.json        # { "api_url": "..." }credentials.json   # { "api_key": "dzl_...", "email": "..." }

Security

  • API key stored at ~/.config/dazzle/credentials.json with 0600 permissions
  • Transmitted as Bearer token over HTTPS only
  • Never logged, never echoed, never sent to third parties
  • No telemetry — no usage data, crash reports, or analytics
  • All source code is open source and auditable

License

Apache 2.0 — see LICENSE

Source: README.md at commit 2e80d16

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.7.1LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.