Meta has opened WhatsApp Business account setup to AI coding agents, publishing a WhatsApp Business Tools MCP server that lets Claude Code, Claude Desktop, OpenAI's Codex app and ChatGPT register phone numbers, author message templates and configure webhooks without a developer touching the Meta dashboard. The server is in beta and rolling out gradually.
Key takeaways
- The server exposes 18 tools at the remote endpoint mcp.facebook.com/whatsapp_business_tools over Streamable HTTP, grouped into discovery, phone onboarding, templates, messaging, webhooks and account setup.
- Agent access is scoped to the specific businesses a developer selects and runs on three OAuth permissions: business_management, whatsapp_business_management and whatsapp_business_messaging.
- It is the second MCP surface Meta has shipped in three months, following the June release now branded Meta Social Technologies MCP.
What the server lets an agent do
The tools, all namespaced with a whatsapp_biz_ prefix, cover the full arc of getting a business onto the platform. An agent can list the businesses, accounts and phone numbers a developer administers, then add a new number, trigger a verification code by SMS or voice, and register the number for sending once the developer reads that code back.
From there the same conversation can create, inspect, update and delete message templates, configure the callback URL that receives inbound events, subscribe the account to webhook topics, and fire a test message to confirm the wiring works. Account-level chores are included too, such as attaching payment details and generating system user tokens.
The practical target is the setup slog. Onboarding a retailer today means bouncing between Meta's account settings, the API reference and a code editor to connect a number, verify it and get events flowing. Meta product marketing lead Zoรซ Lieberman framed the pitch as describing an outcome and letting the agent handle the accounts, numbers, templates and API calls behind it.
Why message templates matter here
The template tooling is what keeps the server useful after launch day. WhatsApp opens a 24-hour customer service window whenever a customer messages a business, and each new inbound message restarts the clock. Inside that window a business can reply freely; outside it, reaching the customer generally requires a template Meta has already approved.
That rule turns template management into recurring work rather than a one-off. The MCP tools let a developer ask for a marketing template carrying a coupon or a utility template for order updates, complete with header, body, footer and buttons, then revise it from the same session. When a free-form send would fall outside the window, the agent is meant to flag the problem and offer an approved template instead.
The guardrails Meta put around it
Meta's permission model leans on the human in the loop. Connecting an agent does not hand it every Meta asset attached to a developer account โ the developer picks which administered businesses are in scope, and can review or revoke the grant from Business Integrations in Facebook settings. Lieberman described the boundary in the announcement:
Every read runs under your own viewer context, every invocation is logged, and anything that changes state requires an authenticated person rather than an app-level credential.
Sending a message also carries a confirmation step, and local-only MCP clients have to reach the endpoint through the mcp-remote bridge rather than a stdio transport.
How it fits Meta's wider agent push
This is not Meta's first agent-facing developer surface. In June Meta shipped Developer Tools MCP, since renamed Meta Social Technologies MCP, which lets an agent discover Graph API endpoints, search documentation and debug an app. The two overlap but sit at different altitudes: the older server is for building integrations, the new one for operating WhatsApp Business itself. Lieberman's guidance is to install both if a project needs both.
The commercial stakes are real. Paid messaging on WhatsApp crossed a $2 billion annual run rate in the fourth quarter of 2025, CFO Susan Li told investors on Meta's January earnings call, and anything that shortens time-to-first-message feeds that line directly.
What to watch next
Beta status is the caveat worth holding onto: Meta says the interface and tool set may change, and the rollout is staggered. The broader pattern is what protocol watchers have been tracking all year, as MCP's own roadmap has shifted toward long-running agent sessions rather than one-shot calls. A server that walks a business through SMS verification and then manages its templates for months is exactly that shape of workload.
FAQ
Which AI clients can use the WhatsApp Business Tools MCP?
Meta's documentation lists Claude Code, Claude Desktop, the OpenAI Codex app and ChatGPT. All four connect to the same remote HTTP endpoint, and clients that only support local servers can bridge to it with mcp-remote.
Is the WhatsApp Business Tools MCP generally available?
No. Meta labels it a beta and says it is rolling out gradually, so it may not appear for every developer immediately. The company also warns that the interface and the tool set itself are subject to change.
Can an agent message real customers through it?
Yes, but with limits. The messaging tools send template or free-form text from a registered number and require a confirmation step, and free-form sends outside WhatsApp's 24-hour customer service window are blocked in favour of an approved template.
