Dazzle

io.github.dazzle-labs由 GitHub 帳號 dazzle-labs 發布v0.7.1更新於 Oct 24, 2026

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

已驗證STDIO僅桌面檔案與儲存開發者工具媒體與設計

概覽

AI 產生的概覽

Dazzle 的本機 MCP 伺服器讓 AI 助理在雲端舞台工作區中建置內容、同步到即時瀏覽器舞台、截圖，並管理直播。

可以做什麼
透過單一工具執行 Dazzle CLI 指令，包括登入、舞台與串流目的地管理以及說明查詢，輸出為 JSON。在撰寫內容前閱讀平台指南。以精確字串取代方式列出、讀取、寫入和編輯舞台工作區中的檔案。將工作區同步到即時舞台，並擷取舞台瀏覽器輸出的 PNG 截圖。讀取內建的 Dazzle 參考資源。
適用情境
適用於 Claude Desktop、VS Code 等沙箱式 MCP 用戶端，讓助理撰寫預先建置的 HTML/CSS/JS 內容、推送到 Dazzle 雲端舞台、進行視覺驗證並管理直播串流目的地。擁有完整 shell 與檔案系統存取權限的代理則建議改用 CLI。
執行需求
透過 npx 從 npm 套件 @dazzle-labs/cli 以 stdio 在本機執行，僅限桌面端。驗證方式為透過 cli 工具互動式登入，或使用 DAZZLE_API_KEY 環境變數進行無頭使用。DAZZLE_STAGE 可選擇固定某個舞台，否則在只有一個舞台時自動選取。需要連線至 Dazzle 服務的網路存取。
安裝前請注意
cli 工具可執行任意 Dazzle 指令，包括建立和刪除舞台、啟動或停止串流、傳送直播聊天訊息以及新增或移除串流目的地。DAZZLE_API_KEY 密鑰儲存在憑證檔案中並以 Bearer 權杖傳送。工作區檔案寫入使用者家目錄下。工作區中不提供 shell 或建置工具。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Dazzle，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only，透過 STDIO。 STDIO 服務會啟動本機處理程序，因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

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)

[Dazzle CLI demo]

Installation

macOS / Linux

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

Windows (PowerShell)

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

Other options

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

bash
dazzle login                              # authenticate (opens browser)dazzle stage create my-stage              # create a stagedazzle stage up                           # activate — starts streamingdazzle stage sync ./my-app --watch        # push content, auto-refresh on changesdazzle stage screenshot -o preview.png    # verify outputdazzle destination add                    # add Twitch/Kick/custom RTMPdazzle destination attach my-destination  # go live

Quick Start (MCP)

Add to your MCP client config:

json
{  "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

ToolDescription
cliRun a dazzle CLI command. Use ["--help"] to discover available commands. Output is JSON.
edit_fileEdit 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.
guideGet the complete Dazzle reference — getting started, CLI commands, content capabilities, and streaming setup. Read this before creating or modifying stage content.
list_filesList all files in the stage workspace (~/.dazzle/stages/{stage}/). Returns relative paths, one per line.
read_fileRead a file from the stage workspace (~/.dazzle/stages/{stage}/{path}).
screenshotCapture a screenshot of the stage's current browser output. Returns a PNG image.
syncSync 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_fileWrite 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

URIDescription
https://dazzle.fm/llms-full.txtComplete Dazzle reference — getting started, CLI help, and content authoring guide.
https://dazzle.fm/llms.txtDazzle quick-start guide — platform overview, setup, CLI basics, and doc links.

CLI vs MCP — which to use?

CLIMCP
Best forCoding agents, terminals, CI/CDClaude Desktop, VS Code, sandboxed clients
FilesystemFull access — write anywhere, run build toolsWorkspace only (~/.dazzle/stages/{id}/)
ShellYes — npm, tailwind, any toolchainNo — pre-built content only
Content syncdazzle stage sync ./dirwrite_file + sync
Screenshotdazzle stage screenshot -o file.pngscreenshot tool (returns JPEG)
Authdazzle login or DAZZLE_API_KEYcli ["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 inthe 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 stagerestarts — 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.
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:  <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).
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 dispatchedas DOM CustomEvents — use this for async updates from subagents, APIs, or otherprocesses.
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.
Destination subcommands 
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.

Stage Resolution

For stage-scoped commands, the stage is resolved in this order:

  1. -s / --stage flag or DAZZLE_STAGE environment variable
  2. Auto-select if you have exactly one stage
bash
dazzle stage sync ./app --stage my-stage   # explicitexport DAZZLE_STAGE=my-stage               # or set for your session

Configuration

Environment variables (override config files and stored credentials):

VariablePurposeDefault
DAZZLE_API_KEYAPI key — skip dazzle login for CI, scripting, one-off commandsstored credentials
DAZZLE_API_URLAPI base URLhttps://dazzle.fm
DAZZLE_STAGEStage name or IDauto-selects if only one

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

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

Security

  • API key stored at ~/.config/dazzle/credentials.json with 0600 permissions
  • Transmitted as Bearer token 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

License

Apache 2.0 — see LICENSE

來源：README.md，提交 2e80d16

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包，因此其工具未知。

版本歷史

1
  1. v0.7.1最新Sep 16, 2026

評分

已滿足適用檢查項的 40%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手；SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭，或保持端點能夠回應探測，以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list，或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

    請在儲存庫或註冊中心條目中宣告授權條款。