Verifying a WhatsApp number by MCP relays Meta's one-time code through the agent's chat

The verification step is the one part of the path that still needs a person. Meta sends a one-time code to the number by SMS or voice, the developer gives that code back to the agent, and the number is then verified and registered for sending ^[5]. The code therefore passes through the agent conversation. Whoever hosts that session is in the verification path for a phone number the business is about to publish ^[19].

Meta handled consent better than it needed to. The developer signs in with a Meta account and picks which of the businesses they already administer the agent may reach, and access is scoped to that selection; connecting does not hand the agent every Meta account attached to the login ^[4]. Within a selected business, the same connection that inspects the account also changes it ^[13]. The announcement describes selection at the level of businesses. Meta did not mention a read-only mode.

WhatsApp's own messaging rule keeps this server useful after launch. When a customer messages a business, it opens a 24-hour customer service window for ordinary free-form replies, and each new message from the customer restarts that clock ^[7]. Once the window closes, reaching that customer generally requires a template Meta has approved ^[8]. The agent can create a marketing template, such as a coupon, or a utility template for order updates, with a header, body copy, footer and buttons ^[9].

From the same conversation the developer can list templates, pull up a particular version, update it or delete it ^[10]. Deletion is the one to think about, because a replacement has to go through Meta's approval again ^[18]. The agent can also send a test message, and if the recipient is outside the window it flags that a free-form message cannot be sent and offers an approved template instead ^[11].

Webhook routing comes down to a single destination field, now editable from the same chat. The agent can configure where WhatsApp delivers incoming messages and other events, whether that is a CRM, a support platform, a chatbot or an order-management system ^[12].

I would connect the inspection tools first. According to mezha.net, the agent helps surface errors that went unnoticed when checking payments, terms of use or business verification status ^[14], and Meta's own example is asking whether the business is missing payment information ^[13]. Those misconfigurations present to the operator as messages that do not send. Meta has a second server, Meta Social Technologies MCP, for finding API endpoints, working with documentation and diagnosing technical errors ^[15].

There is a demand number under all of this. Susan Li told investors on Meta's January earnings call that paid messaging on WhatsApp crossed a $2 billion annual run rate in the fourth quarter of 2025 ^[16], which works out at roughly $500 million booked in the quarter ^[17]. Meta earns that money on messages businesses already send. The case for the MCP server rests on the other cost, which mezha.net describes as switching between the developer console, Meta Business Manager, the API documentation and the template editor ^[3]. Zoë Lieberman, who works on product marketing at Meta, wrote that "your agent handles the accounts, numbers, templates, and API calls" ^[6].