Too lazy
WhatsApp AI assistant · WhatsApp MCP
A ChatGPT-style assistant and an MCP endpoint for your own WhatsApp number
You bring your own gateway and your own number. Your messages sync into a private workspace only you can read. The assistant and MCP layer are what early access is for — request a spot below.
Live todayread-only inbound message sync into your own private workspace.
Early accessthe AI assistant and the MCP endpoint — not built yet, no date promised.
Notethis runs on a self-hosted gateway you control, not Meta's Business API; automating a personal WhatsApp account can put that account at risk under WhatsApp's terms.
Self-hosted WhatsApp gateway
How it works
Connect your own gateway
You run your own Evolution API instance holding your own WhatsApp number. We never hold your number and never ask for your WhatsApp password or Meta approval.
Messages sync to your private workspace
Inbound messages are imported read-only. The incoming webhook is treated as untrusted — the message content is re-read from your own gateway's API before anything is stored.
Add the assistant and MCP layerearly access
The layer you are requesting access to: a ChatGPT-style assistant over that synced history, and an MCP endpoint so an AI agent can work with it. Not shipped yet.
Private WhatsApp assistant
What exists, and what does not
- live
Read-only inbound sync
Messages come in and are stored in your workspace; there is no send or compose screen anywhere in the product today.
- live
Your own number, your own gateway
The gateway instance is yours. Nothing routes through a shared business number, and no Meta Business API approval is involved.
- live
Webhook payloads are never trusted
An inbound webhook only tells us something happened. The actual message content is re-read from your gateway's API, so a forged payload cannot write data.
- live
Workspace isolation with row-level security
Every stored record is scoped to your workspace and enforced at the database with row-level security, not just in application code.
- early access
ChatGPT-style assistant
An assistant that can answer over your own message history. Not built yet; this is what the request form is for.
- early access
MCP endpoint
A Model Context Protocol endpoint so your own AI agent can reach your WhatsApp context. Not built yet; requesting access adds you to the list.
MCP endpoint for WhatsApp
What a WhatsApp MCP endpoint would do
MCP — Model Context Protocol — is an open standard for exposing a data source to an AI agent as a set of tools it can call. A WhatsApp MCP endpoint would let an agent you already use ask things like "find the thread where we agreed the delivery date" or "summarise what I missed in this chat this week" without you copying anything into a chat window.
Plainly: this does not exist yet. There is no MCP server in the product today. This section describes what early access is for, so you can tell us whether it is worth building and what you would point at it.
ChatGPT on WhatsApp alternative
Questions people actually ask
Is this an official WhatsApp product?
No. This is not affiliated with, endorsed by, or connected to WhatsApp, Meta, or OpenAI. It works with your own WhatsApp number through a gateway instance you run yourself. All product names mentioned belong to their respective owners.
Do you read my messages?
No. Messages are stored inside your own workspace and isolated at the database level with row-level security, so they are only readable by your account. There is no shared inbox and no cross-customer access.
Is the AI assistant available now?
No. What is live today is read-only inbound message sync into your private workspace. The ChatGPT-style assistant and the MCP endpoint are not built yet, and we are not promising a date — that is what early access is for.
What is a WhatsApp MCP server?
A WhatsApp MCP server exposes your WhatsApp data to an AI agent as callable tools using the open Model Context Protocol, so the agent can search or summarise your conversations without a human copying text across. Several open-source implementations exist; the one described on this page is planned, not shipped.
Does it use ChatGPT?
Not today — nothing here is connected to ChatGPT, and OpenAI's own ChatGPT integration for WhatsApp was withdrawn in January 2026 after a Meta policy change. "ChatGPT-style" describes the kind of assistant being planned, not the model behind it. Which model it uses is one of the things early access will decide.
What do I need to get started?
Your own WhatsApp number and your own self-hosted Evolution API gateway instance holding it — no Meta Business API approval is required. One caution worth stating plainly: WhatsApp's terms prohibit unofficial clients on consumer accounts, and accounts automated this way have been permanently banned. Use a number you can afford to lose.
WhatsApp AI assistant on your own number
Request early access
Tell us what you would point this at. Early access is small and manual — you will get a real reply from a person, not an automated drip sequence.
Request received. You are on the list — we will email you before anything ships, and we will not add you to anything else.
Enter an email so we can reply.
That email doesn't look right — check for a typo.
That is a lot of requests from here in a short time. Wait a minute and send it once more.
That didn't send. Try again — nothing was saved.
We use what you send here only to contact you about early access. No newsletter, no sharing, no selling. Ask us to delete it any time.