Cloud stages for AI agents and live streaming. Create, manage, and broadcast content.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"dazzle": {
"args": [
"mcp"
],
"command": "dazzle"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
The official CLI and MCP server for Dazzle — cloud stages for AI agents and live streaming.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in entertainment
The official MCP Server for the Mux API
MCP Server for Text to Speech
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to control Unreal E…
Unity MCP Server — 268 tools for AI-assisted game development. Connect Claude, Cursor, or any MCP client to Unity Editor & Unity Hub. Scene management, GameObjects, components, builds, profiling, Shader Graph, Amplify, terrain, physics, NavMesh, animation, MPPM multiplayer & more. Free & open source by AnkleBreaker Studio.
MCP Security Weekly
Get CVE alerts and security updates for io.github.dazzle-labs/dazzle and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
The official CLI and MCP server for Dazzle — cloud stages for AI agents and live streaming.
One binary, two interfaces:
dazzle mcp) — stdio integration for sandboxed clients (Claude Desktop, VS Code, any MCP host)
curl -sSL https://dazzle.fm/install.sh | sh
irm https://dazzle.fm/install.ps1 | iex
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.
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
Add to your MCP client config:
{
"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.
| Tool | Description |
|---|---|
cli | Run a dazzle CLI command. Use ["--help"] to discover available commands. Output is JSON. |
edit_file | Edit 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. |
guide | Get the complete Dazzle reference — getting started, CLI commands, content capabilities, and streaming setup. Read this before creating or modifying stage content. |
list_files | List all files in the stage workspace (~/.dazzle/stages/{stage}/). Returns relative paths, one per line. |
read_file | Read a file from the stage workspace (~/.dazzle/stages/{stage}/{path}). |
screenshot | Capture a screenshot of the stage's current browser output. Returns a PNG image. |
sync | Sync 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_file | Write 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. |
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.
| URI | Description |
|---|---|
https://dazzle.fm/llms-full.txt | Complete Dazzle reference — getting started, CLI help, and content authoring guide. |
https://dazzle.fm/llms.txt | Dazzle quick-start guide — platform overview, setup, CLI basics, and doc links. |
| CLI | MCP | |
|---|---|---|
| Best for | Coding agents, terminals, C |