Run it

MCP server

Delego ships an MCP server, delego-mcp, that runs over stdio. Wire it into any MCP client and your agent proposes actions instead of executing them — no application code required.

Install

The MCP server is an optional extra. Installing it adds the delego-mcp console script:

shell

pip install "delego[mcp]"

Wire it into an MCP client

Register the server in your client’s MCP config. The command is delego-mcp; set DELEGO_HOME to keep the policy, signing keys, and ledger project-scoped. For Claude Code, this is .mcp.json at the project root:

.mcp.json

{
  "mcpServers": {
    "delego": {
      "command": "delego-mcp",
      "env": { "DELEGO_HOME": "/abs/path/to/project/.claude/.delego" }
    }
  }
}

Use an absolute path for DELEGO_HOME — the server’s launch directory isn’t guaranteed. The CLI and the MCP server must share one home so a human can approve the actions the agent proposes.

Initialise the shared home

Create that home, then list and decide pending approvals from the same one:

shell

delego --home .claude/.delego init      # keys, example policy, and a .gitignore
delego --home .claude/.delego pending   # then: delego --home .claude/.delego approve apr_xxxx

Tools exposed

delego_propose_action — submit an action; returns allow / deny / needs_approval.
delego_resolve_action — complete an approved action (the fingerprint must match).
delego_audit_tail — read recent receipts.
delego_show_policy — show the active policy.

Typical flow

The agent calls delego_propose_action. If it comes back needs_approval with an approval_id, a human runs delego approve <id>, then the agent calls delego_resolve_action with the identical action to complete it. A substituted action is refused by the confused-deputy guard.

PreviousHow it works NextClaude Code plugin