Dazzle

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

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

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 thereleases page.

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 live

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

The MCP server starts without credentials — agents can callguideto learn the platform andcli ["login"]to authenticate.

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 usedazzle stage syncdirectly for the full experience.

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).

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).

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).

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.

For stage-scoped commands, the stage is resolved in this order:
- -s/--stageflag orDAZZLE_STAGEenvironment variable
- Auto-select if you have exactly one stage

dazzle stage sync ./app --stage my-stage # explicit export DAZZLE_STAGE=my-stage # or set for your session

Environment variables(override config files and stored credentials):

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

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

- API key stored at~/.config/dazzle/credentials.jsonwith0600permissions
- Transmitted asBearertoken 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

Navigate your Aiven projects and interact with the PostgreSQL®, Apache Kafka®, ClickHouse® and OpenSearch® services

Yunxiao MCP Server provides AI assistants with the ability to interact with the Yunxiao platform.

Get prescriptive CDK advice, explain CDK Nag rules, check suppressions, generate Bedrock Agent schemas, and discover AWS Solutions Constructs patterns.

This AWS Labs Model Context Protocol (MCP) server for CloudTrail enables your AI agents to query AWS account activity for security investigations, compliance auditing, and operational troubleshooting.

Core AWS MCP server providing prompt understanding and server management capabilities.

Analyze CDK projects to identify AWS services used and get pricing information from AWS pricing webpages and API.

Query and analyze your Axiom logs, traces, and all other event data in natural language

Manage and interact with Microsoft Azure services.

Bastion: External Attack Surface Monitoring

Ask your AI assistant about your attack surface: run scans, catch expiring certificates and domains, triage findings, and generate reports.

Agent-ready global image CDN that AI agents can install and operate through MCP.