WhatsApp MCP
Connect your agent to WhatsApp for encrypted chat access, safe draft-and-confirm sends, optional voice transcription, and Obsidian CRM folder injection.
Overview
whatsapp-mcp is a MCP server for the Grow phase that connects AI agents to WhatsApp through an encrypted local bridge with draft-and-confirm sends and optional voice transcription.
What is this MCP server?
- SQLCipher-encrypted local store plus scrubber-CI gating before sensitive operations
- Draft-and-confirm send flow so agents do not blast messages without human approval
- Voice-note transcription via WHATSAPP_WHISPER_BACKEND: local-cpp (default) or openai-api
- Go bridge REST API on WHATSAPP_BRIDGE_HOST and WHATSAPP_BRIDGE_PORT (default 127.0.0.1:8080)
- Optional WHATSAPP_VAULT_CRM_PATH for auto-injecting threads into an Obsidian CRM folder
- Server version 0.1.1
- Default bridge 127.0.0.1:8080
- Default Whisper backend: local-cpp
What problem does it solve?
Founders live in WhatsApp for customers but agents lack a safe, encrypted way to search threads, draft replies, and log CRM notes without sending by mistake.
Who is it for?
Indie operators who self-host the Go bridge, want SQLCipher-backed storage, and need human-in-the-loop WhatsApp drafts from Claude Code.
Skip if: Teams needing official WhatsApp Business Cloud API SLAs, fully unattended bulk campaigns, or zero local bridge maintenance.
What do I get? / Deliverables
After install, your agent can work through the bridge with scrubber-gated tools, confirm outbound drafts, transcribe voice notes, and optionally mirror contacts into Obsidian CRM paths.
- stdio MCP tools for WhatsApp read/draft workflows behind scrubber gates
- Configurable voice transcription and optional CRM folder writes
Recommended MCP Servers
Journey fit
Customer and lead conversations compound in the grow phase; this MCP sits on support and lifecycle workflows once the product exists and you answer WhatsApp daily. Support is the right shelf for messaging bridges that help founders reply, log threads, and avoid reckless auto-sends—not for core app backend code.
How it compares
Self-hosted WhatsApp MCP with safety gates, not the Meta Cloud API console or a generic SMS skill.
Common Questions / FAQ
Who is whatsapp-mcp for?
Solo builders and small teams who use WhatsApp for customers and want MCP agents to assist with encrypted local data and confirmed sends only.
When should I use whatsapp-mcp?
Use it in grow and support workflows when you already run or can run the Go bridge and need agent-assisted inbox search, drafts, transcription, or Obsidian CRM injection.
How do I add whatsapp-mcp to my agent?
Install via uvx from PyPI (identifier adelaidasofia-whatsapp-mcp v0.1.1), start the Go bridge on WHATSAPP_BRIDGE_HOST:WHATSAPP_BRIDGE_PORT, set optional CRM and Whisper env vars, then register the stdio MCP server in your client.