Dazzle MCP Server

What the code does

We read the source, 6 d ago · rules 995398eba69f

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

    return filepath.Join(home, dazzleConfigDirName), nil

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add dazzle -- npx -y @dazzle-labs/cli

{
  "mcpServers": {
    "dazzle": {
      "command": "npx",
      "args": [
        "-y",
        "@dazzle-labs/cli"
      ]
    }
  }
}

[mcp_servers.dazzle]
command = "npx"
args = ["-y", "@dazzle-labs/cli"]

{
  "mcpServers": {
    "dazzle": {
      "command": "npx",
      "args": [
        "-y",
        "@dazzle-labs/cli"
      ]
    }
  }
}

{
  "servers": {
    "dazzle": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@dazzle-labs/cli"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: DAZZLE_STAGE (Pin to a specific stage name or ID. If omitted, auto-selects when you have one stage), DAZZLE_API_KEY (API key for headless/CI use. Alternative to interactive login).