Helmdeck MCP Server

What the code does

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

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

        "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 -e 'HELMDECK_URL=<HELMDECK_URL>' -e 'HELMDECK_TOKEN=<HELMDECK_TOKEN>' -- npx -y @helmdeck/mcp-bridge

{
  "mcpServers": {
    "helmdeck": {
      "command": "npx",
      "args": [
        "-y",
        "@helmdeck/mcp-bridge"
      ],
      "env": {
        "HELMDECK_TOKEN": "<HELMDECK_TOKEN>",
        "HELMDECK_URL": "<HELMDECK_URL>"
      }
    }
  }
}

[mcp_servers.helmdeck]
command = "npx"
args = ["-y", "@helmdeck/mcp-bridge"]
env = { HELMDECK_URL = "<HELMDECK_URL>", HELMDECK_TOKEN = "<HELMDECK_TOKEN>" }

{
  "mcpServers": {
    "helmdeck": {
      "command": "npx",
      "args": [
        "-y",
        "@helmdeck/mcp-bridge"
      ],
      "env": {
        "HELMDECK_TOKEN": "<HELMDECK_TOKEN>",
        "HELMDECK_URL": "<HELMDECK_URL>"
      }
    }
  }
}

{
  "servers": {
    "helmdeck": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@helmdeck/mcp-bridge"
      ],
      "env": {
        "HELMDECK_TOKEN": "<HELMDECK_TOKEN>",
        "HELMDECK_URL": "<HELMDECK_URL>"
      }
    }
  }
}

Put your own values in place of <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’s registry entry marks them as required.