Developer · Local MCP server
Dazzle
Cloud stages for AI agents and live streaming. Create, manage, and broadcast content.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.dazzle-labs/dazzle- Version
- 0.7.1
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-04-04
- Updated
- 2026-04-04
- Publisher
- dazzle-labs (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/dazzle-labs) · how
- Website
- dazzle.fm
- Repository
- github.com/dazzle-labs/cli
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | @dazzle-labs/cli | 0.7.1 | stdio |
How to connect Dazzle
Dazzle runs locally from a Node.js package published to the npm registry: @dazzle-labs/cli version 0.7.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @dazzle-labs/cli@0.7.1. It reads these environment variables: DAZZLE_STAGE and DAZZLE_API_KEY (secret); set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"dazzle": {
"command": "npx",
"args": [
"-y",
"@dazzle-labs/cli@0.7.1"
],
"env": {
"DAZZLE_STAGE": "<value>",
"DAZZLE_API_KEY": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Datenschutz Auskunft Lint15 Prüfungen für Auskunftsschreiben nach Art. 15 DSGVO - samt Monatsfrist ab Eingangsdatum. | Local · stdio |
| Dates-LEExtract dates and timestamps from logs, data files and code, with their format and position. | Local · stdio |
| Datoka HooksPublic webhook relay with signed observations, retries and verified receivers. Self-service beta. | Remote · HTTPLive check: ✓ handshake |
| datoonStructured-data to TOON gateway: converts to TOON only when it saves LLM tokens. | Local · stdio |
| Db Access MCPMCP server for Postgres/MySQL/Redshift/SQL Server over SSH/SSM tunnels with secret providers. | Local · stdio |
| Db Conn MCPA dead-simple, self-hosted MCP server for securely querying databases via AI agents. | Local · stdio |
| DB Connect MCPMulti-database MCP server for PostgreSQL, MySQL, and ClickHouse. | Local · stdio |
| Db GatewayKVKK/GDPR-compliant LLM-to-database gateway: PII masking, RBAC, rate limiting, audit log. | Local · stdio |