Bmc Helix MCP Server

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 bmc-helix-mcp -- npx -y bmc-helix-mcp

{
  "mcpServers": {
    "bmc-helix-mcp": {
      "args": [
        "-y",
        "bmc-helix-mcp"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.bmc-helix-mcp]
command = "npx"
args = ["-y", "bmc-helix-mcp"]

{
  "mcpServers": {
    "bmc-helix-mcp": {
      "args": [
        "-y",
        "bmc-helix-mcp"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "bmc-helix-mcp": {
      "args": [
        "-y",
        "bmc-helix-mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: HELIX_API_URL (BMC Helix Entry level REST API URL endpoint.), HELIX_TOKEN_URL (BMC Helix JWT Login endpoint URL.), HELIX_USERID (BMC Helix API Username/UserID.), HELIX_PASSWORD (BMC Helix API User Password.), HELIX_CERT_PATH (Path to the retrieved BMC Helix TLS certificate chain.), MCP_PORT (The port number on which the MCP Server should run.), MCP_AUTH_TOKEN (Optional Bearer token to secure the MCP Server communication.), MCP_TLS_ENABLED (Set to true to run the MCP Server with secure TLS (HTTPS).), MCP_TLS_KEY (Path to the TLS private key file.), MCP_TLS_CERT (Path to the TLS certificate file.), MCP_TLS_CA (Path to the TLS Certificate Authority (CA) file.). The author declared them in the registry entry; get the values from the project itself.