Agent Integrations

Caplets works with Codex, Claude, OpenCode, Pi, and other MCP clients. Code Mode is the default surface for configured capabilities.

Codex

Run setup:

caplets setup

Manual local MCP config:

[mcp_servers.caplets]
command = "caplets"
args = ["serve"]

Claude

Run setup:

caplets setup

Manual setup uses Claude’s MCP command:

claude mcp add --transport stdio --scope user caplets -- caplets serve

OpenCode

OpenCode can use Caplets through MCP or the native OpenCode integration. Native mode exposes caplets__code_mode for Code Mode, plus progressive or direct tools only when configured.

Native integrations use the shared anonymous telemetry controls and do not send telemetry on a native-first run until a visible CLI telemetry notice has already been recorded.

Remote native usage:

CAPLETS_MODE=remote CAPLETS_REMOTE_URL=https://caplets.example.com/caplets opencode

Pi

Pi can use Caplets through MCP or the native Pi integration. Native mode uses the same local and remote selection rules as OpenCode.

Native integrations use the shared anonymous telemetry controls and do not send telemetry on a native-first run until a visible CLI telemetry notice has already been recorded.

Remote native usage:

CAPLETS_MODE=remote CAPLETS_REMOTE_URL=https://caplets.example.com/caplets pi

Other MCP clients

Use:

{
  "mcpServers": {
    "caplets": {
      "command": "caplets",
      "args": ["serve"]
    }
  }
}

For remote-backed MCP, use caplets attach instead of caplets serve.

caplets attach <url> is stdio-only. If you want one local HTTP runtime to own environment, Vault, Remote Login, reloads, and logs while still composing an upstream host, run:

caplets serve --transport http --upstream-url https://caplets.example.com/caplets

Then configure the MCP client with caplets attach <local-runtime-url>.