Skip to main content
@izap/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

npx @izap/wizard                              # interactive wizard (on a TTY)
npx @izap/wizard run "add iZap MCP"           # same, with a stated goal
npx @izap/wizard plan "connect an AI client"  # read-only plan, writes nothing
Or install the binary globally:
npm install -g @izap/wizard
izap-wizard doctor
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. --dry-run previews without writing; --yes skips the confirmation gate.

What it scaffolds

MCP client

Install the iZap Analytics 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

izap-wizard mcp add                              # install the iZap MCP server
izap-wizard mcp client --stack typescript        # scaffold an MCP client
izap-wizard rest client --stack python --auth oauth
izap-wizard webhook receiver --stack typescript
izap-wizard sse client --stack python
izap-wizard whatsapp connect                     # WhatsApp Business onboarding page

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):
izap-wizard ai "add iZap MCP to my Next.js app"
# → Wrote izap-integration-brief.md (detected stack, recipe, edit points)
The wizard never reads your .env values and never writes secrets. It prefers idempotent writes and shows planned changes under --dry-run.