Dazzle

Name: Dazzle
Author: dazzle-labs

by dazzle-labsversion 0.7.1i★ –iRuns on your computer

Registry nameio.github.dazzle-labs/dazzle

Install

Overview

Description from the maker (original English)

Cloud stages for AI agents and live streaming. Create, manage, and broadcast content.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other
You need to fill in: DAZZLE_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: DAZZLE_STAGE, DAZZLE_API_KEY

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "dazzle": {
      "command": "npx",
      "args": [
        "-y",
        "@dazzle-labs/cli",
        "mcp"
      ],
      "env": {
        "DAZZLE_STAGE": "your-value",
        "DAZZLE_API_KEY": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add dazzle --env DAZZLE_STAGE=your-value --env DAZZLE_API_KEY=your-value -- npx -y @dazzle-labs/cli mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "dazzle": {
      "command": "npx",
      "args": [
        "-y",
        "@dazzle-labs/cli",
        "mcp"
      ],
      "env": {
        "DAZZLE_STAGE": "your-value",
        "DAZZLE_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "dazzle": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@dazzle-labs/cli",
        "mcp"
      ],
      "env": {
        "DAZZLE_STAGE": "your-value",
        "DAZZLE_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

DAZZLE_STAGE env
Pin to a specific stage name or ID. If omitted, auto-selects when you have one stage.
DAZZLE_API_KEY secret env
API key for headless/CI use. Alternative to interactive login.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account dazzle-labs, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32686 servers in this category
Published to the registry more recently than 6% of the other 32686 servers in this category
Basic checks equal to or better than 100% of the other 32686 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Dazzle safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: DAZZLE_API_KEY

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.7.1) reached the registry 7 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Verbaly

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago

Install

Verbaly

by AronSoto

i18n for coding agents: extract, check and translate an app's text, with drafts a person approves

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

dazzle

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

One binary, two interfaces:

CLI — full shell access for coding agents (Claude Code, Cursor, terminals) and automation
MCP server (dazzle mcp) — stdio integration for sandboxed clients (Claude Desktop, VS Code, any MCP host)

Installation

macOS / Linux

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

Windows (PowerShell)

irm https://dazzle.fm/install.ps1 | iex

Other options

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.

Quick Start (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 live

Quick Start (MCP)

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.

MCP Tools

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.

Workspace tools

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.

MCP Resources

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 vs MCP — which to use?

	CLI	MCP
Best for	Coding agents, terminals, CI/CD	Claude Desktop, VS Code, sandboxed clients
Filesystem	Full access — write anywhere, run build tools	Workspace only (`~/.dazzle/stages/{id}/`)
Shell	Yes — npm, tailwind, any toolchain	No — pre-built content only
Content sync	`dazzle stage sync ./dir`	`write_file` + `sync`
Screenshot	`dazzle stage screenshot -o file.png`	`screenshot` tool (returns JPEG)
Auth	`dazzle login` or `DAZZLE_API_KEY`	`cli ["login"]` via MCP

CLI Reference

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:

dazzle login # authenticate (one-time)
dazzle s new my-stage # create a stage
dazzle s up # bring it up — starts streaming to Dazzle
dazzle s sync ./my-app -w # sync + auto-refresh on changes
dazzle s ss -o preview.png # take a screenshot to verify
dazzle s down # stop streaming and shut down

Auth: dazzle login, or set DAZZLE_API_KEY for headless/CI use. Stage selection: use -s , 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 --help" for more information on a command.

Stage subcommands

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: 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` subcommands

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, --hel

Only the beginning is shown; read the rest in the repo

Dazzle

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Verbaly

README from the maker

dazzle

Installation

macOS / Linux

Windows (PowerShell)

Other options

Quick Start (CLI)

Quick Start (MCP)

MCP Tools

Workspace tools

MCP Resources

CLI vs MCP — which to use?

CLI Reference

stage sync flags

stage screenshot flags

stage event subcommands

`stage sync` flags

`stage screenshot` flags

`stage event` subcommands