Use Zap from your agent
Point your agent at Zap.
One MCP command or one URL. Every CLI command supports --json. The first-run sequence below plans everything and executes nothing live: no sandbox is acquired and no provider is called.
safe first run — plan only
no live worknpx @wzrdtech/[email protected] doctor --json
npx @wzrdtech/[email protected] init my-zap --non-interactive --json
cd my-zap
npx @wzrdtech/[email protected] compose --weight med --sandbox box --dry-run --jsonConnect over MCP
Add Zap as an MCP server in any MCP-capable coding agent. Plan-only stays the default; live side effects require explicit intent and a configured payer.
MCP — stdio
copy & connectnpx -y @wzrdtech/[email protected] mcpAgent map (this site)https://zap.wzrd.tech/llms.txt
Full agent indexhttps://docs.zap.wzrd.tech/llms.txt
Per-client setuphttps://docs.zap.wzrd.tech/agents/use-zap
Canonical docshttps://docs.zap.wzrd.tech
Safety invariants: side-effecting tools are planned, never executed, without --live and a payer; a missing payer fails closed with PAYER_MISSING; agent secrets are write-only and scoped to declared HTTPS connections.
Works with
Claude CodeMCP
CursorMCP
CodexMCP
DevinMCP
OpenClawMCP
HermesMCP
PiMCP