dazzle
dazzle
Das offizielle CLI und der MCP-Server für Dazzle – Cloud-Bühnen für KI-Agenten und Live-Streaming.
Ein Binary, zwei Schnittstellen:
CLI – vollständiger Shell-Zugriff für Coding-Agenten (Claude Code, Cursor, Terminals) und Automatisierung
MCP-Server (
dazzle mcp) – stdio-Integration für sandboxed Clients (Claude Desktop, VS Code, jeder MCP-Host)
Installation
macOS / Linux
curl -sSL https://dazzle.fm/install.sh | shWindows (PowerShell)
irm https://dazzle.fm/install.ps1 | iexWeitere Optionen
go install github.com/dazzle-labs/cli/cmd/dazzle@latestVorkompilierte Binaries für macOS (arm64/amd64), Linux (amd64/arm64) und Windows (amd64/arm64) finden Sie auf der Releases-Seite.
Related MCP server: browser-gateway
Schnellstart (CLI)
dazzle login # authenticate (opens browser)
dazzle stage create my-stage # create a stage
dazzle stage up # activate — starts streaming
dazzle stage sync ./my-app --watch # push content, auto-refresh on changes
dazzle stage screenshot -o preview.png # verify output
dazzle destination add # add Twitch/Kick/custom RTMP
dazzle destination attach my-destination # go liveSchnellstart (MCP)
Fügen Sie dies Ihrer MCP-Client-Konfiguration hinzu:
{
"mcpServers": {
"dazzle": {
"command": "dazzle",
"args": ["mcp"]
}
}
}Der MCP-Server startet ohne Anmeldedaten – Agenten können guide aufrufen, um die Plattform kennenzulernen, und cli ["login"], um sich zu authentifizieren.
MCP-Tools
Tool | Beschreibung |
| Führt einen Dazzle CLI-Befehl aus. Verwenden Sie ["--help"], um verfügbare Befehle zu entdecken. Die Ausgabe erfolgt als JSON. |
| Bearbeitet eine Datei im Bühnen-Arbeitsbereich durch exakten String-Austausch. Der old_string muss exakt einmal in der Datei vorkommen. Verwenden Sie zuerst read_file, um den aktuellen Inhalt zu sehen. |
| Ruft die vollständige Dazzle-Referenz ab – erste Schritte, CLI-Befehle, Inhaltsfunktionen und Streaming-Einrichtung. Lesen Sie dies, bevor Sie Bühneninhalte erstellen oder ändern. |
| Listet alle Dateien im Bühnen-Arbeitsbereich auf (~/.dazzle/stages/{stage}/). Gibt relative Pfade zurück, einen pro Zeile. |
| Liest eine Datei aus dem Bühnen-Arbeitsbereich (~/.dazzle/stages/{stage}/{path}). |
| Erstellt einen Screenshot der aktuellen Browser-Ausgabe der Bühne. Gibt ein PNG-Bild zurück. |
| Synchronisiert den Bühnen-Arbeitsbereich (~/.dazzle/stages/{stage}/) mit der Live-Bühne. Führen Sie dies nach dem Schreiben von Dateien aus, um Inhalte zu übertragen. Entspricht 'dazzle stage sync {workspace-dir}'. |
| Schreibt eine Datei in den Bühnen-Arbeitsbereich (~/.dazzle/stages/{stage}/{path}). Erstellt bei Bedarf übergeordnete Verzeichnisse. Verwenden Sie dies, um Inhalte aufzubauen, die dann mit der Bühne synchronisiert werden können. |
Arbeitsbereich-Tools
Die Arbeitsbereich-Tools (write_file, read_file, edit_file, list_files, sync) speichern Dateien im Verzeichnis ~/.dazzle/stages/{stage-id}/ auf dem Host-Dateisystem. Dies überbrückt sandboxed Umgebungen (z. B. Claude Desktop), in denen die Bash des Agenten in einem isolierten Container läuft und keine Dateien mit dem CLI-Prozess teilen kann.
Workflow: write_file → edit_file (iterieren) → sync → screenshot (überprüfen)
Einschränkungen: Keine Shell/Exec – Build-Tools (npm, tailwind, etc.) können nicht im Arbeitsbereich ausgeführt werden. Inhalte müssen als fertiges HTML/CSS/JS vorliegen. Agenten mit vollem Dateisystem- und Shell-Zugriff (z. B. Claude Code) sollten für das volle Erlebnis direkt dazzle stage sync verwenden.
MCP-Ressourcen
URI | Beschreibung |
| Vollständige Dazzle-Referenz – erste Schritte, CLI-Hilfe und Leitfaden zur Inhaltserstellung. |
| Dazzle-Schnellstartanleitung – Plattformübersicht, Einrichtung, CLI-Grundlagen und Dokumentationslinks. |
CLI vs. MCP – was sollte man verwenden?
CLI | MCP | |
Am besten für | Coding-Agenten, Terminals, CI/CD | Claude Desktop, VS Code, sandboxed Clients |
Dateisystem | Voller Zugriff – überall schreiben, Build-Tools ausführen | Nur Arbeitsbereich ( |
Shell | Ja – npm, tailwind, jede Toolchain | Nein – nur fertige Inhalte |
Inhaltssynchronisierung |
|
|
Screenshot |
|
|
Authentifizierung |
|
|
CLI-Referenz
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 in
the 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 stage
restarts — 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.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 Unterbefehle
Usage: dazzle stage (s) event (ev) <command>
Send real-time data to the running page without reloading. Events are dispatched
as DOM CustomEvents — use this for async updates from subagents, APIs, or other
processes.
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.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.Bühnenauflösung
Für bühnenbezogene Befehle wird die Bühne in dieser Reihenfolge aufgelöst:
-s/--stageFlag oderDAZZLE_STAGEUmgebungsvariableAutomatische Auswahl, wenn Sie genau eine Bühne haben
dazzle stage sync ./app --stage my-stage # explicit
export DAZZLE_STAGE=my-stage # or set for your sessionKonfiguration
Umgebungsvariablen (überschreiben Konfigurationsdateien und gespeicherte Anmeldedaten):
Variable | Zweck | Standardwert |
| API-Schlüssel – überspringt | gespeicherte Anmeldedaten |
| API-Basis-URL |
|
| Bühnenname oder ID | automatische Auswahl, falls nur eine vorhanden |
Konfigurationsdateien (~/.config/dazzle/, 0600 Berechtigungen):
config.json # { "api_url": "..." }
credentials.json # { "api_key": "dzl_...", "email": "..." }Sicherheit
API-Schlüssel wird unter
~/.config/dazzle/credentials.jsonmit0600Berechtigungen gespeichertÜbertragung ausschließlich als
Bearer-Token über HTTPSNiemals protokolliert, niemals ausgegeben, niemals an Dritte gesendet
Keine Telemetrie – keine Nutzungsdaten, Absturzberichte oder Analysen
Der gesamte Quellcode ist Open Source und überprüfbar
Lizenz
Apache 2.0 – siehe LICENSE
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
No tool schema history has been recorded yet.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
- sleipnirOAuthtv.sleipnir
Multistream to Twitch, YouTube and Kick; generate OBS overlays from a plain-English prompt.
- openhelmOAuthai.openhelm
Autonomous cloud agent tasks: real browser + your tools, structured evidence-backed results.
Hosted browser for AI agents: screenshots, post-JS DOM, console, WCAG. No install, no API key.
61Clip Twitch, YouTube and Kick VODs, rank moments by viral score and schedule posts.
1
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceRemote browser instances for your AI agents. Reliably complete any browser-based task at scale. Fully-control agentic browsers that spin up in seconds.1540Apache 2.0
- AlicenseNot gradedqualityAmaintenanceReliable, scalable browser infrastructure for AI agents. Route, pool, and failover across any browser provider. 8 built-in browser tools using raw Chrome CDP - navigate, screenshot, snapshot, interact, evaluate. Zero-config with auto Chrome detection & concurrent sessions support7999MIT
- FlicenseAqualityDmaintenanceEnables AI agents to control a neko virtual browser via WebSocket and REST APIs, while allowing live viewing through a WebRTC stream.13-

HumanBrowserofficial
AlicenseNot gradedqualityCmaintenanceCloud Chromium for AI agents — stealth, residential proxies, captcha solving, A2A 1.0 endpoint. The MCP server lets Claude Desktop, Cursor, and Cline drive a real browser via three tools (humanbrowser_run, humanbrowser_stream, humanbrowser_viewer_url).21Apache 2.0
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/dazzle-labs/cli'
If you have feedback or need assistance with the MCP directory API, please join our Discord server