Run WhatsApp From Claude
Connect Washarp to Claude Desktop and handle your numbers by asking — what came in today?, reply to Budi — instead of clicking through an inbox. Setup takes about a minute.
A Washarp account with at least one connected number
Claude acts as you. If no number is linked yet, connect one first — the tools have nothing to read or send until then.
Claude Desktop, updated
Custom connectors live under Settings → Connectors. If you do not see that section, update Claude Desktop; the feature also requires a paid Claude plan.
The same login you use here
Connecting opens a normal Washarp sign-in. Claude never sees your password — it receives a token scoped to your account, which you can revoke at any time.
Add the connector
- 1
Open connector settings in Claude Desktop
Go to Settings → Connectors, then choose Add custom connector.
- 2
Paste this address
Connector URLhttp://washarp.online/api/mcpGive it a name you will recognise — “Washarp” works.
- 3
Sign in and approve
Claude opens a Washarp sign-in window. Use the same account you use here, then approve the access screen. Claude receives a token for your account only — never your password.
- 4
Check it worked
Start a new chat and ask:
Who am I connected as in Washarp?Claude should answer with your email address and which workspace it is acting in. If it does, you are done — try “what came in on WhatsApp today?” next.
Prefer a config file?
For other MCP clients — or Claude Desktop without custom connectors — add Washarp to claude_desktop_config.json instead. The sign-in happens in your browser the first time you start it.
{
"mcpServers": {
"washarp": {
"command": "npx",
"args": ["-y", "mcp-remote", "http://washarp.online/api/mcp"]
}
}
}What Claude can do
Eleven tools, all limited to what you can already do in Washarp. You never call these by name — describe what you want and Claude picks.
| Tool | Effect | What it does |
|---|---|---|
| whoami | Reads | Which account Claude is connected as |
| list_sessions | Reads | Every WhatsApp number and its status |
| get_session | Reads | Live status of one number |
| get_session_qr | Reads | The QR code to link a phone |
| list_chats | Reads | Recent conversations, searchable by name |
| list_messages | Reads | The messages in one conversation |
| inbox_overview | Reads | Everything unread, across all numbers |
| create_session | Changes | Adds a slot for a new number |
| start_session | Changes | Restarts a stopped number |
| send_message | Sends | Sends a WhatsApp message |
| delete_session | Deletes | Unlinks a number from Washarp |
Messages go to real people
send_message reaches a real contact the moment it runs and cannot be unsent; delete_session unlinks a number. Both are marked so Claude asks you before running them — leave that confirmation on, and read the message text and recipient before you approve.
You can revoke Claude’s access at any time from your account settings, without touching your WhatsApp numbers.
If something goes wrong
Still stuck? The technical reference — endpoints, the OAuth handshake, and self-hosting notes — lives in MCP.md in the repository, and the FAQ covers Washarp itself.