Personal WhatsApp MCP for Claude, built directly on whatsmeow. Encrypted-at-rest storage, Whisper…
Quick Install
Automated & IDE SetupCopy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
Not yet automatically verified
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.
Manual Client & Custom JSON ConfigExpand JSON ▾
Client Config & Setup
Choose your client or environment
Target File:
💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Documentation Overview
whatsapp-mcp
A WhatsApp MCP server for Claude, built directly on whatsmeow. Encrypted at rest, prompt-injection-scrubbed, draft-and-confirm on every send, full audit trail, daily CI security gates. Actively maintained.
Why this one?
The most-starred WhatsApp MCP (lharries/whatsapp-mcp, 5.6K stars) is the architectural reference for this pattern, but has not shipped since July 2025 and leaves the lethal-trifecta problem entirely to the user. This implementation closes the gaps:
| Canonical | This implementation | |
|---|---|---|
| Last shipped | July 2025 | Active |
| DB encryption | Plain SQLite | SQLCipher with key in the platform secret store (macOS Keychain / Windows Credential Manager / libsecret) |
| Prompt-injection scrubber | None | Every inbound message |
| Send safety | Fires immediately | Mandatory confirm_send between draft and delivery |
| Audit log | None | Every tool call, 30-day retention |
| Voice notes | Not transcribed | whisper.cpp local, Spanish-tuned default |
| LID alias resolution | Open issue cluster upstream | Shipped, with backfill migration for legacy threads |
| CI security | None | govulncheck + pip-audit + Dependabot, daily |
Not a fork. The Go bridge is built directly against whatsmeow; the Python MCP layer and SQLite schema are original. Other implementations (lharries, LukasHaas, verygoodplugins) were read as reference only.
What this gives you
Claude can:
- Read your WhatsApp chats, messages, and contacts
- Search messages with accent-insensitive, typo-tolerant matching
- Transcribe voice notes locally via
whisper.cpp(Spanish-tuned by default) - Resolve LID (Linked IDentifier) names instead of numeric placeholders
- Send text messages, reactions, and reply-quotes, with a mandatory
confirm_sendstep between draft and delivery - Pull matching CRM context from your Obsidian vault when reading a chat
- See only prompt-injection-scrubbed message text, never raw adversarial input
Everything runs locally on your machine. No cloud sync. No telemetry. Optional OpenAI Whisper backend is opt-in, off by default.
Architecture
Two components, both local:
whatsapp-bridge/(Go). Binds to 127.0.0.1 only. Wrapswhatsmeowfor the WhatsApp Web multidevice protocol. Owns SQLite persistence with SQLCipher encryption. Handles QR and pairing-code auth (live-refreshing terminal QR with Windows-safe rendering, plus a headless auth API —GET /api/auth/qr,POST /api/auth/pair-phone,POST /api/auth/reconnect— so a GUI or supervisor can drive pairing without a terminal), media up/download, session recovery fromStreamReplacedconflicts, call history capture. Exposes a REST API the Python MCP layer consumes.whatsapp-mcp-server/(Python, FastMCP). Consumes the Go bridge REST API. Exposes 11 MCP tools to Claude: full read surface (chats, messages, contacts), accent-insensitive search, presence (typing, online, mark-read), and text-send + reactions + reply-quotes with mandatoryconfirm_send. Runs viauvand stdio transport.
Install
Open Claude Code, paste:
This installs the Python MCP server side. The Go bridge still needs the one-time QR pairing flow with your phone — see the legacy install block below for those steps.
Manual install (full Go bridge + QR pairing)
See SETUP.md for step-by-step install per OS. In short:
- Grab a prebuilt bridge binary from Releases (Windows/macOS/Linux — no compiler needed), or build from source (Go 1.26+ and a C toolchain)
- Python 3.11+ and
uvfor the MCP server layer - Clone this repo; verify with
scripts/check_prerequisites.sh(Windows:scripts\check_prerequisites.ps1) - Start the bridge:
./bin/whatsapp-bridge(Windows:.\bin\whatsapp-bridge.exe) - Scan the QR (it refreshes in place — always scan the one on screen), or pair by typed code with
--pair-phone +15551234567 - Register the MCP in your Claude Code
.mcp.json - Restart Claude Code
FFmpeg and whisper.cpp are only needed if you enable voice-note transcription (off by default).
Configuration
All configurable via environment variables. See .env.example for the full list.
Key variables:
| Variable | Default | Purpose |
|---|---|---|
WHATSAPP_BRIDGE_PORT | 8080 | Go bridge REST API port |
WHATSAPP_DB_PATH | $HOME/.claude/whatsapp-mcp/store/messages.db | Encrypted SQLite database |
WHATSAPP_MEDIA_PATH | $HOME/.claude/whatsapp-mcp/media/ | Media file storage |
WHATSAPP_VAULT_CRM_PATH | empty | Absolute path to your vault CRM folder for auto-injection (e.g., Obsidian 👤 CRM/). When unset, CRM injection is disabled. |
WHATSAPP_WHISPER_BACKEND | off | off (zero-config boot), local-cpp (private, needs a whisper model), or openai-api (opt-in) |
WHATSAPP_WHISPER_API_KEY | empty | Required only when backend is openai-api |
WHATSAPP_WHISPER_MODEL | large-v3 | whisper.cpp model name |
WHATSAPP_SCRUB_PROMPT_INJECTION | true | Strip known prompt-injection patterns from incoming messages before Claude sees them |
WHATSAPP_AUDIT_LOG | true | Log every tool call to audit.log |
WHATSAPP_ENCRYPT_DB | true | Enable SQLCipher DB encryption; key in the platform secret store (macOS Keychain / Windows Credential Manager / libsecret) |
WHATSAPP_DB_KEY | empty | Explicit 64-hex-char SQLCipher key override (skips the platform store). Escape hatch for headless/CI/custom secret managers, and the recovery path when the secret store cannot be read — see below |
The DB key and WHATSAPP_DB_KEY
With WHATSAPP_ENCRYPT_DB=true (the default), the bridge encrypts the message
store with a 256-bit SQLCipher key kept in the platform secret store. The key
lifecycle is deliberately conservative, because a wrong key silently orphans
every stored message:
- A fresh key is minted only when the secret store definitively answers
"no such item" (macOS
errSecItemNotFound, WindowsERROR_NOT_FOUND, libsecret clean miss) and no non-empty store database exists yet. - Any other failed read — locked keychain, no D-Bus session, revoked access —
makes the bridge exit with an error instead of minting: the key may still
exist, and overwriting it would make the encrypted store permanently
undecryptable. The error names the fix (e.g.
security unlock-keychain). - If the secret store has no key but a populated store database exists, the bridge also refuses to mint and asks you to supply the original key.
WHATSAPP_DB_KEY (64 hex chars = 32 bytes, e.g. openssl rand -hex 32) is
the escape hatch for all of these: when set, it is used directly and the
platform secret store is never touched. Use it for headless/CI machines,
custom secret managers, restoring a store on a new machine, or booting while
the platform store is unavailable.
Security
This MCP is the highest-trust component in your Claude stack because every WhatsApp message you receive flows through it. See SECURITY.md for the threat model, tool risk-tier classification, and the full list of hardening decisions.
Short version:
- Bridge binds to
127.0.0.1only, never0.0.0.0 - SQLite encrypted at rest with SQLCipher; key stored in the platform secret store (macOS Keychain / Windows Credential Manager / libsecret), with an explicit
WHATSAPP_DB_KEYescape hatch - Every tool call logged to
audit.logwith 30-day retention - Send tools require an explicit
confirm_sendstep between draft and delivery - Incoming message text passes through a prompt-injection scrubber before Claude sees it
whatsmeowpinned to a specific commit; upgrades require diff review- No telemetry, no external API calls by default
Status
v0.1.0, actively maintained.
Related MCP Servers
Reviews
No reviews yet — be the first to share how this listing worked for you.
Frequently Asked Questions about Personal WhatsApp MCP for Claude, built directly on whatsmeow
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
Badge Style:
Live Dynamic SVG Preview
Markdown (GitHub README)
[](https://allmcps.com/mcp/personal-whatsapp-mcp-for-claude-built-directly-on-whatsmeow)HTML Embed
<a href="https://allmcps.com/mcp/personal-whatsapp-mcp-for-claude-built-directly-on-whatsmeow"><img src="https://allmcps.com/api/badge/personal-whatsapp-mcp-for-claude-built-directly-on-whatsmeow?style=directory" alt="Personal WhatsApp MCP for Claude, built directly on whatsmeow on AllMCPs" /></a>Technical Specs & Signals
CategoryCommunication
11/15 checks healthy over the last 45d
40Quality signal: Fair · 40/100How this signal is calculated ▾
Server availabilityNot measured
Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.
Verified ownership10/20
Documentation & tools16/30
Adoption & activity4/15
Community engagement0/10
A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.
Supply-chain signal
No high-severity advisories surfaced by our automated scan.
Critical 0High 0Medium 0Low 0
Scanned 6d ago via OSV.dev · adelaidasofia-whatsapp-mcp (PyPI)
Own this project?
This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.
Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.
Claim & get free dofollowShare & Embed
Add our SVG badge (dark/light directory styles) or embeddable widget to your site.