Skip to main content
Zap ships an MCP server in the CLI. Any MCP-capable agent gets the full tool surface — recipes, compose, runtime, agents, fs, harness, pay, memory, media, doctor — from one command:
No MCP support? Paste these URLs into your agent chat instead:

Connect your agent

Claude
Or add to .mcp.json in your project root:
.mcp.json

HTTP transport

For remote agents, run Streamable HTTP instead of stdio:
Non-loopback binds require ZAP_MCP_TOKEN. See MCP for tool domains and transport details.

What your agent can do

Compose runtimes

Resolve Runtime.md into a deterministic plugin tree with a lock hash.

Run agents

Render, deploy, and drive durable sessions — plan-only by default.

Drive sandboxes

Exec CPU work on Box VMs and every other provider behind one contract.

Stay machine-readable

Every tool returns structured JSON with stable error codes.