Helmdeck MCP Server

What the code does

We read the source, 1 h ago · rules 3dff92dd89df

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

postinstall: node scripts/postinstall.js

const result = spawnSync(binPath, process.argv.slice(2), { stdio: "inherit" });

const binPath = path.join(__dirname, binName);

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.

        "trap 'shred -u \"$KEY_DIR\"/id_rsa 2>/dev/null || rm -f \"$KEY_DIR\"/id_rsa; rmdir \"$KEY_DIR\" 2>/dev/null || true' EXIT",

      - /var/run/docker.sock:/var/run/docker.sock

        "trap 'shred -u \"$KEY_DIR\"/id_rsa 2>/dev/null || rm -f \"$KEY_DIR\"/id_rsa; rmdir \"$KEY_DIR\" 2>/dev/null || true' EXIT",

        "trap 'shred -u \"$KEY_DIR\"/id_rsa 2>/dev/null || rm -f \"$KEY_DIR\"/id_rsa; rmdir \"$KEY_DIR\" 2>/dev/null || true' EXIT",

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 helmdeck -- npx -y @helmdeck/mcp-bridge

{
  "mcpServers": {
    "helmdeck": {
      "args": [
        "-y",
        "@helmdeck/mcp-bridge"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.helmdeck]
command = "npx"
args = ["-y", "@helmdeck/mcp-bridge"]

{
  "mcpServers": {
    "helmdeck": {
      "args": [
        "-y",
        "@helmdeck/mcp-bridge"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "helmdeck": {
      "args": [
        "-y",
        "@helmdeck/mcp-bridge"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: HELMDECK_URL (Base URL of your helmdeck control plane (e.g. http://localhost:3000 for a local Compose install, or your reverse-proxied https URL)), HELMDECK_TOKEN (JWT bearer token minted from your helmdeck control plane. Generate with: curl -X POST $HELMDECK_URL/api/v1/auth/login -d '{"username":"admin","password":"..."}'). The author declared them in the registry entry; get the values from the project itself.