WhatsApp MCP
A local-only MCP server giving Claude guarded read and reply access to WhatsApp.
A Go whatsmeow bridge plus a Python MCP server that reads chats and builds per-client context, with no cloud involved.
- Local-only, no cloud relay for private chats
- Go whatsmeow bridge plus Python MCP server
- Builds per-client CONTEXT documents from history
- Guarded reply capability rather than unchecked autonomy
A local-only MCP server that gives Claude read access to WhatsApp plus a guarded ability to reply. A Go bridge built on whatsmeow connects to WhatsApp, while a Python MCP server exposes the tools to Claude. From chat history it can assemble per-client CONTEXT documents — useful for keeping track of what each client has asked for and agreed to.
Everything runs locally, with no cloud relay, so private conversations stay on the machine. The reply path is guarded rather than fully autonomous, reflecting a consistent stance across my agent work: read freely, but act deliberately. In practice this lets me keep an accurate, per-client record of requirements and commitments without manually digging back through months of chat, while private conversations never leave the machine because there is no cloud relay anywhere in the path.