Provides read and write access to WhatsApp, including tools for managing chats, messages, media, contacts, groups, and connection status.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@WhatsApp MCP list my recent chats"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
An MCP server that gives Claude read and write access to WhatsApp, through a
self-hosted Evolution API
gateway. Dependency-free: one file, Node's built-in fetch, stdio transport.
Your number stays linked on your own machine. No third party sees the messages.
Tool | What it does |
| Is the number linked and online. |
| Recent chats, newest first, with JIDs and unread counts. |
| Messages in one chat. Each carries an |
| Download the attachment on a message. Images come back viewable inline. |
| Match contacts by name or number substring. |
| Is a phone number registered on WhatsApp. |
| Groups this number belongs to, with JIDs. |
| Send a text message. The only tool with an outbound side effect. |
| Returns a pairing QR when the link has dropped. |
| Bounce a stuck instance. Does not unlink the number. |
Related MCP server: mcp-zap
A running Evolution API instance with a linked WhatsApp number. This server is only a client; it does not start or manage the gateway.
All configuration is environment variables:
Variable | Default | Meaning |
| (required) | Global API key, |
|
| Base URL of the Evolution API server. |
|
| Instance name for your number. |
|
| Where |
|
| Where |
Register it with Claude Code:
claude mcp add whatsapp -s user \
-e EVO_APIKEY=your-key \
-e EVO_URL=http://localhost:8080 \
-e EVO_INSTANCE=primary \
-- node /path/to/whatsapp-mcp/server.js
claude mcp list # expect: whatsapp ... ConnectedRestart Claude Code afterwards. Tool lists are read once at session start, so a newly added server (or a newly added tool) will not appear in a session that was already running.
EVO_APIKEY=your-key npm testAn integration check against the live gateway, no mocks: it spawns a real server
process, finds a recent image on its own, and asserts get_media returns decoded
image bytes and writes them to disk. Pin a specific message with
WA_TEST_MESSAGE_ID if you would rather not have it search.
get_media inlines images up to 3.5 MB; anything larger, and any non-image, is
saved to disk and the path is returned instead.
Downloads are pruned after 24 hours so a chat full of photos cannot quietly grow into a disk problem.
Media only downloads while it is still on WhatsApp's servers. Very old attachments can come back empty.
This server cannot be deployed
WhatsMCP connects Claude and other MCP-compatible AI agents directly to WhatsApp. Send and receive text, images, documents, and voice notes; manage groups (create, add/remove members, promote admins); look up contacts and profiles; follow channels; and read call and message history — all through a standard MCP interface. For voice use cases, WhatsMCP offers SIP-based calling plans (inbound-only, or full inbound/outbound) so AI voice agents can answer and place WhatsApp calls, plus low-latency WebSocket integrations with voice agent providers like ElevenLabs. Multiple WhatsApp accounts can be paired and managed per workspace, with webhook support for real-time inbound message delivery to your own infrastructure.
Your own WhatsApp as an MCP server: read, search and send from any MCP client.
Ask questions across your WhatsApp inbox from Claude, ChatGPT, Cursor or any MCP client.
Hosted X (Twitter) MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
