Meta has released an MCP server that hands the setup of WhatsApp Business messaging to an AI agent. A developer who previously had to move between several Meta tools and services to get a company onto the platform can now describe what is needed to the coding agent of their choice and let it carry out the steps. The server, WhatsApp Business Tools MCP, connects that agent directly to the WhatsApp Business Platform.
The agent takes over most of the technical work. It creates the company's WhatsApp Business account, adds and verifies its phone number, registers that number for Cloud API access, checks the business terms of use, and performs the other actions setup requires. A company can also describe the message template it wants and have the agent build it, or ask the agent to modify a template that already exists.
The monitoring is the more revealing part. The agent can test messages and webhooks and track three operations that Meta says could previously fail without anyone noticing: the terms of use check, the payment method, and business verification.
This is an expansion of a set Meta already runs. The company previously offered MCP servers for managing ads and controlling app settings, and has now added one for connecting a business to WhatsApp. During setup and configuration, developers can also call a second Meta server, Meta Social Technologies MCP, which the company says helps locate API endpoints, search the documentation and resolve errors.
Meta is joining a list rather than starting one. PayPal, Stripe, GitHub, Notion, Slack, Salesforce, Atlassian, X, Google and Microsoft all expose their services to agents through MCP servers.
Read that silent-failure list again, because it says more about WhatsApp Business than the launch does. Terms of use, payment method, business verification: three gates a company could fail without being told. That is not an exotic edge case, it is the spine of onboarding, and the fix arrived as a monitoring feature attached to an agent rather than as a fixed flow. This reads less like a new capability than like a patch for friction Meta has been living with long enough to know exactly which three things break.
Notably absent from the announcement is any account of authority. Creating an account, verifying a phone number and clearing a terms of use check were, in the pre-agent version of this process, things a person did and a person answered for. Meta says what the agent can now do and nothing about what a verification performed by software acting on a developer's prompt is worth, or who is accountable when it turns out to have been performed on the wrong company.
The distribution logic is the real point. Whoever occupies the agent at the moment a developer decides which messaging platform to wire up wins the integration, and Meta has now put WhatsApp there. The cost of that position is that identity, billing and verification — the parts of a business platform that exist precisely to establish who someone is — are now steps a model executes on request.