Show HN: WhatsApp MCP running free on Cloudflare (github.com)
I wanted my humble Claude on mobile to access my WhatsApp messages but the only options I could find either required WhatsApp Business or an actual server to run Baileys on.
I wanted to run it for free on ClaudeFlare and with my personal WhatsApp account, so I built this.
Important feature - it connects to your Google account as well as WhatsApp to grab the names of all your WhatsApp contacts, otherwise you get only phone numbers for many of them and search doesn't work properly.
This is a single user install because it's both gray area and very private - so point your agent at the repo and let it set things up.
101 comments
[ 2.8 ms ] story [ 19.0 ms ] threadIt's always been a possibility that when you sent an email to someone their provider could be building an ad profile on you. Any third party tool someone else uses to manage their personal files and communications could always have some arbitrary privacy policy that let them do what they see fit.
For the most part, you never know what random SAAS someone on the other end of a relationship is really using.
Imagine someone puts all the Signal messages someone else sent them through an AI. I dunno. I think problem is most AI doesn't work like Confer.to, also by Signal's founder.
The entire concept of conversations being "secure" is only as good as your ability to trust the other party isn't doing something insecure with them (and that yours and their devices are, themselves, as secure as you think they are. Which they generally aren't.)
All of which is to say, it's security theater and always has been when applied to real life situations.
Yes, and that's exactly why E2EE messaging became a thing. Signal put it on the map through the WhatsApp integration.
To me there is a difference if the server spies on me (that's without E2EE) or if the person I am writing to leaks everything on the Internet.
If the person you're writing to leaks everything on the Internet, you should consider you are talking to them in public. I'm sure you don't say all the same things when you are in the metro or when you are in private, or do you?
Pretty much never for email. Maybe some people go out of their way to perform PGP but that's usually only for the most secret of information and sometimes not even for that.
FWIW the only thing I've used PGP for in many years is encrypting my home address when buying darknet drugs
- Most people are not in Signal
- I have friends that want utmost privacy and shun me for using Android and buy iPhone etc but then install Google Maps. Add my name/address/email/phone etc to google sync.
- Worse - many employers are using FAANG for services. How many managers are uploading Excel sheets? Who supervisors them?
- Even if I keep every thing locally (which I don't ) finally govt will lose their passport database and ...
Whatsapp uses the Signal protocol for E2EE: https://signal.org/blog/whatsapp-complete/
So yeah, whatsapp messages are E2E encrypted and therefore can not be used as training data unless you upload them to the cloud manually, as this project does
https://www.bloomberg.com/news/articles/2026-04-28/us-ends-i...
So what? WhatsApp is end-to-end encrypted. Signal is better (e.g. because the client is open source), but security is a gradient. WhatsApp is better than Telegram in terms of security.
> but then install Google Maps
Again, it's a gradient. Sure, they leak some data, but at least they don't leak all the content of all their messages. Or would you say that if you leak your name on the Internet, you may as well publish your sextape because "now everybody knows your name, you have nothing to hide anymore"?
> How many managers are uploading Excel sheets?
So because my company leaks my work documents to Microsoft means that I should leak the content of the messages I send to my partner? How do you get to that conclusion?
> finally govt will lose their passport database and ...
Right. And it is a known fact that when the government loses their passport database, suddenly your private pictures appear on the public Internet! /s
But LLM agents are really useful and the tools to give one access to your entire digital life is just an OAuth prompt away.
https://news.ycombinator.com/item?id=43901204
* Unless you want to go into a conspiracy theory that all the Meta employees can see the source code and nobody has ever felt like whistleblowing about the backdoor Meta put into WhatsApp, that is.
Its still preferable to use Signal since now it actually supports numberless registration. Hopefully they will actually fee payable not via credit card at some point.
It's preferable to use Signal because they don't collect as much metadata as WhatsApp, and the client is open source.
I don't care so much about the numberless registration. Actually I don't even understand why people care so much about it.
Don't forget that metadata is not encrypted, so Meta know who you are writing to, who writes to you, who your contacts are, all the usage pattens of the app, and more metadata (not sure if it's still the case, but a few years ago WhatsApp even uploaded the battery state of your phone to Meta).
Not like Meta is a saint...since they're competitors
but it's an MCP, so that also means it'll be more token-verbose than an API, which means your local agent hardware is going to chug a bit.
i have reached the point of just using LLMs to build my own API servers and tooling like search, and teach the LLM how to use those APIs, rather than MCPs.
What about… nothing. Nothing. A friend screenshotting an E2EE message is NOT even in the same world of trouble as an agentic automation over all their conversations.
But email… nope. Stop. A single person passing group chats to Claude will compromise the few hundred people in our parenting WhatsApp community.
I have a similar setup for my personal agent, except all inference runs on my local homelab and open weight models.
I see no ethical qualms to this. These people sent messages to me, and only I have access to it; I’m not sharing it with a third party.
The world always worked like this though, as soon as "data" is shared out from your head to the wider world, it has "leaked" and can no longer be considered secret. This was as true 100 years ago as it is today. The only secrets that can be kept, remains the ones you keep inside of your head and don't share with others.
Even if you do connect to an AI company, you could also limit the blast area by using a control layer to limit the scopes, for example I built this so I can grant individual WhatsApp chats but not all of them: https://github.com/ju-li/automata-mcp
Open clients like Telegram make a lot more sense. WhatsApp is at the whim of Zuck's and whoever is ruling US's political inclination on what is allowed or not.
That is not a great way to run a country. US corporations in many ways are like worms.
If a bot needs to text me it sends an API request or it can read whatever I allow with full visibility as I have the logs and limit the access.
The amount of effort was minimal. About 4 prompts to get it all working and zero SaaS, 3rd party, or purchases after the software was built.
Every now and again I sketch out an automatic iPhone backup over wireless workflow so I can extract the WhatsApp conversations once a day - which may be a good usability/tos-safety trade-off - but that may or may not be worth it.
Do you know if running Whatsapp in Cloud risks your account to be banned?
I'm working on a similar tool, connecting all that data to build your context graph that knows all the people and conversations and expose it via MCP. https://lobu.ai/for/personal/
My approach is requiring you to have a home device where you keep your accounts open in a browser and observing the data from there. The same applies to Linkedin, Instagram, X etc. even reading my timeline to summarize what I need to know without me doomscrolling.
When that happens it immediately cuts your access and makes you request a reconsideration that can take 24+ hours. Some accounts get booted without this option. So if you use Whatsapp for anything important that can be a really big problem. I was reinstated, and only discovered this from going through a couple of cycles trying to add these back.
So doing what you are doing with this seems almost like a guarantee that you will be perma banned.
> […] default CPU limit on Workers is too small for it. wrangler.jsonc raises it, and raising it needs the paid plan, which is a few dollars a month. I haven't tried the free plan.
https://github.com/finereli/whatsapp-mcp/tree/64f1b3017931e4...