Too lazy
WhatsApp AI assistant · WhatsApp MCP server
Early access
The WhatsApp AI assistant for your own number
Ask your own chat history anything, in plain language. Too lazy turns the number you already use into a personal AI assistant — and hands the same context to your AI agent through a WhatsApp MCP server.
Early access. Inbound message sync runs today. The assistant and the WhatsApp MCP server open to early-access workspaces first — ask for a spot and we email you when yours is up.
WhatsApp GPT, on your own number
Ask your WhatsApp anything
Every message you have ever sent is already the best context you own. It is just unsearchable. An AI assistant that can actually read it turns four years of chat into something you can ask a question.
Find the thing you know you agreed
Ask for the message where the date, the price, or the address was settled. You get the quote and the thread it came from, not a scroll bar and a guess.
Catch up without reading 400 messages
Ask what changed in a chat this week and get the decisions, the open questions, and who is waiting on you — in the order they matter.
Stop losing the attachment
The invoice, the contract, the photo of the meter reading. Ask for it by what it was about, and your assistant surfaces the file and the message it arrived in.
Answer in your own words
Your history is the context. Drafts come back sounding like the way you already talk to that person, because that is the only material the assistant has.
WhatsApp MCP integration
The WhatsApp MCP server your agent connects to
MCP — the Model Context Protocol — is the open standard for handing a data source to an AI agent as a set of tools it can call. Too lazy speaks it for WhatsApp. Point Claude, your own agent, or anything else that acts as an MCP client at your workspace, and your chat history becomes a first-class tool call instead of a copy-paste job.
The search on the public web for a WhatsApp MCP server currently returns a handful of bare repositories you host, patch, and babysit yourself. This one is the managed version: your number, your gateway, your workspace, and an endpoint that is already scoped to you.
search_messages()
Full-text search across your synced threads, returning the message, the sender, and the timestamp — so the agent can quote instead of paraphrase.
summarise_thread()
A bounded summary of one chat over a window you pick, built for context budgets rather than for a wall of transcript.
list_chats()
The threads in your workspace with their last activity, so an agent can decide where to look before it reads anything.
find_attachment()
Attachments by what they were about, with the message that carried them. Invoices route on to the folder you already file them in.
WhatsApp automation, self-hosted
How the WhatsApp AI chatbot connects to your number
Connect the number you already have
You run an Evolution API gateway holding your own WhatsApp number. No Meta Business API approval, no business verification, and no shared broadcast number that makes you look like a marketing blast.
Your history syncs to a private workspace
Messages import into a workspace only your account can read, isolated at the database with row-level security. The inbound webhook is treated as untrusted: content is re-read from your own gateway before anything is stored.
Ask it things, or point an agent at it
Use the assistant directly, or connect an AI agent over the WhatsApp MCP server and let it call the tools itself. Same workspace, same isolation, same number.
Personal AI assistant
A personal AI assistant on the number you already use
- It already knows the context. No prompt library, no pasted transcript. The assistant starts from four years of your own conversations.
- It is yours, not a shared bot. One workspace, one number, row-level isolation. Nobody else is in your inbox and nothing is pooled.
- It works where you already talk. The number your family, your landlord, and your accountant already message. Nothing to migrate.
WhatsApp ChatGPT alternative
ChatGPT on WhatsApp, after OpenAI switched it off
OpenAI withdrew its ChatGPT integration for WhatsApp in January 2026 after a Meta policy change. The 1-800-ChatGPT number is gone, and the thousands of people who had quietly built it into their day got a shutdown notice instead of a replacement.
Too lazy is not that product coming back, and it is better than the thing you lost. A shared broadcast number could only ever answer general questions — it never knew a single thing about you, because it could not see your messages.
This runs on your own number and answers from your own history. Ask it what your plumber quoted, not what the average plumber charges. It is a WhatsApp AI chatbot with the one advantage a public one structurally cannot have: the context is already yours.
Before you close the tab
Straight answers to the obvious objections
- “I am not handing my private chats to a startup.”
- Nor should you, on trust alone. Your messages sit in your own workspace, isolated at the database with row-level security rather than by application code that could be got wrong. There is no shared inbox, no pooled index, and no cross-customer read path to misconfigure.
- “Another chatbot number I have to add and remember.”
- There is no new number. Too lazy connects the one you already use, through a gateway you run yourself — nothing to migrate, nothing to tell your contacts, and no broadcast account that makes your messages look like marketing.
- “I already have an AI agent. I do not want a second app.”
- Then do not use ours. Connect your agent to the WhatsApp MCP server and let it call search_messages and summarise_thread itself. The assistant and the MCP endpoint read the same workspace, so you pick the surface and keep the context.
- “Every WhatsApp MCP repo I found was a weekend project.”
- That is exactly the gap. The open-source servers hand you a clone, a config file, and a maintenance job. This is your number, your gateway, and an endpoint already scoped to your workspace — set up once, with a person on the other end during early access.
Questions people actually ask
WhatsApp AI assistant FAQ
Is this an official WhatsApp product?
No. Too lazy 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.
What is a WhatsApp MCP server?
A WhatsApp MCP server exposes your WhatsApp conversations to an AI agent as callable tools over the open Model Context Protocol, so the agent can search, quote, and summarise your threads without you copying text into a chat window. Too lazy runs that server against your own number and your own workspace, and it opens to early-access workspaces first.
Is this ChatGPT on WhatsApp?
It replaces it. OpenAI's own ChatGPT integration for WhatsApp was withdrawn in January 2026 after a Meta policy change, so the 1-800-ChatGPT number is gone. Too lazy is not ChatGPT and is not built on any single model — it is your own assistant, on your own number, answering from your own message history rather than from a stranger's chatbot.
Can anyone else read my messages?
No. Every message is stored inside your own workspace and isolated at the database with row-level security, so only your account can read it. There is no shared inbox, no cross-customer access, and the assistant answers from your workspace alone.
Is my WhatsApp account at risk?
It can be, and it is worth saying plainly. WhatsApp's terms prohibit unofficial clients on consumer accounts, and accounts automated this way have been permanently banned. Too lazy connects through a self-hosted gateway holding a number you control, not through Meta's Business API. Use a number you can afford to lose, and decide with that in front of you.
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, no business verification, and no shared broadcast number. Ask for early access and we will walk your workspace through the connection.
What does early access cost?
Nothing during early access. Pricing is not set, and we are not asking anyone for a card. Early-access workspaces are the ones whose use cases shape what ships first.
Your chat history is the best context you already own
Early access is small and hand-run. You tell us what you would ask it, we tell you exactly what your workspace can do — and a person replies, not a drip sequence.
WhatsApp AI assistant
Get early access
Tell us the number you would connect and the first thing you would ask it. That answer is what decides which tools ship next.
- One email when your workspace is up. Nothing else.
- No card, no pricing page, no trial clock.
- A person reads what you write in the last field.