Developer builds free WhatsApp MCP connector for Claude on Cloudflare

By Splitfeed EditorialLast updated Oct 18, 2026, 22:50 UTC

On October 18, 2026, an independent developer posted a Show HN submission to Hacker News describing a self-built connector that links Claude to personal WhatsApp messages through the Model Context Protocol. The tool runs on Cloudflare Workers at no cost and uses a personal WhatsApp account rather than a WhatsApp Business account. Because WhatsApp's underlying library, Baileys, normally returns only phone numbers rather than contact names, the developer also wired in a Google account integration to pull contact names and make search usable. The stated motivation was wanting Claude accessible on mobile without paying for a dedicated server or signing up for a business-tier WhatsApp product.

The significance here is less about the technical novelty and more about what it represents in the broader pattern of MCP tooling. The Model Context Protocol is becoming a layer through which developers route AI assistants into personal data silos, and WhatsApp is one of the most heavily used private messaging platforms in the world. Bridging the two creates a genuinely useful workflow, letting an AI assistant read, search, and potentially act on a user's message history. The dispute centers on whether that convenience is worth the access it requires: the tool needs credentials for both a personal WhatsApp account and a Google account, meaning a single misconfiguration or security lapse could expose contact lists and message content.

None of the three camps have published specific reactions to this project yet. The Pro-AI camp would typically frame this as exactly the kind of grassroots, zero-cost innovation that demonstrates AI assistants becoming practically useful in everyday life rather than remaining confined to desktop browsers. The Anti-AI camp would typically point to the privacy surface created by handing a personal messaging account and a Google account to an AI pipeline as a concrete example of the data-access risks that critics have warned about. The Middle Ground camp would typically acknowledge the real utility while calling for clearer guidance on credential handling and the scope of data the tool can read or retain.

The practical question to watch is whether Meta takes any enforcement action against personal-account use of Baileys-based connectors at scale, since WhatsApp's terms of service restrict unofficial automation on personal accounts. Any policy response or terms update from Meta, or a security incident tied to a similar tool, would sharpen the debate considerably.