dazzle
dazzle
La CLI oficial y el servidor MCP para Dazzle: escenarios en la nube para agentes de IA y transmisión en vivo.
Un binario, dos interfaces:
CLI: acceso completo al shell para agentes de codificación (Claude Code, Cursor, terminales) y automatización.
Servidor MCP (
dazzle mcp): integración stdio para clientes en sandbox (Claude Desktop, VS Code, cualquier host MCP).
Instalación
macOS / Linux
curl -sSL https://dazzle.fm/install.sh | shWindows (PowerShell)
irm https://dazzle.fm/install.ps1 | iexOtras opciones
go install github.com/dazzle-labs/cli/cmd/dazzle@latestLos binarios precompilados para macOS (arm64/amd64), Linux (amd64/arm64) y Windows (amd64/arm64) se encuentran en la página de lanzamientos.
Related MCP server: browser-gateway
Inicio rápido (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 liveInicio rápido (MCP)
Añade esto a la configuración de tu cliente MCP:
{
"mcpServers": {
"dazzle": {
"command": "dazzle",
"args": ["mcp"]
}
}
}El servidor MCP se inicia sin credenciales; los agentes pueden ejecutar guide para conocer la plataforma y cli ["login"] para autenticarse.
Herramientas MCP
Herramienta | Descripción |
| Ejecuta un comando de la CLI de dazzle. Usa ["--help"] para descubrir los comandos disponibles. La salida es JSON. |
| Edita un archivo en el espacio de trabajo del escenario mediante el reemplazo exacto de cadenas. La old_string debe coincidir exactamente una vez en el archivo. Usa read_file primero para ver el contenido actual. |
| Obtén la referencia completa de Dazzle: cómo empezar, comandos de CLI, capacidades de contenido y configuración de transmisión. Lee esto antes de crear o modificar el contenido del escenario. |
| Lista todos los archivos en el espacio de trabajo del escenario (~/.dazzle/stages/{stage}/). Devuelve rutas relativas, una por línea. |
| Lee un archivo del espacio de trabajo del escenario (~/.dazzle/stages/{stage}/{path}). |
| Captura una captura de pantalla de la salida actual del navegador del escenario. Devuelve una imagen PNG. |
| Sincroniza el espacio de trabajo del escenario (~/.dazzle/stages/{stage}/) con el escenario en vivo. Ejecuta esto después de escribir archivos para publicar el contenido. Equivalente a 'dazzle stage sync {workspace-dir}'. |
| Escribe un archivo en el espacio de trabajo del escenario (~/.dazzle/stages/{stage}/{path}). Crea los directorios principales según sea necesario. Úsalo para crear contenido que luego pueda sincronizarse con el escenario. |
Herramientas de espacio de trabajo
Las herramientas de espacio de trabajo (write_file, read_file, edit_file, list_files, sync) almacenan archivos en ~/.dazzle/stages/{stage-id}/ en el sistema de archivos del host. Esto sirve de puente para entornos en sandbox (p. ej., Claude Desktop) donde el bash del agente se ejecuta en un contenedor aislado y no puede compartir archivos con el proceso de la CLI.
Flujo de trabajo: write_file → edit_file (iterar) → sync → screenshot (verificar)
Limitaciones: Sin shell/exec: no se pueden ejecutar herramientas de compilación (npm, tailwind, etc.) en el espacio de trabajo. El contenido debe ser HTML/CSS/JS precompilado. Los agentes con acceso completo al sistema de archivos y al shell (p. ej., Claude Code) deben usar dazzle stage sync directamente para obtener la experiencia completa.
Recursos MCP
URI | Descripción |
| Referencia completa de Dazzle: cómo empezar, ayuda de la CLI y guía de creación de contenido. |
| Guía de inicio rápido de Dazzle: descripción general de la plataforma, configuración, conceptos básicos de la CLI y enlaces a la documentación. |
CLI vs MCP: ¿cuál usar?
CLI | MCP | |
Ideal para | Agentes de codificación, terminales, CI/CD | Claude Desktop, VS Code, clientes en sandbox |
Sistema de archivos | Acceso completo: escribe en cualquier lugar, ejecuta herramientas de compilación | Solo espacio de trabajo ( |
Shell | Sí: npm, tailwind, cualquier cadena de herramientas | No: solo contenido precompilado |
Sincronización de contenido |
|
|
Captura de pantalla |
| Herramienta |
Autenticación |
|
|
Referencia de la CLI
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).Flags de stage sync
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).Flags de stage screenshot
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).Subcomandos de stage event
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.Resolución de stage
Para los comandos con ámbito de stage, el stage se resuelve en este orden:
Flag
-s/--stageo variable de entornoDAZZLE_STAGESelección automática si tienes exactamente un stage
dazzle stage sync ./app --stage my-stage # explicit
export DAZZLE_STAGE=my-stage # or set for your sessionConfiguración
Variables de entorno (anulan los archivos de configuración y las credenciales almacenadas):
Variable | Propósito | Predeterminado |
| Clave de API: omite | credenciales almacenadas |
| URL base de la API |
|
| Nombre o ID del stage | selección automática si solo hay uno |
Archivos de configuración (~/.config/dazzle/, permisos 0600):
config.json # { "api_url": "..." }
credentials.json # { "api_key": "dzl_...", "email": "..." }Seguridad
Clave de API almacenada en
~/.config/dazzle/credentials.jsoncon permisos0600Transmitida como token
Bearersolo a través de HTTPSNunca registrada, nunca mostrada, nunca enviada a terceros
Sin telemetría: sin datos de uso, informes de errores ni análisis
Todo el código fuente es de código abierto y auditable
Licencia
Apache 2.0: consulta 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