MCP 統合

Add governed tool execution to any MCP-compatible AI coding tool. One command generates the config — HELM intercepts every tool call and produces a cryptographic receipt.

Claude Desktop

# Generate a .mcpb bundle
helm mcp pack --client claude-desktop --out helm.mcpb

Double-click helm.mcpb or drag it into Claude Desktop to install. The bundle includes the cross-platform HELM binary and auto-starts the MCP server.

Claude Code

helm mcp install --client claude-code

Installs a plugin that bundles a .mcp.json config. Tool calls are intercepted by the governance firewall and recorded as signed receipts.

Cursor

helm mcp print-config --client cursor

Add the output to .cursor/mcp.json:

{
  "mcpServers": {
    "helm-governance": {
      "command": "helm",
      "args": ["mcp", "serve", "--transport", "stdio"]
    }
  }
}

VS Code

helm mcp print-config --client vscode

Add the output to .vscode/settings.json:

{
  "mcp": {
    "servers": {
      "helm-governance": {
        "command": "helm",
        "args": ["mcp", "serve", "--transport", "stdio"]
      }
    }
  }
}

Windsurf

helm mcp print-config --client windsurf

Windsurf supports both stdio and HTTP transports:

# Remote HTTP transport
helm mcp serve --transport http --port 9100
# URL: http://localhost:9100/mcp

Codex

codex mcp add helm-governance -- helm mcp serve --transport stdio

What happens after install

Every tool call from your AI coding tool now passes through HELM:

AI Tool Call → HELM MCP Server → Policy Check → Execute or Deny → Receipt

• ALLOW → tool executes, result returned, receipt stored
• DENY → tool blocked, reason code returned, denial receipt stored

Both outcomes produce a signed receipt in the ProofGraph.

Authentication

Mode	Use case	Config
None (default)	Local stdio	No config needed
Static API key	Remote HTTP	Set HELM_API_KEY env var

Next steps

• Quickstart — install HELM and run your first governed call
• Writing Policy Files — control what tools can do
• Proxy API — HTTP proxy endpoints and headers