WhatsApp Is Where My Life Happens. So I Put It Inside My AI Assistant
AI Coding · 5 min read

WhatsApp Is Where My Life Happens. So I Put It Inside My AI Assistant

Long story short, I created wuzapi-mcp. It is open source, public, MIT, free, and I’m using it every day. I started it on 26 October 2026 because I use WhatsApp heavily, and because the thing I wanted simply was not there.

For me WhatsApp is the ultimate channel. If you write me there, it has the maximum importance. My family writes me there. I’m a heavy WhatsApp user, voice notes included. And I found it super frustrating that Claude, which I use every day, or even ChatGPT, could not just read and act on my WhatsApp.

This is the part that annoyed me. WhatsApp passed 3 billion monthly users at the end of April 2025, and in October 2025 about nine in ten internet users in Italy used WhatsApp, with Spain, Portugal, Germany, and the UK not far from that same reality (Statista). So we have this channel that basically everybody around me uses, but my assistant was blind there. So I built the missing door.

The problem with “official”

There are two WhatsApps. There is personal WhatsApp, the free one, the one normal people like me use every day, and there is the WhatsApp Business Platform, the official API for companies. Personal WhatsApp has no API at all. The business one exists, but you pay per message.

Since 1 July 2025, Meta charges on the Business Platform by message category: marketing, utility, authentication templates, and service messages inside the 24-hour window after a customer writes (pricing). Service messages had been free since November 2024, but from 1 October 2026 Meta charges them again, with the first 1,000 per phone number per month still free, and utility messages inside the window too. So yes, if you have a business number, that is a completely different topic.

And then there is the other thing. Since 15 January 2026, the Business API terms bar general-purpose AI assistants; ChatGPT, Copilot, and Perplexity left WhatsApp, and Meta AI is the only general-purpose assistant inside WhatsApp (TechCrunch). Fine for Meta, I guess. But nothing there lets my assistant read my WhatsApp. The official road goes in the opposite direction from what I needed.

I tried the old thing, then built my own

I started from WuzAPI, an open-source REST API for WhatsApp based on whatsmeow, and I use it as is. I was also inspired by lharries/whatsapp-mcp, which is popular, about 6,900 stars, but its code has not changed since July 2025. It was not stable or maintained, and it lacked things I wanted: reactions, webhooks, an integrated login.

So I built my own version from scratch on top of WuzAPI. It links to your WhatsApp as a linked device, like WhatsApp Web: you scan a QR code, and that’s it. Messages are archived locally in SQLite, with full-text search, and it can pull up to a year of history from the phone.

If you are not familiar with MCP, I wrote a no-BS guide here: MCP, Skills, Commands, Agents. In practice, for this project, MCP is the layer that lets Claude Code, Claude Desktop, Gemini CLI, Codex, Cursor, VS Code, or another MCP client talk with your WhatsApp tools. It is a wrapper, yes, but a very useful one. The result is boring in the best possible way: it works.

What I actually use it for

When I’m driving, instead of asking Siri, which, you know, makes no sense, I can ask Claude to do way more stuff on WhatsApp. Just in the last week, I asked it to create a poll. I asked it to create a group for the birthday of my youngest, invite all the people, and summarize what was happening there.

There are about 40 tools. It can read and search chats, send messages, files, and voice notes, add reactions, create polls, show poll results, including who voted what and who has not voted, create groups, add people, create invite links, and manage group settings. Voice notes are transcribed to text.

I also use it while coding. Some customers still prefer to write me on WhatsApp, but I don’t want to stop what I’m doing and reply from the phone. So I have an agent that retrieves that information, and even replies or reacts there for me. It’s not like the agents I built for a client, which talk to customers on the paid business side: this one is mine, on my own number. The useful part is simple: my assistant finally sees the channel where real life happens.

How to install it, and hosted mode

To install it locally, you need Docker, but you do not need to build anything. There is a prebuilt Docker image, and it is basically three commands on Mac, Windows, or Linux. Honestly, you can also ask Claude Code to install it for you, and it figures it out.

I also run mine on my own VPS because I want WhatsApp to live and breathe without re-authenticating all the time. In hosted mode, you run it on your own server behind HTTPS, with a passphrase login only you know, and then the claude.ai apps — web, phone, and from the phone even the car — can use it as a connector. I documented that in the hosted mode guide.

There is no cloud version run by me, and I have not decided to create one. The reason is simple: I do not want to hold other people’s conversations. Those are your communications: your family, your customers. If I ever did one, it would be encrypted. For now, the cleanest version is: run it yourself, own your data, use it every day.

The warnings, because yes, there are warnings

Just to be clear, this is not an official WhatsApp API. The same limits apply as for anyone using WhatsApp. If you send thousands of messages, WhatsApp can restrict or burn your number, and it does not matter if you typed very fast on the keyboard or asked an assistant to loop.

Use it on your own account, at a human pace. Also remember that messages are untrusted input. Anyone can write instructions inside a WhatsApp message, so keep confirmation on for sending, especially if you connect it to an assistant that can act.

It’s the same pattern I used for Gmail and Calendar: give my assistant the door, keep the key. Useful, yes. Blind trust, no.

The repo is here again: wuzapi-mcp. If you have questions, open an issue, send me a message, do whatever you want. I’m happy to show you how it works. I will support it because I use it, and because I want this thing to keep working. WhatsApp is where my real conversations already are; I just wanted my assistant to stop waiting outside the door.

Sources

← All writing