Meta hands WhatsApp Business setup to Claude and Codex

Hand Claude a phone number and a display name, and it will stand up the WhatsApp Business account behind them, right up to the moment Meta sends a one-time code by SMS or voice and a person has to read it back. That is the WhatsApp Business Tools MCP server Meta announced Tuesday, as The New Stack reports, and it works with Codex too.

At a glance

• The WhatsApp Business Tools MCP server connects Claude or Codex to a developer's Meta account, scoped to the businesses they select, so the agent can add numbers, build message templates and set webhooks.
• A customer's message opens a 24-hour window for free-form replies, and each new message restarts it; after that the business needs a template Meta has approved.
• Rollout is gradual, the tools stay in beta and may change, and anything that changes state requires an authenticated person rather than an app-level credential, so the agent runs on the developer's own access.

If you have not been following the money side: 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. According to a Meta Ads changelog maintained by Ads Uploader, WhatsApp marketing messages became available in the Marketing API on 13 August. The setup work underneath all of that has stayed fiddly.

The agent runs the onboarding until Meta sends the code

Getting a business onto WhatsApp today sends a developer hopping between Meta's account settings, the API documentation and a code editor to connect and verify a number, configure webhooks and get the integration working. Some of that is a one-off; managing templates, testing changes and troubleshooting bring you back.

With the new server, a developer connects it to an agent, signs in with their Meta account, and picks which of the businesses they already administer the agent may touch. The access is scoped to that selection; connecting an agent does not give it free rein over every Meta account attached to the developer.

From there the number and the display name are enough for the agent to run the steps that add the number and create the WhatsApp account behind it. Meta sends the one-time verification code, the developer passes it back into the chat, and the number is verified and registered for sending.

Zoë Lieberman, who works on product marketing at Meta, wrote in the announcement post that the point is to collapse a string of separate API tasks into a plain-English request: "You describe what you want — your agent handles the accounts, numbers, templates, and API calls."

Why does the agent still matter once setup is done?

Because of templates, and templates exist because of a rule. When a customer messages a business, a 24-hour customer service window opens, and inside it the business can reply with ordinary free-form messages. Every new message from the customer restarts the clock. The rule is there to stop businesses turning an old conversation into an open-ended channel for unsolicited messages.

Once the window closes, contacting that customer again generally means using a message template Meta has approved. So a retailer can ask the agent for a marketing template offering a coupon, or a utility template for order updates, with a header, body copy, footer and buttons. From the same conversation you can list existing templates, pull up a version, update it or delete it.

Then ask for a test message before any of it reaches a customer. If the recipient sits outside the 24-hour window, the agent flags that a free-form message cannot be sent and offers an approved template instead.

Every invocation is logged, and state changes need a person

The agent can inspect the account as well as change it. You can ask what is already configured or what still needs attention, including whether the business is missing the payment information Meta needs to charge for billable WhatsApp messages.

There is also the other half of a conversation: what happens when the customer replies. The developer can ask the agent to configure the webhook that tells WhatsApp where to send incoming messages and other events, whether that is the retailer's CRM, support platform, chatbot or order-management system.

Meta says the agent operates using the access of the person who connected it, and that actions performed through the MCP are recorded. Lieberman put the guardrails this way in the announcement post:

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.

Two Meta MCP servers, and Meta says install both

MCP is the plumbing here: an open protocol that lets an AI client talk to a compatible tool server without a separate integration written for each platform. The official documentation compares it to a USB-C port for AI applications. Meta already had one server running on it.

Developer Tools MCP arrived in June and was later rebranded Meta Social Technologies MCP; by the Ads Uploader changelog, that rename landed on 18 August. It is the broad one: Graph API endpoints, Meta's documentation, the app behind an integration, error troubleshooting. The new server is narrower and operational, and Lieberman writes that the two are "complementary — install both if you need both."

In our view the sharpest design choice here is the one that keeps state changes behind an authenticated person: a New Stack explainer on agents and APIs notes that an agent handed an endpoint will keep calling it until it gets a successful response. What the announcement does not describe is how a template's approval or rejection comes back to the agent.

When the beta label comes off is not something Meta has dated: the server is rolling out gradually, and the interface and tools stay in beta and subject to change. The first practical check is whether your businesses show up at all in the picker when you connect an agent. After that, watch the tool list, because a workflow built on it this month may need revisiting.