Meta lets Claude and Codex configure WhatsApp Business via MCP
The New Stack Paul Sawers ● Covered by 2 sources
Meta now lets Claude and Codex set up WhatsApp Business through MCP. That could save devs from juggling Meta settings, docs, webhooks and code.
Based on reporting by The New Stack, Paul Sawers — read the original for the full story.
Summary, retelling and take written by AI under human oversight; images are AI-generated illustrations. How we work · Report an error
Meta is handing a chunk of WhatsApp Business setup to AI coding agents. The new WhatsApp Business Tools MCP server lets developers connect agents like Claude or Codex, sign in with a Meta account, pick which businesses the agent can access, and then have it do the setup work directly.
That matters because WhatsApp is already a serious business channel. Meta’s CFO Susan Li said paid messaging on the app hit a $2 billion annual run rate in the fourth quarter of 2025. But the setup has been messy enough to keep developers bouncing between account settings, API docs and code just to get a phone number verified, webhooks wired up and the integration running.
Meta says the agent can handle the onboarding pieces in plain English: add a business number, create the WhatsApp account behind it, and take the one-time verification code sent by SMS or voice. It can also work with message templates, which are required once the 24-hour customer service window closes and a business wants to reach out again. That means marketing promos, order updates and other approved messages can be created, listed, revised or deleted from the same conversation.
The useful part is that this does not stop at setup. The agent can send test messages, flag when a free-form message would be blocked outside the 24-hour window, and configure the webhook that routes incoming replies into a CRM, support tool, chatbot or order system. It can also inspect account settings, including whether payment information is missing for billable messages.
Meta says the guardrails are built in. The agent works under the access of the person who connected it, actions are logged, and anything that changes state needs an authenticated person rather than an app-level credential. This is also not Meta’s first MCP play: in June it launched Developer Tools MCP, later renamed Meta Social Technologies MCP, which covers the broader developer stack. The new server is narrower and more operational, and Meta says it is rolling out gradually while still in beta.
My take — AI-written commentary, not fact-checked reporting
This is the sensible kind of AI automation: boring, specific, and actually useful. The industry has spent years pretending “agentic” meant magic; here it mostly means fewer tabs and fewer copy-pasted codes, which is a lot more honest. Open or closed doesn’t matter much when the real prize is getting businesses hooked into the plumbing.
Read more about this at: The New Stack