edouard-claude/whatsapp-mcp

A full-featured Model Context Protocol server for WhatsApp.
Rust MCP server · Go bridge on whatsmeow · SQLite + full-text search · multi-account
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.
text
MCP host (Claude Code, Claude Desktop, your agent...)
| stdio (JSON-RPC)
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)
wa-bridge (Go, whatsmeow) -- one process, N WhatsApp accounts
WhatsApp (multi-device web protocol)
## Why another WhatsApp MCP?
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:
| | this project |
| MCP surface | 39 tools with output schemas and exact risk annotations, resources and URI templates, 5 prompts, argument completion, live resource notifications (resources/subscribe and subscriptions/listen) |
| Nothing lost | every message is stored with its raw protobuf; a message type unknown today is decoded tomorrow without a resync (134 such messages were reclassified in practice) |
| At-least-once ingestion | whatsmeow acknowledges a message to WhatsApp only after it is committed in SQLite (SynchronousAck); a crash means redelivery, never loss |
| Identity | WhatsApp's phone-number and LID identities are unified at write time, and past rows are merged when a mapping is learnt |
| Rich content | replies, reactions, edits, deletions for everyone, polls, albums, events, locations, contacts, business messages |
| Media | raw files for the host model to listen to or look at; expired media is re-requested from the phone automatically |
| Session care | three-level reconnection (whatsmeow, backoff, watchdog), per-account lock so two instances never kick each other out |
| Multi-account | several WhatsApp numbers behind one server, pairing by 8-character code directly from an MCP tool |
| Agnostic | no AI inside: transcription, image description and summaries are the host model's job |
| Distribution | two static binaries, no Python, no CGO, no runtime dependency |
## Install
### Prebuilt binaries (macOS, Linux)
bash
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
WAMCPINSTALLDIR). 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, x8664-apple-darwin, x8664-unknown-linux-gnu,
aarch64-unknown-linux-gnu.
### From source
Requirements: Rust 1.94+, Go 1.25+, protoc (Protocol Buffers compiler).