whatsapp-mcp
A full-featured Model Context Protocol server for WhatsApp. Rust MCP server · Go bridge on whatsmeow · SQLite + full-text search · multi-account
Power your agent
पब्लिशर का इंस्टॉल। PlugMCP एंडपॉइंट नहीं।
Host a copy with our keys and logs.
रजिस्ट्री में अभी कोई पैकेज्ड रिलीज़ नहीं है। रिपॉज़िटरी का README देखें.
रिमोट URL या आपकी मशीन पर कमांड? दोनों इंस्टॉल में क्या अंतर है
PlugMCP पर चलाएँ
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
लॉन्चपब्लिशर से
A full-featured Model Context Protocol server for WhatsApp. Rust MCP server · Go bridge on whatsmeow · SQLite + full-text search · multi-account
Full-featured WhatsApp MCP server: Rust MCP server + Go whatsmeow bridge. 39 tools, resources, prompts, live notifications, multi-account, full-text search, raw media for your agent.
Give an AI agent your WhatsApp: read and search every conversation, send and reply, react, edit and delete, manage groups and communities, fetch voice notes and images as raw files, and get notified the moment a message arrives. One stdio binary, no Python, no service to install, your data stays on your machine.
MCP host (Claude Code, Claude Desktop, your agent...)
| stdio (JSON-RPC)
v
wa-mcp (Rust, tokio, rmcp)
|- mcp 39 tools, resources + templates, prompts, completions, subscriptions
|- store one SQLite per account, FTS5 search, raw protobuf of every message kept
|- ingest live events + history -> store, acknowledged to WhatsApp only after commit
| stdin/stdout pipes, length-prefixed protobuf frames (proto/bridge.proto)
v
wa-bridge (Go, whatsmeow) -- one process, N WhatsApp accounts
v
WhatsApp (multi-device web protocol)
Existing servers (lharries/whatsapp-mcp, rodrigopg/whatsapp-mcp) proved the idea: a whatsmeow bridge plus a Python MCP server exposing a dozen tools. This project rebuilds it end to end:
curl -fsSL https://raw.githubusercontent.com/edouard-claude/whatsapp-mcp/main/install.sh | sh
This downloads the latest release for your platform, verifies its checksum and
installs wa-mcp and wa-bridge side by side in ~/.local/bin (override with
WA_MCP_INSTALL_DIR). Both binaries must stay in the same directory: wa-mcp
starts wa-bridge from there.
Or grab an archive from the releases page:
aarch64-apple-darwin, x86_64-apple-darwin, x86_64-unknown-linux-gnu,
aarch64-unknown-linux-gnu.
Requirements: Rust 1.94+, Go 1.25+, protoc (Protocol Buffers compiler).
git clone https://github.com/edouard-claude/whatsapp-mcp
cd whatsapp-mcp
make build PROFILE=release # target/release/wa-mcp + target/release/wa-bridge
docker build -t whatsapp-mcp https://github.com/edouard-claude/whatsapp-mcp.git
docker run -it --rm -v wa-data:/data whatsapp-mcp pair perso --phone 33612345678
docker run -i --rm -v wa-data:/data whatsapp-mcp serve
The volume keeps the WhatsApp session and the message database between runs.
wa-mcp pair perso --phone 33612345678
Enter the 8-character code on your phone: WhatsApp › Linked devices › Link a device ›
Link with phone number instead. Leave the command running: your history
(often years of messages) is downloaded and indexed right after pairing, then stop it
with Ctrl-C. Without --phone, a QR code is printed in the terminal instead.
perso is an alias of your choice; repeat with another alias for another number.
wa-mcp doctor # checks binaries, data directory, accounts, locks
Claude Code
claude mcp add whatsapp -- wa-mcp serve
Claude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"whatsapp": { "command": "/Users/you/.local/bin/wa-mcp", "args": ["serve"] }
}
}
Any stdio MCP client: run wa-mcp serve. Add --read-only to expose read tools only.
If you are an agent asked to install this server, follow these steps in order and check each result before moving on.
curl -fsSL https://raw.githubusercontent.com/edouard-claude/whatsapp-mcp/main/install.sh | sh.
If no release matches the platform, build from source (Rust 1.94+, Go 1.25+, protoc)
with make build PROFILE=release and copy target/release/wa-mcp and
target/release/wa-bridge into the same directory on the PATH.wa-mcp doctor must print bridge … ok. If it says the bridge is
missing, wa-bridge is not next to wa-mcp (or pass --bridge /path/to/wa-bridge).+
or leading zero (e.g. 33612345678) and an alias (lowercase, digits, -, _).
Run wa-mcp pair <alias> --phone <number> and give the user the printed code; they
enter it on their phone under Linked devices › Link with phone number instead.
Keep the process running until the history lines stop (historique … 100 %),
then stop it. Alternatively, once the server runs, call the session_pair tool.claude mcp add whatsapp -- wa-mcp serve,
or the host's stdio configuration with command wa-mcp and argument serve).session_status tool: state must be connected.Things to know:
wa-mcp on the same account refuses to start
(per-account lock). Stop wa-mcp pair/run before the host starts serve.wa-mcp serve runs; hosts
that stop idle servers disconnect it. WhatsApp also unlinks devices when the phone
itself stays offline for about 14 days.send_*, edit_message, delete_message or group change.A chat or contact can be designated by JID, international number or name
(accent- and case-insensitive); an ambiguous name returns the candidates.
Dates accept 2026-09-30, 2026-09-30T08:00, today, yesterday, or an elapsed
duration (24h, 7d). Tool descriptions are written in French.
whatsapp://accounts
whatsapp://{account}/status
whatsapp://{account}/chats
whatsapp://{account}/chat/{chat}
whatsapp://{account}/chat/{chat}/messages
whatsapp://{account}/contact/{contact}
whatsapp://{account}/media/{chat}/{message_id}
Subscribe to whatsapp://{account}/chat/{chat}/messages to receive
notifications/resources/updated on every new message in that chat.
catch_up, summarize_chat, draft_reply (in your own writing style),
daily_digest, extract_actions.
Data layout: accounts/<alias>/session.db (whatsmeow keys), store.db (messages,
contacts, groups), media/ (downloaded files), lock.
--read-only.session.db holds your WhatsApp encryption keys. Protect the data directory like
a password.make build # debug build of both binaries
make check # cargo fmt --check, clippy -D warnings, go vet
make test # unit tests (store merges, FTS, parsing, message building...)
make proto # regenerate Go code after editing proto/bridge.proto
proto/bridge.proto: the only contract between Rust and Go. The bridge stays
deliberately thin: it exposes whatsmeow, no business logic, no SQL.proto/whatsmeow/: whatsmeow's .proto files, vendored at the commit pinned in
bridge/go.mod (see proto/whatsmeow/VERSION), compiled by prost.crates/wa-mcp/src/: bridge.rs (child process), ingest.rs, store.rs,
query.rs, parse.rs / compose.rs (WhatsApp messages in and out), mcp/.docs/plan.md: the original design notes (in French).MIT, see LICENSE. The bridge links whatsmeow
(MPL-2.0), whose .proto files are vendored under proto/whatsmeow/; release
binaries therefore include MPL-2.0 code, whose source is available upstream.
Inspired by lharries/whatsapp-mcp and
rodrigopg/whatsapp-mcp.
Not affiliated with, endorsed by or connected to WhatsApp or Meta. Use at your own risk and in accordance with WhatsApp's terms.
Full-featured WhatsApp MCP server: Rust MCP server + Go whatsmeow bridge. 39 tools, resources, prompts, live notifications, multi-account, full-text search, raw media for your agent.
टूल
अभी टूल सूची नहीं है। रिमोट सर्वर को पहले हेल्थ चेक के बाद सूची मिलती है।
FAQ
इस पेज पर Cursor, Claude Desktop, Claude Code या VS Code के लिए stdio कॉन्फ़िग कॉपी करें। यह पब्लिशर का इंस्टॉल इस्तेमाल करता है, PlugMCP प्रॉक्सी नहीं।
इस रिकॉर्ड में कोई ज़रूरी एनवायरनमेंट वेरिएबल दर्ज नहीं है।
Whatsapp stdio पर लोकल चलता है।
पिछली जाँच 2026-10-27 को हुई। Full-featured WhatsApp MCP server: Rust MCP server + Go whatsmeow bridge. 39 tools, resources, prompts, live notifications, multi-account, full-text search, raw media for your agent.