Create a pairing session
Generate a QR code or phone-number sync flow for the WhatsApp account you want to connect.
$ npx @whatsapp-use/mcp
Pair an existing WhatsApp account and give full access to your agent. Drop our MCP server into Claude, OpenClaw, Hermes, or any MCP-aware tool — one config entry, no glue code.
Add the WhatsApp-Use MCP server.
Server: https://mcp.whatsapp-use.dev
Key: wuse_live_92k
Then pair my WhatsApp account.Connect an existing WhatsApp account. Same flow as adding a WhatsApp Web session.
One MCP endpoint, every agent speaks it. Claude Desktop, Cursor, Cline, custom — no glue code.
Hosted cloud by default. Move sensitive accounts into a dedicated TEE.
how it works
We host the WhatsApp client and the pairing flow. You authorize the account, then your agent talks to it over MCP.
Generate a QR code or phone-number sync flow for the WhatsApp account you want to connect.
The account owner scans the QR or completes phone sync. We host the WhatsApp client behind the scenes.
Drop our MCP server into Claude Desktop, Cursor, Cline, or any MCP-aware tool with one config entry.
The server pushes message, edit, and pairing events back to your agent in real time.
use cases
Personal assistants, coding agents, MCP-aware tools, or anything custom you build.
Hand your WhatsApp to Claude, ChatGPT, or any custom assistant. Daily briefs, on-the-go replies, full search.
Get pinged when a build finishes or a PR is ready. Reply to deploy from your phone.
Use your WhatsApp from Claude Desktop, Cursor, or any MCP-compatible client. Drop-in setup.
Auto-respond to scheduling requests, confirm meetings, and send reminders.
Let an agent search your WhatsApp for context — past conversations, files, decisions.
Any custom agent that speaks MCP — connect it in one config entry and start sending.
deployment
Start in the hosted cloud. Move sensitive accounts into a dedicated TEE when you need a verifiable privacy boundary.
Multi-tenant runtime with encrypted storage and audit logs. The right default for most agents and personal use.
Dedicated tenant inside a Trusted Execution Environment. Message data is sealed to the enclave — even we can't read into it.
faq
Mostly about how this is built and what happens to your data.
No. WhatsApp-Use runs on the same protocol WhatsApp Web uses (a whatsmeow-style client). That's how we keep pairing instant and skip the Business API onboarding queue.
WhatsApp lets users connect their account to web sessions, which is what we do under the hood. Heavy automation can still trigger rate limits or bans — respect limits and don't message people who didn't ask to hear from you.
QR code or phone-number sync — the same flow as adding a new WhatsApp Web session. The account owner stays in control and can revoke at any time.
Encrypted in our hosted cloud by default. On Enclave, message data is sealed inside a TEE running on dedicated infrastructure — we can't read into it.
Yes. We ship an MCP server. Add it to Claude Desktop, Cursor, Cline, or any MCP-aware client with one config entry. Custom agents on other stacks can use any MCP client library.
Sessions disconnect immediately. Stored messages and webhook logs are purged within 30 days.
pricing
Cloud pricing is per WhatsApp account you've paired. Enclave runs on dedicated TEE infrastructure and is priced separately.
Trial
Pair one account and try the full MCP server. No card required.
Connect
Per-account pricing for agents running on the hosted cloud.
Enclave
Dedicated TEE tenant for teams with regulated data or strict privacy boundaries.
start
7 days free, then $20 per connected account. Cancel any time.