There's a moment most people who automate WhatsApp hit eventually. You've connected Claude to your chats, you've watched it read a thread and draft a reply, and it feels like magic — until you ask it to send something tomorrow morning and it just... can't. It sends now or not at all.
That gap is the whole reason this article exists. Reading and sending is the easy half of WhatsApp automation. The half that actually saves you time is timing: the follow-up that goes out at 9am while you're still asleep, the reminder that fires the day before an appointment, the customer batch that drips out over an hour instead of all at once. This guide is about closing that gap — telling Claude, in plain English, to schedule WhatsApp messages and run paced campaigns from your own number, without writing a line of code.
Why connect WhatsApp to Claude at all
If you live in WhatsApp for work, the friction isn't typing — it's context-switching. You think of a message you need to send Thursday, and you either send it now (wrong time) or you make a mental note (which you'll forget). Connecting WhatsApp to an AI assistant like Claude turns that thought into an action without leaving the conversation you're already in.
The plumbing that makes this possible is MCP, the Model Context Protocol — the open standard Anthropic introduced in late 2024 that lets an AI model call external tools through a shared interface. A WhatsApp "MCP server" is a small program that exposes WhatsApp actions as tools Claude can call. Once it's connected, you don't click around an app. You say what you want, and Claude figures out which tool to call.
For non-technical operators, that's the appeal: it's AI-ops without the "ops." No dashboards, no integrations to wire up, no scripts. Just a chat window where "schedule a WhatsApp to Dana tomorrow at 9am" becomes a scheduled message.
What most WhatsApp MCP servers can't do
Here's the part nobody tells you when you search "WhatsApp MCP server" and find a dozen GitHub repos. Almost all of them only read and send.
The most popular open-source projects — the whatsmeow-based servers in Go, the Baileys-based ones in TypeScript — are genuinely good software. But look at their actual tool lists and you'll find the same shape every time: search contacts, list chats, read messages, send a message, maybe download media. That's it. There is no "schedule for later." There are no campaigns. There are no reusable audiences with per-contact personalization. If you want a message to go out at a specific future time, the open-source servers simply don't have a tool for it.
On top of the missing scheduling, most of them need a developer to stand up. You're installing a Go toolchain or a Python environment, running a local bridge process, scanning a QR code into a terminal, and keeping that process alive on your own machine. The moment your laptop sleeps, the assistant loses its connection to WhatsApp.
So the real gap isn't "can an AI touch WhatsApp" — plenty of tools clear that bar. The gap is "can I tell an AI to schedule and pace WhatsApp messages without being a developer." That's a much shorter list.
For the full landscape of what's out there — official Cloud API servers, the open-source projects, and the trade-offs between them — see our comparison of the best WhatsApp MCP servers. This article is about the one capability that comparison singles out as unique: scheduling and campaigns from Claude.
What the Blueticks MCP exposes to Claude
The Blueticks MCP is built around the actions that the read-only servers leave out. Alongside reading and sending, Claude gets tools for:
- Scheduling. Send a message at a future time, then list, reschedule, or cancel anything you've queued — all in plain English.
- Campaigns. Schedule a paced bulk send against a list, with pause, resume, and cancel controls, so you're not firing hundreds of messages in one burst.
- Audiences. Build reusable contact lists with per-contact variables like
{firstName}and{product}, so a campaign message personalizes itself for each recipient.
Everything runs through the same engine that powers Blueticks' scheduling and campaigns inside the app — so the scheduling Claude triggers is the same first-class scheduling Blueticks has always done, just driven by a sentence instead of a form. (If you want the manual, in-app version, that's covered in our guide to scheduling WhatsApp messages.)
One thing to be clear about up front: this runs over your own WhatsApp number via WhatsApp Web — the same unofficial transport Blueticks' extension uses — not Meta's official Cloud API. That has real consequences (we'll get to the honest limits below), but the upside is that there's no Meta Business verification, no number provisioning, and no per-template approval queue. It's the number you already use, sending messages that look exactly like you typed them.
Connecting Blueticks to Claude
Setup is two pieces: get your WhatsApp number connected to Blueticks, then add the MCP to Claude. Both are quick, and neither needs code.
Link your number. Before Claude can schedule anything, Blueticks needs a live connection to your WhatsApp. This is the same link step the product uses everywhere else — you connect your existing, already-active WhatsApp account to the Blueticks engine by scanning a QR code, the way WhatsApp Web works. If you're already using Blueticks to schedule messages, you're done with this step. If you're starting fresh, the Blueticks Chrome extension is the simplest on-ramp to get connected.
Add the MCP to Claude. Blueticks publishes a hosted MCP server you connect with a single entry in your Claude config. You'll need a Blueticks API key (created from your Blueticks API dashboard), and then you add a small server block that runs the @blueticks/mcp package with that key in the environment. The package pulls itself on first run — there's nothing to clone, compile, or keep alive on your machine. Restart Claude, and the WhatsApp tools appear.
I'm describing this at a level you can rely on rather than walking you through every keystroke, because the exact menu and file paths differ between Claude Desktop, Claude Code, and other MCP clients, and they evolve. The current, version-correct setup steps — the config block, where the file lives on your OS, and how to mint an API key — live in the official Blueticks developer docs. Follow those for the precise commands.
Once it's connected, a good first test is simply to ask Claude whether your WhatsApp is connected. If the engine is linked, it'll confirm — and you're ready to schedule.
Telling Claude to schedule a message
This is the payoff. With the MCP connected, scheduling is one sentence:
"Schedule a WhatsApp to +1 415 555 0134 tomorrow at 9am: 'Morning Dana — confirming our call at 2pm today.'"
Behind that sentence, Claude does a few things in order. It first checks your current date, time, and timezone, so "tomorrow at 9am" resolves to the right moment instead of the server's clock. It drafts the message and shows it to you. And once you approve, it queues the send for that exact time.
The queue is fully conversational after that. Ask "show me my scheduled WhatsApp messages" and Claude lists what's pending. Change your mind with "reschedule the message to Dana to 11am" or "cancel it," and it updates or removes the queued send. You never open a calendar, a form, or the app.
The everyday version of this is the follow-up you'd otherwise forget. You finish a call, and instead of making a mental note, you say: "schedule a WhatsApp to this client Friday at 10am asking if they've had a chance to review the proposal." Done, off your mind, fires while you're doing something else.
Telling Claude to run a paced campaign or follow-up drip
Scheduling one message is useful. Scheduling the same message to a list — without machine-gunning it out all at once — is where the campaign tools earn their place.
Say you want to let a group of customers know about early access. You can tell Claude:
"Create an audience called Early Access with these numbers, then run a campaign to them: 'Hi {firstName}, early access opens Monday — want me to reserve your spot?'"
Claude builds the reusable audience, attaches the per-contact variables, and schedules a paced campaign against it. The {firstName} token resolves per recipient, so each person gets a message addressed to them, not a generic blast. And because it's a campaign rather than a loop of individual sends, it goes out spread over time, and you keep pause, resume, and cancel control by just asking for it: "pause the Early Access campaign," "resume it," "cancel it."
That same pattern is how you'd build a light follow-up drip — a first message now, a nudge scheduled for a few days later to anyone who hasn't replied. You're orchestrating it in conversation, but the actual delivery is handled by the same paced engine Blueticks uses for campaigns in the app.
What it can't (and shouldn't) do
I'd be doing you a disservice if I left it at the happy path. A few honest limits:
This is not Meta's official Cloud API. It runs over WhatsApp Web with your own number — an unofficial transport. That's what makes it no-code and free of per-template fees, but it also means you're operating under WhatsApp's normal anti-abuse rules, not inside a Meta-blessed business channel. Using third-party automation on WhatsApp can put a number at risk if you abuse it. If you need Meta-verified, high-volume, template-based business messaging, the Cloud API is the right tool, not this.
No per-template or per-message Meta fees — with an asterisk. You're not paying Meta's conversation-based pricing because you're not using Meta's billed channel at all. That's a genuine cost saving, but it's not "free messaging" at WhatsApp's layer — it's "no Meta template billing." Don't read it as unlimited.
Pace yourself, especially at first. Don't blast hundreds of messages in seconds, and don't message people who never opted to hear from you. Start with a small batch, watch that it's delivering cleanly, then scale up. The campaign tools exist precisely so you can pace; use them. No one — not Blueticks, not any unofficial tool — can promise zero ban risk, so behave like a careful human.
Claude acts on your instruction, not on its own. This is not an always-on autonomous agent that decides to message people for you. It schedules and sends when you tell it to (or when you set up a campaign that runs on a schedule you defined). The control stays with you, and the draft-before-send step is there so nothing leaves your account without your say-so.
Free vs Pro. On the Free plan, single scheduled messages are limited to one at a time and sends carry a "Powered by blueticks.co" footer — though Free can still run bulk campaigns. Pro removes the branding and adds offline sending so you don't need WhatsApp Web open. Worth knowing before you build a workflow around it.
FAQ
Can Claude actually schedule a WhatsApp message for later, or only send now? It can schedule. With the Blueticks MCP connected, you can ask Claude to send a message at a future time, and then list, reschedule, or cancel anything you've queued — all in plain English. This is the capability the popular open-source WhatsApp MCP servers don't have.
Do I need to know how to code? No. You add one server entry to your Claude config and create an API key — there's no toolchain to install, no repo to clone, and nothing to keep running on your machine. The WhatsApp session runs on Blueticks' hosted engine. The current step-by-step config lives at dev.blueticks.co.
Does it send from my own number? Yes. It runs over your own connected WhatsApp account via WhatsApp Web, so recipients see a normal message from you, not from a third party. You link your number once by scanning a QR code, the way WhatsApp Web works.
Is this the official WhatsApp Business / Cloud API? No. It's an unofficial WhatsApp Web integration on your own number. That's what keeps it no-code and free of Meta's per-template fees, but it also means you're under WhatsApp's normal usage rules. For Meta-verified, high-volume template messaging, use the official Cloud API instead.
Will scheduling from Claude get my number banned? Not if you behave like a human. Risk rises sharply with cold outreach and high volume, and stays low for messaging people who expect to hear from you. Pace bulk sends through campaigns, start small, and don't message strangers. No unofficial tool can promise zero risk.
Can it run a follow-up drip automatically? You can schedule a first message and a later nudge, and run paced campaigns with pause/resume/cancel control. It acts on the schedule and campaigns you set up — it's not an autonomous agent that messages people on its own.
Schedule your first WhatsApp from Claude
The open-source WhatsApp MCP servers stop at reading and sending. The thing that actually saves you time — telling an AI to schedule a message for 9am tomorrow, or to drip a personalized campaign out over the next hour — is the part they can't do. Blueticks' MCP is built around exactly that, no terminal required, from the number you already use.
Connect your number, add the MCP to Claude, and try the one sentence that started this article: "schedule a WhatsApp to someone tomorrow morning." The full setup and your API key are at dev.blueticks.co.
