Meta announced today it will allow AI coding agents to handle much of the setup required for businesses to operate on WhatsApp, using a new WhatsApp Business Tools MCP server that connects with agents like Claude or Codex. According to a blog post from Meta, the tool aims to transform what would otherwise be a series of separate API tasks into something users can request in plain English. Paid messaging on WhatsApp crossed a $2 billion annual run rate in the fourth quarter of 2025, Meta CFO Susan Li told investors on the company's January earnings call, but getting businesses properly configured on the platform remains a complicated process that sends developers bouncing between account settings, API documentation, and code editors.
The new server handles tasks including connecting and verifying phone numbers, configuring webhooks, managing message templates, and sending test messages. A developer can connect the MCP server to an agent, sign in with their Meta account, and select which businesses they administer the agent can access—access is limited to those specific businesses rather than giving the agent control across every Meta account linked to the developer. The agent can then add a phone number and set up the WhatsApp account behind it when given the number and display name the business wants to use. Meta sends a one-time verification code by SMS or voice, and once the developer provides that code to the agent, the number becomes verified and registered for sending messages. The agent also manages message templates, which become necessary once WhatsApp's 24-hour customer service window closes—a rule designed to prevent businesses from converting old customer threads into channels for unsolicited messages.
"You describe what you want—your agent handles the accounts, numbers, templates, and API calls," writes Zoë Lieberman, who works on product marketing at Meta, in the Tuesday announcement. The report explains that when a customer messages a business, it opens a 24-hour window during which the business can respond with free-form messages, and each new message from the customer restarts that clock. After the window closes, businesses generally must use a Meta-approved message template to contact that customer again. According to the post, the agent can create marketing templates offering customers coupons or utility templates for order updates, and templates can include headers, body copy, footers, and buttons. From the same conversation, the person using the agent can list existing templates, retrieve a particular version, update it, or delete it, and the agent can flag when a free-form message can't be sent and offer an approved template instead.
Meta says actions performed through the MCP are recorded and the agent operates using the access of the person who connected it. "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," Lieberman writes. That approach keeps the agent acting only within the authenticated user's existing access, making permissions bounded by a known human account and sensitive changes easier to attribute and control—a contrast with some companies pushing toward giving agents their own scoped, revocable identities, such as Vercel's recent acquisition of Better Auth, Microsoft's Entra Agent ID, and Amazon Bedrock AgentCore Identity. The report notes this isn't Meta's first effort to make its developer tools accessible to AI agents—the company launched Developer Tools MCP in June, later rebranded as Meta Social Technologies MCP, which operates across Meta's developer platform including WhatsApp Business API integrations. The two tools are complementary, with Meta Social Technologies MCP serving as the broader developer tool for discovering Graph API endpoints and troubleshooting errors, while WhatsApp Business Tools MCP focuses specifically on operating WhatsApp Business accounts.
Meta says the new WhatsApp server is rolling out gradually and may not be available to everyone immediately, while the interface and tools remain in beta and subject to change. The company writes that developers should install both tools if they need both. Agents working across enterprise communication platforms may soon need to master not just the technical protocols of message delivery, but the compliance boundaries and business logic that govern when and how companies can speak to their customers.