Skip to main content
@izapai/wizard is a developer-facing CLI that adds iZap to an existing app. It is recipe-driven and deterministic: it detects your stack, writes small explicit edits and source-backed scaffolds, and previews every change before touching a file. No API key or LLM call is required.

​
Run it

Or install the binary globally:
On a terminal, the bare command launches a full-screen wizard with a live task checklist and Status / Logs / Reference tabs. In a pipe or CI it prints the same steps line by line — and without a TTY, writing requires --yes: otherwise the run previews the plan and exits non-zero. --dry-run previews without writing; --yes skips the confirmation gate. The wizard never overwrites a scaffold file you have edited: conflicting files stop the run with a clear list, and --force overwrites deliberately. .env.example files union-merge (your lines win, missing keys append), and a malformed .mcp.json aborts instead of being replaced.

​
What it scaffolds

MCP client

Install the iZap MCP server into .mcp.json, plus a TypeScript or Python client. See Analytics MCP.

REST client

JWT or OAuth 2.0 + PKCE client scaffold for TypeScript or Python. See Authentication.

Webhooks & SSE

A webhook receiver or a Server-Sent Events client for live chat streams.

WhatsApp surfaces

Templates, transmissions (broadcasts), send-message, and a Meta Embedded Signup connect page — server-side so your JWT never reaches the browser.

​
Common commands

Shared flags: --dry-run, --json, --force, --output-dir DIR, --target-root PATH, --env production|staging.

​
Agent handoff

izap-wizard ai "<goal>" runs the same detection and planning, then writes an izap-integration-brief.md you can hand to a coding agent (Claude Code, Cursor, or an MCP-connected agent):
The wizard never reads your .env values and never writes secrets. It prefers idempotent writes and shows planned changes under --dry-run.