Meta's WhatsApp Business MCP makes onboarding a tool call

Meta shipped a WhatsApp Business Tools MCP server on September 15, and the pitch is that your coding agent does the setup paperwork. TechCrunch reports it connects agents — Claude, Cursor, Codex, ChatGPT — directly to the WhatsApp Business Platform to handle account creation, phone number verification, Cloud API registration, message template design, and checking payment methods and business verification status. That is a genuinely miserable multi-console workflow, and getting it out of the Developer Console and Business Manager is worth something. It also means an agent now holds the keys to your customer messaging channel.

What actually happened

This extends a set Meta already had — MCP servers for ads and for app configuration — with one aimed at onboarding. The work it absorbs normally spans three surfaces: the Developer Console, Business Manager, and the API reference you keep open in a fourth tab.

Read the capability list as a permission list, because that is what it is. Creating an account, registering a number against the Cloud API, and authoring message templates are not read operations. Template design in particular is the regulated part — templates are what let you message a customer outside the 24-hour service window, they go through Meta's approval, and a rejected or badly categorized template is a deliverability problem that shows up as silence rather than an error.

Meta has not, as far as we can find, published a standalone doc page for this server, so treat the capability list as reported rather than as a contract until it lands in the WhatsApp changelog.

Why it matters for your business

For a small operator, WhatsApp is often the channel — the order confirmations, the appointment reminders, the "are you open" messages. An MCP server that shortens the setup from a week to an afternoon is real leverage. The risk is not the automation; it is the scope you hand it and never revisit.

Scope the token before the agent, not after. The MCP server acts with whatever credentials you give it. Use a system user with only the assets it needs, not an admin token that reaches every business asset in your portfolio. If your agent can register phone numbers, it can register the wrong one.

Separate setup credentials from send credentials. Onboarding is a one-time burst of privileged writes. Messaging is a continuous, lower-privilege operation. Rotate the setup token out when onboarding is done; do not let it become the thing your production sender uses because it already worked.

Keep the templates in your repo. Templates are business logic — your tone, your compliance language, your variables. Generating them through an agent is fine. Leaving the only copy inside Meta's console is not. Check the template definitions into version control so you can diff them, review them, and recreate them on any platform.

Watch the general pattern. Vendors are shipping MCP servers for their own admin surfaces because it moves you onto the platform faster. That is a fair trade going in, and a lock-in problem if the agent-driven config only exists in their console. Own the definitions; rent the delivery.

Sources: TechCrunch, WhatsApp Business Platform documentation.