Dazzle
Create and manage Dazzle cloud stages so AI agents can produce and broadcast live streaming content without building infra from scratch.
Overview
io.github.dazzle-labs/dazzle is a MCP server for the Launch phase that lets agents create and manage Dazzle cloud stages and broadcast live streaming content.
What is this MCP server?
- Dazzle MCP via npx @dazzle-labs/cli mcp (package v0.7.1)
- Cloud stages for AI agents plus live streaming create/manage/broadcast flows
- DAZZLE_STAGE pins a stage name or ID; DAZZLE_API_KEY supports headless or CI login
- Website dazzle.fm; CLI repository dazzle-labs/cli
- Server schema version 0.7.1
- npm identifier @dazzle-labs/cli with positional argument mcp
- Transport: stdio; runtime hint npx
Community signal: 1 GitHub stars.
What problem does it solve?
Standing up reliable live stages and streams for an AI-led launch is heavy ops work when you are one person also building the product.
Who is it for?
Solo creators and agent builders who want managed cloud stages and live streaming wired into Claude Code or Cursor for launch events and recurring shows.
Skip if: Teams that only need static SEO landing pages or in-app analytics with no live broadcast component.
What do I get? / Deliverables
After MCP registration and auth, your agent can drive Dazzle stages and broadcasts so you ship audience-facing live distribution without custom streaming infrastructure.
- Agent-managed Dazzle stages for live content
- Broadcast workflows without self-built streaming stack
- Repeatable launch-time distribution channel for shows and demos
Recommended MCP Servers
Journey fit
Launch is where you put the product in front of an audience; Dazzle’s stages and broadcasting focus on distribution surfaces rather than core app coding. Distribution covers channels and go-live mechanics—live stages and streams are explicit audience-facing launch tactics for builders promoting agents or shows.
How it compares
Managed live-stage and streaming MCP—not a local Git or GitHub developer tool.
Common Questions / FAQ
Who is io.github.dazzle-labs/dazzle for?
Builders and creators running AI agents or live formats who want Dazzle’s cloud stages and streaming controlled from an MCP-capable coding agent.
When should I use io.github.dazzle-labs/dazzle?
Use it at Launch when you are going live, rehearsing streams, or automating broadcast workflows on Dazzle rather than self-hosting media infra.
How do I add io.github.dazzle-labs/dazzle to my agent?
Run the MCP server through npx @dazzle-labs/cli mcp over stdio, complete interactive login or set DAZZLE_API_KEY, optionally set DAZZLE_STAGE, then add the server to your MCP client config.