You can hand ChatGPT your WhatsApp. It reads your threads, tells you who is still waiting on a reply, drafts the answer, and sends it from your own number.
What nobody tells you on the way in: it only works while something on your side holds a live WhatsApp session. If that something is a browser tab, it stops the second you close the laptop. This guide is written around that fact instead of hiding it in a footnote.
Can you connect WhatsApp to ChatGPT?
Yes. Add a remote MCP server as a plugin in ChatGPT developer mode. Two things must be true first: developer mode is available on your account, and a WhatsApp engine is connected and stays connected while ChatGPT works.
- ChatGPT developer mode - turn it on in Settings before anything else.
- A live WhatsApp engine - browser tab or always-on gateway, your choice.
- The connector URL -
https://api.blueticks.co/mcp, with the/mcppath. - The invoke surface - the Work tab, not the normal Chat tab.
That is the whole shape of a whatsapp mcp chatgpt setup. ChatGPT runs the Model Context Protocol client, Blueticks runs the server, and the server exposes WhatsApp actions as tools ChatGPT can call. If the protocol layer is new to you, the WhatsApp and MCP primer covers the architecture first.
What has to be true before you start
Two prerequisites, and one of them disqualifies most people who try this on a whim. A WhatsApp engine has to be connected for ChatGPT to read or send anything at all, and developer mode has to be available on your ChatGPT account. Check both now, in that order.
Your WhatsApp engine has to be connected, and stay connected
ChatGPT does not talk to WhatsApp. It talks to a server, and that server drives a WhatsApp session you own. No live session, nothing for ChatGPT to drive.
The behaviour is not vague. When a tool call arrives and no engine is online for the account, the Blueticks API answers 503 Service Unavailable with No WhatsApp engine is connected for this account. ChatGPT surfaces that as the tool failing. It does not queue the message for later, and it does not tell you your laptop is asleep.
There are exactly two ways to be connected, and they behave very differently:
| Browser extension on WhatsApp Web | Hosted always-on gateway | |
|---|---|---|
| Where the session runs | Your browser tab | Blueticks infrastructure |
| Laptop closed, browser quit | Session ends, tools fail | Keeps running |
| Good for | Working hours, at the desk | Overnight sends, scheduled follow-ups, anything you are not present for |
Say it plainly: the extension dies when the tab closes. Shut your laptop at 18:00, ask ChatGPT from your phone at 22:00 to send a reminder, and the extension path fails while the gateway path works. That single difference decides whether this is a toy or a tool. First-time connection is a QR scan either way, documented in the Blueticks guides. One limit if you run both at once: WhatsApp caps a standard account at four linked devices — more on a Meta Verified account — and each session counts.
ChatGPT developer mode has to be available to you
MCP servers are added in developer mode, and developer mode is not guaranteed to be there. OpenAI's own wording, in the plugin connection docs, is exactly this:
"Developer mode availability can depend on account and workspace policy."
That is from OpenAI's connect-and-test guide, and it is the only statement on gating worth repeating. OpenAI does not publish a plan list there, so anyone naming tiers is guessing. Open Settings, look under Security and login, and see whether the toggle exists on your account. On a work account an admin can switch developer mode off, which makes it an ask for them, not a setting you can win. Fifteen seconds now, or a wasted evening later.
How to connect WhatsApp to ChatGPT in four steps
Turn on developer mode, add the Blueticks MCP server URL at chatgpt.com/plugins, install the plugin from your personal plugins directory, then switch the ChatGPT homepage tab from Chat to Work and invoke it with @. Four screens, no terminal, no config file, about five minutes.
Step 1: turn on developer mode
In ChatGPT, open Settings, select Security and login, and turn on Developer mode. That path is straight from OpenAI's documentation. Everything in a chatgpt developer mode mcp setup hangs off this toggle. Without it there is nowhere to paste a server URL.
Flag for anyone cross-checking against another article: most competing guides still send you to Settings → Connectors → Advanced settings. That path is stale. OpenAI renamed the Apps SDK to Plugins, and developers.openai.com/apps-sdk now answers 301 and redirects to developers.openai.com/plugins. If your guide says Connectors, it predates the rename and the rest of its click-path probably drifted too.
Step 2: add the Blueticks MCP server
Go to chatgpt.com/plugins and select the plus button. Enter a name and description you will recognise in a tool list, like "Blueticks WhatsApp". Under Connection, choose the public endpoint option and enter the MCP server URL, including the /mcp path:
https://api.blueticks.co/mcp
The path is not decoration. https://api.blueticks.co on its own is not an MCP endpoint and the connection will not come up. OpenAI's build guide describes the expected shape as a streamable HTTP endpoint "typically at /mcp", streamable HTTP being the current transport, introduced in protocol revision 2025-03-26 to replace the HTTP+SSE transport from 2024-11-05. None of that is yours to configure. You just need the path on the URL.
Create the connection. A Blueticks sign-in screen appears, you sign in, and you land back in ChatGPT. Review the tools ChatGPT discovered. You should see nine. If you see zero, jump to the troubleshooting section.
Step 3: install it from your personal plugins
Creating the connection does not install it. Open your personal plugins at chatgpt.com/plugins?view=personal, find the plugin you just created, open it, and select the plus button to install. This is the step people skip: the plugin exists, the tools were discovered, and it still does nothing in a chat, because it was never installed.
Step 4: switch to the Work tab and invoke it
Return to the ChatGPT homepage. At the top, switch the tab from Chat to Work. Start a new Work chat, type @ in the prompt box, and pick your plugin. That sequence is OpenAI's documented quickstart flow, not a workaround.
Test with something read-only before you let it send anything: "list my five most recent WhatsApp chats". If chats come back, the chatgpt whatsapp connector is live end to end. If you get a tool error, your engine is almost certainly offline.
Which WhatsApp tools does ChatGPT get?
Nine, exposed by name. ChatGPT sees audiences, campaigns, chats, contacts, engine, groups, scheduled_messages, utils and webhooks. You never call them by name yourself. You describe the outcome and ChatGPT picks the tool.
chats- read and send inside conversationsscheduled_messages- send now or schedule for latercontacts- look up who is whogroups- create and manage WhatsApp groupsaudiences- reusable contact lists for bulk sendscampaigns- paced bulk delivery, with pause and cancelwebhooks- get an HTTPS callback on eventsengine- check connection state, log out, reloadutils- date and time, phone validation, link previews
Two things worth knowing. engine is what to reach for when you suspect the prerequisite has broken: ask "is my WhatsApp engine connected?" and it answers with the live state instead of making you guess. And ChatGPT sees the same nine tools Claude sees. The server does not hand ChatGPT a smaller menu; the difference between the two setups is the client, not the capability. Depth on the scheduling tool lives in the scheduling-from-MCP guide.
What can you actually ask it to do?
Three requests that pay for the setup on day one: triage the unread pile, answer one thread properly, and put a follow-up on the calendar so you stop carrying it in your head. Each maps to a tool without you naming it.
"Which WhatsApp conversations from the last two days are waiting on a reply from me?" This lands on chats. You get a triaged list instead of a scroll. Reading is the part that eats the morning, not typing, so triage pays for the whole setup before you ever send whatsapp from chatgpt at all.
"Reply to Dana: the quote is going out Thursday, and ask if she wants the extended warranty line included." Also chats. Read the draft, correct the tone in plain language, then let it go. It leaves from your number and lands in your sent messages like anything you typed by hand.
"Remind me to chase the Kaplan invoice next Tuesday at 09:00, and send them a nudge at the same time." This lands on scheduled_messages, and here is the gotcha: a scheduled send needs an engine at fire time, not at schedule time. Schedule it from a browser tab, close the laptop, and Tuesday 09:00 arrives with nothing to send through. Same trap in any WhatsApp follow-up automation you build on this.
Why isn't it working?
Four causes, in the order they actually occur. Diagnose before you change anything: ask ChatGPT "is my WhatsApp engine connected?" first, because that one question resolves the most common failure and rules it out for the other three.
- Your engine is offline. By far the most likely. Symptom: tools are listed, every call fails. The tab closed, the laptop slept, the session dropped. Reconnecting the plugin fixes nothing. Re-link your number, or move to the always-on gateway so it stops recurring. A session in a browser tab follows ordinary WhatsApp Web behaviour: it ends when the tab does.
- Developer mode is unavailable or admin-disabled. Symptom: no toggle in Settings, or it vanished after a policy change. Nothing on the Blueticks side is involved. OpenAI states availability depends on account and workspace policy, so this is a conversation with your admin.
- The URL is missing the
/mcppath. Symptom: the connection never comes up and no tools are discovered. People pastehttps://api.blueticks.coand stop. Open the plugin's connection settings and add the path. - You are in the Chat tab, not Work. Symptom: everything looks installed, and typing
@does not offer the plugin. Switch the homepage tab to Work and start a new chat. An existing Chat-tab conversation will not pick it up.
If the tools were discovered once and then went stale after a server-side change, the plugin's connection page has a Refresh action that re-reads the advertised metadata.
ChatGPT or Claude: which should you connect?
Functionally, a coin flip. Both clients reach the same nine tools on the same server, so neither can do something to your WhatsApp the other cannot. Pick on where you already work, not on capability.
The honest split is ergonomic. ChatGPT keeps MCP servers behind developer mode and puts plugin use in the Work tab: more clicks up front, cleanly separated afterwards. Claude surfaces connectors in its main settings, which is fewer clicks to first use. The Claude side has its own screens and its own page, so read how to connect WhatsApp to Claude rather than adapting this one. Nothing here transfers except the prerequisite, which is identical.
What this is not
Four honest limits, and they matter more than any step above. This is not the first WhatsApp MCP server, not Meta's Cloud API, not risk-free for your number, and not a substitute for having permission to message someone.
Not the first, and not the only one. Open-source WhatsApp MCP servers predate this and deserve the credit. lharries/whatsapp-mcp pairs a Go bridge built on whatsmeow with a Python MCP server; jlucaso1/whatsapp-mcp-ts does it in one Node process on Baileys. Both are self-hosted, both work, and other hosted vendors exist in this field too. The comparison lives in the WhatsApp MCP server roundup, not here.
Your own number, not the Business API. This drives your existing WhatsApp account over WhatsApp Web or a hosted gateway. No template approval queue and no Cloud API per-message pricing, and equally none of the Cloud API's guarantees: no Meta-sanctioned delivery contract, no business verification, no Meta support path.
Nobody can promise your number is safe. Automating a personal WhatsApp account carries real risk, because unauthorized automated or bulk messaging violates WhatsApp's Terms of Service and Meta enforces it. Read-and-reply on existing conversations sits at the low end, cold outreach at volume at the high end. Anyone selling a guaranteed no-ban setup is selling something they cannot deliver.
Consent is yours, not the tool's. ChatGPT will happily draft two hundred first-contact messages. Whether those people agreed to hear from you is your responsibility alone.
One last disambiguation, because a phrase brings people here by mistake. If you searched for an openai whatsapp integration meaning the other direction, calling the OpenAI API from a WhatsApp Business number so a bot answers your customers, this page is not that. That build uses Meta's Cloud API or a provider on top of it, a separate business number, pre-approved templates and per-message billing. Real thing to build, completely different thing. For where ChatGPT itself stands on WhatsApp as a product, read ChatGPT on WhatsApp.
When ChatGPT can't reach your number, none of this happens
Every step above assumes a live WhatsApp session. Remove it and the connector is a menu of nine tools that all return an error. The always-on gateway is what makes the rest of this page real, and it is the honest reason to pay for anything here.
Put it the way it actually bites. The plugin is rarely the problem. The problem is that you close your laptop at six and your clients message at nine — nothing is broken, and nothing is connected either.
That is the whole product argument. A browser tab gives you WhatsApp automation during office hours. A hosted gateway parks the session on infrastructure that does not sleep, so a 22:00 request from your phone actually leaves your number.
Stop losing sends to a closed laptop. No Meta developer console, no template approval, no per-message fees. Connect your own number to an always-on engine, then let ChatGPT read and send on it whether you are at your desk or not. Get an always-on WhatsApp engine.
FAQ
Does ChatGPT have a WhatsApp connector?
Not a built-in one. You add WhatsApp yourself by connecting a remote MCP server as a plugin in ChatGPT developer mode. Blueticks serves that endpoint at https://api.blueticks.co/mcp, and once installed ChatGPT gets nine WhatsApp tools.
Can ChatGPT send WhatsApp messages for me?
Yes, from your own number, once the connector is installed and a WhatsApp engine is connected. You ask in plain language, ChatGPT calls the chats or scheduled_messages tool, and the message leaves your account. It fails if no engine is online.
Do I need ChatGPT Plus to add an MCP server? OpenAI says only that "Developer mode availability can depend on account and workspace policy" and does not publish a plan list. Ignore any article that names tiers. Open Settings, look under Security and login, and check your own account.
Does this use the WhatsApp Business API? No. It drives your existing personal WhatsApp account over WhatsApp Web or a hosted gateway. There is no Meta Cloud API involved, so no template approval and no per-message pricing, and also none of the Cloud API's guarantees.
Will my computer need to stay on? With the browser extension, yes. Close the tab and every ChatGPT tool call fails. With the hosted always-on gateway, no: the session runs on Blueticks infrastructure and keeps working overnight, which is what an always-on engine is for.
