CommsConnector
Read your own WhatsApp conversations and reply as yourself in Claude or ChatGPT, through a hosted linked-device session, with no QR script to run yourself.
Official site: www.whatsapp.com
What it can do
2 read/1 send
- 01Read
List your 100 most recent conversations and read a thread
- 02Send
Send a message, or reply in an existing thread
- 03Read
Summarize a thread you have read
The connector links your own WhatsApp account as a linked device, the way WhatsApp Web does, and the session runs on a hosted browser instead of your laptop. Your phone stays the master of the account. If you unlink the device there, the session ends, the card goes back to unconnected, and any workflow leaning on it stops.
It is neither the WhatsApp Business API nor a shared bot number. It is your account, acting as you.
Is there an MCP for WhatsApp?
Yes, in two families. The first links a personal account. Open-source servers such as lharries/whatsapp-mcp do it with a QR code scanned into a script you run and keep alive yourself. The second is Meta's own WhatsApp Business Tools MCP server, which Meta documents as a beta for managing a WhatsApp Business integration. Its endpoint is in the table below. Tulina's connector belongs to the first family, with the session hosted for you.
How do you connect WhatsApp to Claude and ChatGPT?
Through Tulina's MCP server, in three steps:
- In Tulina, add the Unipile account connector, with your own subscription key or the platform's hosted messaging option granted by an admin. Unipile is the provider that holds the linked-device session.
- Open the WhatsApp connector and choose Connect my WhatsApp account. You link it like WhatsApp Web, with nothing to paste and no extension.
- Add
https://mcp.tulina.ai/mcpto Claude or ChatGPT and sign in with your Tulina account. The MCP page has the same link.
Tulina vs Meta's WhatsApp Business Tools MCP server
They do different jobs. Meta's server administers a Business integration, and Tulina's reads and answers a personal account.
| Meta's Business Tools MCP | Tulina | |
|---|---|---|
| Endpoint | mcp.facebook.com/whatsapp_business_tools | mcp.tulina.ai/mcp, one link for every connected tool |
| Sign-in | OAuth with a Meta developer account, choosing the businesses and apps it may use | Your WhatsApp account, linked as a device |
| Account | A WhatsApp Business account and its registered phone numbers | Your own number |
| What it does | Onboards numbers, manages message templates, configures webhooks, sends messages | Lists conversations, reads a thread, sends a message |
| Needs | Admin access to a business and to a WhatsApp-enabled app, and the Cloud API terms accepted | A phone with WhatsApp, and a Unipile connection |
| Personal chats | Meta's page does not describe reading them | Yes, the threads on your account |
If you run a business integration with templates and webhooks, Meta's server is the one built for it. The Tulina connector fits a person who wants an assistant that can read their own threads and answer from their own number.
What you can ask it
"Read my latest WhatsApp conversations and tell me which ones are waiting on me." The agent lists up to 100 recent threads, newest first, reads the ones that look open, and tells you which end on an incoming message.
"Summarize the thread with Marc since Monday." The agent finds the thread, reads its messages and summarizes the period you named. The read returns the thread's messages and the summary is the model's work, so a long thread is read in pieces.
"Reply to Marc: let's meet Thursday at 2pm." The agent sends into the existing thread. A send leaves at once from your number and there is no draft step, so it is worth asking to see the text first.
Telegram, Instagram and Messenger work the same way for their own inboxes, and Gmail covers mail.
What the WhatsApp connector can't do
- It lists at most 100 threads per call. Unipile does not paginate WhatsApp, so an older thread is reached by its id and not by scrolling the list.
- A message whose photo, voice note or poll Unipile did not pass on comes back marked as unavailable. Its content is unknown, not empty.
- It does not use the WhatsApp Business API, templates or webhooks.
- It sends direct messages, and a send has no draft or undo.
- It depends on the phone. If the device is unlinked there, the session dies and workflows stop.
- Reads and sends are separate tools, so an organisation can allow reading without allowing sending.
- The session is held by Unipile, our provider, for the account you link.
Why through Tulina
The connection was never the hard part.
Most systems now publish their own way for a model to reach them, and that is good: it is what Tulina connects to. The hard part is deciding who may use it, what it is allowed to return, and what the model knows before it asks.
The keys stay in one place
YouTeamOrganisation
Connect WhatsApp once. The credential is encrypted in a vault, never held in clear, and never pasted into a chat or a workflow file. A person uses their own key where they have one, their team's where they do not, the organisation's after that, so nobody is blocked and nobody holds more access than they need. Revoke it once and everything running on it stops.
What leaves is filtered before it leaves
fields droppedmasked or hashedpseudonymised
Roles decide who can reach WhatsApp at all. Beyond that, a policy on the connector itself decides what comes back. The data is minimised at the source rather than after it has already reached a model.
Every call is on the record
whatwhowhen
Runs are logged for the organisation. That is what makes an automated action reviewable after the fact, and it is what a security review asks for first.
The run starts knowing your company
namingkey accountsdecisions
A direct connection gives a model access. It does not tell it how your company names things, which accounts matter, or what was decided last quarter. Tulina carries that across every tool, so the same request against WhatsApp returns something usable instead of something generic.
Processes that run on WhatsApp
None published yet.