Connect your WhatsApp
Enter your number → get a code and QR. Then give AI tools safe access. You stay in charge.
1 · Your number
We generate an 8-digit code and a QR at the same time. Confirm once on your phone.
Pairing code
Link with phone number instead
----
- WhatsApp → Linked Devices → Link a Device
- Tap Link with phone number instead
- Enter the code above
QR code
Scan with WhatsApp camera
Waiting…
![WhatsApp QR code]()
- WhatsApp → Linked Devices → Link a Device
- Point the camera at this QR
Prefer scan without typing a number? Use the QR on the homepage
What this unlocks
After linking, WAMCP is only a bridge. Chat stays in the official WhatsApp app.
AI agents (MCP)
66 tools: read, search, reply, groups, media, notifications.
Full API access
REST key
wbot_… for apps: send, history, webhooks, health.
You control it
Name agents · auto / approval / read-only · revoke anytime.
Not a second inbox
Infrastructure for agents & backends — not a chat UI.
Permissions at a glance
MCP · agents
If you allow it
- Read chats, contacts, groups, media
- Send / reply / react
- Watch notifications (reactive loops)
- Approval mode: you confirm in portal
REST · apps
With API key
- Session health & reconnect
- Send + outbound flows
- History, sync, webhooks
- Enable / rotate MCP tokens
Default after connect: send + read on, provision off. Docs: /docs · playbook
Connecting many numbers? (workspace)
Optional for SaaS. Personal users can skip — we auto-create a private workspace when you connect.
Used on the next generate so numbers stay under the same org.
For developers & AI agents
/docs/agent-playbook ·
/llms.txt ·
/docs
Agent path:
POST /api/session/connect/kit with phone_number
(+ optional X-Tenant-Key) → poll status → paste mcp_connection.cursor_mcp_example.
Homepage QR (no phone): POST /api/session/connect/qr on /.
| HTTP | Meaning | What to do |
|---|---|---|
| 401 | Invalid workspace key | Clear key or leave empty |
| 403 | UUID / other workspace | Restart with same key |
| 429 | Rate limited | Wait, then retry |