Source: github.com/finereli/whatsapp-mcp
The server acts as a linked device rather than keeping a constant connection. It connects once a day and whenever an agent asks for data, collects queued messages, and stores them in a SQLite database inside a Durable Object in the owner's Cloudflare account. Media is kept only as labels such as [image], and nothing is transcribed.
The tools include list_chats, get_messages, search_messages, unnamed_chats, set_contact_names, sync_now, link_status and relink. Read tools refresh from WhatsApp first when the stored copy is more than ten minutes old. For chats known only by phone number, the agent can match numbers against a contacts tool it already has and save the names.
The README says the project is not official. It uses the protocol WhatsApp Web uses, through the open source Baileys library, and the author states this goes against WhatsApp's terms. The headline's free claim needs a caveat: the author says large imports need the Workers Paid plan, which costs a few dollars a month, and the free plan has not been tested.
Why it matters if you build agents
Agent developers get a working example of giving an agent private chat history through MCP, with the data kept in the owner's own account. Before relying on it, check the README's warning about WhatsApp's terms and the Workers Paid requirement. The project is built for one owner reading their own account, and it does not cover sending messages.
Get stories like this every weekday
One short email with the day's agent tooling news.