The Pulse
Meta Lets AI Agents Set Up WhatsApp Business Accounts
Meta introduced WhatsApp Business Tools MCP, connecting Claude, Cursor, Codex and ChatGPT to WhatsApp Business setup workflows. The system can create accounts, verify phone numbers, manage templates and test webhooks through an authenticate
AI.info Team ·
Meta is handing AI coding agents access to the administrative work behind WhatsApp Business messaging. The company announced WhatsApp Business Tools MCP on September 15, connecting agents such as Claude, Cursor, Codex and ChatGPT directly to the WhatsApp Business Platform.
The system is designed to replace a setup process spread across Meta’s Developer Console, Business Manager, API documentation and a code editor. Developers can describe the business messaging configuration they need, then let an authenticated agent carry out supported account and testing tasks.
Meta’s announcement is available in its developer blog.
From phone verification to Cloud API registration
WhatsApp Business Tools MCP can create a WhatsApp Business Account, add and verify a phone number, register that number for the Cloud API and check whether the business has completed required Terms of Service steps.
Phone verification still depends on the human-controlled number. Meta sends a one-time code by SMS or voice, and the developer provides that code to the agent before the number can be verified and registered. The agent therefore performs the workflow, but the account remains tied to a person’s authenticated access.
Meta says users sign in through Facebook Login for Business and grant specific permissions. Account changes require an authenticated person rather than an app-level credential, limiting the agent’s authority to the businesses and permissions selected during setup.
Templates and webhooks move into the same conversation
The MCP server also covers recurring work after onboarding. A developer can describe a message template, ask the agent to create it, or request changes to an existing template. The agent can report the template’s approval status as part of the workflow.
Testing tools cover both outbound messages and webhooks. Developers can configure callback URLs and field subscriptions, send test messages and check whether the WhatsApp integration responds as expected. Meta also says the system can surface problems involving payment methods, Business Verification and Terms of Service requirements that might otherwise remain unnoticed.
“You describe what you want — your agent handles the accounts, numbers, templates, and API calls,” Zoë Lieberman of Meta writes in the company’s announcement.
Meta separates documentation help from account actions
WhatsApp Business Tools MCP is not Meta’s only developer-facing MCP server. Meta Social Technologies MCP provides broader support for finding Graph API endpoints, searching documentation, inspecting application configuration and troubleshooting errors.
The two tools serve different purposes. Meta Social Technologies MCP helps an agent understand Meta’s developer platform and investigate problems; WhatsApp Business Tools MCP gives it WhatsApp-specific operations for accounts, numbers, templates, webhooks and test messages. Meta recommends using both when a project needs platform guidance as well as WhatsApp configuration.
That distinction matters because the WhatsApp server can perform state-changing operations. An agent that can create an account or modify a template has more authority than one that only retrieves documentation, making permission scope and human authentication part of the product design rather than an afterthought.
Beta access comes with a narrower promise
Meta is rolling out WhatsApp Business Tools MCP gradually, and the interface remains in beta. Availability can differ by agent and account, while the tools themselves may change as Meta expands or revises the service.
The release is aimed at development and testing workflows, not at replacing the WhatsApp Business Platform as a production messaging system. Businesses still need their own application logic, approved messaging templates, webhook handling and operational controls once an integration moves beyond testing.
Meta’s move gives coding agents a direct route into one of its most commercially important developer products, but the immediate change is narrower than an autonomous customer-service system. Agents can now perform much of the setup and validation work; people still authorize the account, provide verification codes and decide which businesses the agent may change.