Your AI Agent Can Now Set Up WhatsApp Business — Up to a Point

TL;DR: On 15 September Meta released a tool that lets an AI coding agent — Claude and ChatGPT among them — do the fiddly setup for WhatsApp Business messaging: create the account, add and verify the number, register for the API, build message templates. It’s genuinely tedious work that now takes a conversation instead of an afternoon. But Meta is explicit that this release is “built for development and testing workflows, not production sending at scale”, and the approvals that actually gate you — business verification, template review, the code texted to your phone — still can’t be delegated to anything.

What Meta actually released

On 15 September 2026, Meta announced the WhatsApp Business Tools MCP — an MCP server, which is simply a standard way of handing an AI assistant a set of buttons it’s allowed to press on your behalf. In this case the buttons belong to the WhatsApp Business Platform.

In Meta’s own description, the agent “checks your Terms of Service status, creates a WhatsApp Business Account, adds your phone number, verifies it over OTP, and registers it for the Cloud API.” Five steps that have historically meant clicking between several different Meta dashboards.

It goes a bit further than first setup:

• Message templates — the pre-approved formats WhatsApp requires for business-initiated messages. The agent can draft new ones, edit existing ones, and track where they are in approval.
• Testing — it can send real test messages and configure webhooks, which is where hand-configuration usually goes wrong.
• Prerequisite checks — it flags what you’re missing up front, such as a payment method or incomplete business verification, rather than letting you discover it four steps later.

Meta says it’s “currently discoverable on Claude, Codex and ChatGPT”; TechCrunch reports Cursor works too. Authentication runs through Facebook Login for Business, and Meta notes that tokens never enter the prompt history — a sensible detail, given the usual alternative is pasting an access token into a chat window.

What no agent can do for you

This is the part worth reading before you get excited, and it’s the reason the honest headline has “up to a point” in it.

Meta’s own scope statement: “This release is built for development and testing workflows, not production sending at scale.” That is not a small caveat. If your plan is to start messaging customers next week, this tool is not the thing that gets you there.

And the real gates remain exactly where they were:

• The verification code still comes to a human. Meta sends a one-time code by SMS or voice, and a person has to read it out. An agent can drive the process right up to that point and no further.
• Business Verification is still Meta reviewing your business. Documents, a real company, a wait.
• Templates still face policy review. Your agent can write a beautiful message template. WhatsApp’s rules decide whether it’s allowed, and who wrote it makes no difference.
• You still need the boring prerequisites — a Meta Business account with admin access, accepted terms, and a payment method on file.

So the accurate summary is: the agent removes the tedium, not the gatekeeping. Which is genuinely valuable, as long as you know which one was costing you.

Why WhatsApp Business setup matters if you don’t code

Here’s why this is our story rather than a developer-tooling footnote.

A large number of people building something with AI tools aren’t building an app for its own sake — they’re running a small business and want customers to be able to message them. WhatsApp is the default way that happens in much of the world. And the reason many of them never get there isn’t the messaging: it’s the twenty-step API onboarding that sits in front of it.

That onboarding assumes you’re a developer. It uses words like “Cloud API”, “webhook” and “access token” without explaining them, spreads the process across several dashboards, and fails silently if you miss something. It is exactly the sort of task that stops a non-technical person dead — not because it’s hard, but because it’s opaque.

Handing it to Claude changes the shape of that problem in a specific way: you can now ask what’s happening at each step and get an answer, rather than guessing which dashboard you were supposed to be in. The agent also tells you up front what you’re missing, which is the single most useful thing about it.

There’s a wider pattern here too. Meta is exposing platform administration as something an agent can call — the dashboard becomes one way in rather than the only way. If that spreads, a lot of “I gave up during setup” moments quietly disappear across a lot of products.

How to try it (and whether you should yet)

1. Check you have the prerequisites first. A Meta Business account with admin access, WhatsApp Business terms accepted, and a payment method on file. No agent can conjure these.
2. Connect the MCP server in an agent that supports it — Claude, Codex or ChatGPT per Meta, or Cursor per TechCrunch. Authentication goes through Facebook Login for Business.
3. Ask it to check your status before asking it to do anything. “What’s missing before I can send a WhatsApp Business message?” is the highest-value first question, and it costs nothing.
4. Have your phone to hand. The OTP arrives by SMS or voice and you’ll need to read it out.
5. Treat this as a test setup, not a launch. Meta says development and testing. Believe them, and don’t promise a client WhatsApp messaging on the strength of a smooth afternoon.

Who should care about WhatsApp Business on MCP (and who shouldn’t)

• Running a small business and wanting customer messaging: you’re the person this helps most, with the caveat that you’re setting up to test, not to broadcast.
• Building an internal tool: relevant if notifications are part of it. The template rules are stricter than people expect — read them before designing around them.
• Building a revenue app with a messaging feature: useful for getting a working sandbox quickly. The production path is a separate, slower conversation with Meta.
• Just learning: honestly, skip it. This is plumbing for a specific platform, and there are better things to spend a weekend on.
• Not using WhatsApp for business: nothing here changes for you, and the wider “admin as agent-callable tools” trend is the only part worth filing away.

Our take

We like this more than we expected to, for an unglamorous reason: it targets the part that actually stops people.

Most AI tooling announcements aim at the interesting bit — generating the code, designing the thing, writing the copy. The reason a small business doesn’t have WhatsApp messaging is almost never that the interesting bit was too hard. It’s that step nine of the setup mentioned a webhook and they closed the tab. Automating the boring middle is a less exciting pitch and a more useful product.

What we’d push back on is any write-up that implies this gets you sending messages to customers. It doesn’t, and Meta says so plainly — development and testing, not production at scale. The gates that take real time are identity, verification and policy review, and every one of them is still a human decision by design. That’s appropriate; nobody should want an AI agent that can self-approve a business to message the public at volume.

So: a real reduction in busywork, an unchanged amount of gatekeeping. It’s the same discipline we applied when OpenAI stopped selling its top ChatGPT tier — work out what you were actually blocked on before reacting to the announcement. If the busywork was your blocker, this is a good week. If approval was your blocker, nothing has changed — and it’s worth being clear-eyed about which one you were actually stuck on, because the setup taking an afternoon was never the expensive part.

Not sure which tool fits what you’re building — or whether you need one at all? Take the 60-second Vibe Coding Tool Finder quiz →

FAQ