A developer has released a free server that lets artificial intelligence agents read and search WhatsApp conversations within a personal Cloudflare account. The project, called WhatsApp MCP, is hosted on Cloudflare Workers and uses the open-source Baileys library to interface with WhatsApp Web's protocol. It does not send messages or alter WhatsApp's functionality, and operates solely as a read-only bridge.

The server runs as a single Durable Object in the user's Cloudflare account, storing message history in a SQLite database. It connects to WhatsApp only once daily to fetch newly queued messages, then disconnects immediately. Users link their phone to the server via a QR code scan, similar to WhatsApp Web pairing, after which any MCP-compatible AI client can query the stored messages.

Key capabilities include full-text search across all chats, filtering by date or participant, and retrieving message excerpts. The system preserves message metadata but does not download media files, displaying them only as labels like [image] or [voice note]. Unnamed chats appear as phone numbers until an AI agent cross-references them with local contacts and assigns names via a dedicated tool.

Security considerations are noted: the implementation uses an undocumented WhatsApp protocol and violates WhatsApp's terms of service, though the developer emphasizes it is intended for personal use only. The server requires a Cloudflare Workers Paid plan for initial large-scale history imports due to CPU limitations on the free tier. A free-tier workaround may exist but carries reliability risks.

Setup involves creating a Cloudflare account, deploying the code via npm, and configuring authentication through a password or email link. Once deployed, users connect their AI agent using a command like `claude mcp add --transport http whatsapp https://<url>/mcp`, then authenticate to access the message database. The system does not support sending messages and is designed for single-account use only.

The project highlights growing interest in AI-enhanced messaging workflows, though it relies on reverse-engineered protocols and carries inherent technical and compliance trade-offs. Users must manage their own deployment and understand the limitations around message completeness and contact identification.