{origin}/mcp: read analytics, manage your AI assistants, and send
messages and broadcasts. Same business logic and auth as the REST API.
Every tool is scoped to your business over OAuth and carries read-only / destructive hints,
so the agent knows what’s safe to call before it calls it. Titles and descriptions ship in
English and Portuguese. Connect Claude, ChatGPT, or Cursor in one click.
Choosing WhatsApp tooling for AI agents?
How iZap compares to transport-only APIs (Twilio, Cloud API, 360dialog) and no-code
inboxes — and when each is the right pick.
Connect
Authentication is OAuth 2.0 (interactive clients bootstrap it automatically) or a Bearer JWT for server-to-server code. Register it as a remote HTTP MCP server:Add to your AI client
Point any MCP-capable client at the URL above — interactive clients run the OAuth login for you.- Cursor
- Claude
- ChatGPT
- Codex CLI
- Manus
One-click: open Add iZap to Cursor and confirm the install — or paste this link into your browser:Manual — add to
~/.cursor/mcp.json (global) or .cursor/mcp.json (per-project):Swap the host for the staging URL (
https://api-staging.izap.ai/mcp) to test against staging.Tool catalog
All tools accept an optionalbusiness_id (UUID); omit it to use your first
business. Read-only tools are safe to call freely; the ones marked write create,
change, or send.
Analytics (read-only)
AI assistants
Contacts & WhatsApp messaging
Broadcast transmissions
Notes
- Dates are ISO-8601 strings (e.g.
2026-04-15); timezone is an IANA name (e.g.America/Sao_Paulo). search_today_messagesis rate-limited per user per day.- Server errors surface as MCP tool errors (
isError: true) with the messageError <status>: <detail>; a401means refresh the token.
Build with the MCP in your code
Get a token, then use the Python or TypeScript MCP SDK to call these tools from
your own app or agent.