Meta now lets an AI agent set up WhatsApp Business — here's what it actually automates
Meta shipped a WhatsApp Business Tools MCP server on 15 September 2026, and it lets an agent of your choosing — Claude, Cursor, Codex or ChatGPT — connect to the WhatsApp Business Platform and run the setup itself. The announcement puts one half of a WhatsApp Business integration inside an agent, and leaves the other half exactly where it was.
The half that moved is the console chore list. The half that did not is the part where a business entity, a template policy and a payment relationship have to be signed for by a person. That split is the whole story for an agency that has ever billed "WhatsApp Business API implementation" as a line item.
Meta's own summary of the agent path is short: “Ask your agent to set up WhatsApp Business messaging and it walks the whole path: checks your Terms of Service status, creates a WhatsApp Business Account, adds your phone number, verifies it over OTP, and registers it for the Cloud API.” The friction it replaces is named just as plainly in Meta's developer documentation: “Getting a WhatsApp Business integration running means moving between the Developer Console, Business Manager, the API reference, and your editor, then pasting an access token somewhere it shouldn't live.”
Two caveats belong next to that quote, and both come from Meta's own material. First, the account creation step is not corroborated: the server's tool reference lists no tool that creates a WhatsApp Business Account, so the sentence above is Meta describing the path, not a tool you can call today (more on that below). Second, this release is explicitly “built for development and testing workflows, not production sending at scale” — the server is beta, it is rolling out gradually, and Meta says the tool set may change.
What the WhatsApp Business Tools MCP server automates
The server is a remote MCP server at https://mcp.facebook.com/whatsapp_business_tools. It authenticates with your Meta developer account over OAuth, so the same sign-in flow works with every client, and the tool set is namespaced whatsapp_biz_. Meta's framing of the starting point is worth keeping: “Most tools are scoped to a business you administer, so a typical session starts by listing your businesses and picking one. The tool set is evolving during beta.”
Counting Meta's tool reference gives 18 whatsapp_biz_* tools. They cover the following work:
| Setup chore | Tool(s) on the server | What it does |
|---|---|---|
| Find the assets | whatsapp_biz_businesses, whatsapp_biz_accounts, whatsapp_biz_phone_numbers | Lists the businesses you administer, the WhatsApp accounts under one, and the phone numbers on an account with their status and onboarding state. |
| Add a phone number | whatsapp_biz_add_phone_number | Attaches a number to a WhatsApp account. |
| Verify the number | whatsapp_biz_send_verification_code, whatsapp_biz_verify_phone_number | Sends the OTP by SMS and completes verification with the code the client reads back to the agent. |
| Register for the Cloud API | whatsapp_biz_register_phone_number | Registers a verified number so it can send and receive. This is the step that has no UI: “You can only register a number via the API — you cannot register a number through WhatsApp Manager (WAM) or the App Dashboard.” |
| Check Terms of Service status | server precondition, checked up front | A status check, not an acceptance — “Messaging and phone-number registration are blocked until an admin accepts them.” |
| Create and edit templates | whatsapp_biz_create_template, whatsapp_biz_update_template, whatsapp_biz_delete_template, whatsapp_biz_list_templates, whatsapp_biz_get_template | Full create, read, update and delete on message templates, plus a deep link to each template's approval progress. |
| Test a message | whatsapp_biz_send_message | Sends a free-form text inside the 24-hour customer service window, or an approved template from a registered number; Meta's description says it confirms the target with you before sending. |
| Point webhooks | whatsapp_biz_configure_webhooks, whatsapp_biz_subscribe_webhook | Sets the callback URL and verify token, then subscribes the account to your app's webhook fields. |
| Configure payments | whatsapp_biz_configure_payments | Configures a payment method so the account can send billable messages. |
| Business Verification: check and start | whatsapp_biz_verify_business | Reports verification status and starts the process — it does not complete it. |
| System user token | whatsapp_biz_system_user_token | Returns a deep link to the System Users page for a custom build; the token generation itself stays a click in Business Settings. |
Three things on that list are worth more than the rest, because they are the ones that used to eat unbilled hours. The registration call is API-only, so an operator without a development environment could not finish setup at all. The test half is a real deliverable rather than a formality — Meta calls it “send a real message from your registered number to validate the integration end to end, and configure callback URLs and field subscriptions without getting them subtly wrong.” And the monitoring half targets failures that were previously silent: “Terms of Service, payment method, and Business Verification usually fail quietly. Your agent checks them up front and deep-links you to whatever is missing.”
One correction on account creation. Two published write-ups, including Meta's own blog post, describe the agent creating the WhatsApp Business Account. The server's tool reference does not list a create-account tool: the account tools are read-only listings. Treat account creation as unconfirmed until Meta ships a tool for it, and do not promise a client that the agent will create the account.
Meta shipped a companion server for the same workflow. Meta Social Technologies MCP (formerly Meta Developer Tools MCP) is for discovering Graph API endpoints, searching documentation and troubleshooting errors, and Meta's guidance is that the two are complementary: use the WhatsApp server for accounts, numbers, templates, webhooks and test messages, and install both if you need both. The server is discoverable today on Claude, Codex and ChatGPT, and Meta publishes a validated-client list — Claude Desktop, Claude Code, ChatGPT (Web), Codex App, Codex CLI, Cursor App and Cursor CLI — with configuration snippets per client.
What still needs a human
The line that matters for a proposal is not what the agent can click. It is what the agent still cannot be. Meta states the principle once: “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.” Everything in this section is that principle with a name attached.
| What stays human | Why it cannot be handed to the agent |
|---|---|
| App and business admin identity | The precondition for every tool: “You must have admin access on the app, not only on the business.” No admin role, no session. |
| Accepting the Cloud API Terms of Service | The agent checks status; an admin accepts. Messaging and number registration stay blocked until that happens. |
| Completing Business Verification | The tool checks and starts it. The completion path runs in Business Manager: Meta's own words are that “the verification process itself must be completed in the Facebook Business Manager”, and “only someone with an Admin role in the Business will be able to complete the verification process.” Verification is an identity review of the business entity, not a configuration step. |
| Template policy and review | Templates go through automated systems and manual reviews, and approval can take “up to 24 hours”. Rejections are itemised in Business Support Home, and an appeal “must include a sample”. Sensitive-identifier rules (full payment card numbers, financial account numbers, national IDs) are the ones that most often kill SMB marketing copy. |
| The billing relationship | Configuration is automatable — whatsapp_biz_configure_payments exists — but billing itself is not: “Billing and billing-related actions are handled through the Meta Business Suite.” And it locks: a WABA's time zone and currency cannot be edited once a line of credit is attached, and a WABA cannot be migrated between businesses. |
| Official Business Account status | A Meta review with an eligibility clock. The owning portfolio must have passed Business Verification and “the business must be registered on the WhatsApp Business Platform for at least 30 days”; a denied request means waiting 30 days before submitting again. |
| Access grants and prompt-injection exposure | Scopes are granted by a person, and Meta names the risk: anything the agent can call, it can call “including in response to malicious instructions hidden in tool outputs (prompt injection)”. Meta's own advice is separate dev and prod apps and a periodic revocation audit. |
| Quota and rate ceilings | Per-user per-tool rate limits, registration limited to 10 requests per business number in a 72-hour window, a default 10 new business customers per rolling 7 days for partners, an initial cap of 2 registered numbers per Meta Business Account, and 80 messages per second per number by default. No agent raises any of these. |
| Legal responsibility | The business owns the account and the content: “it is your sole responsibility to determine your legal obligations.” |
If a client asks whether they still need help, the honest split is this: the clicking is largely gone, the identity, policy and liability work is not. That is also the part a careful agency documents rather than performs silently, because it is the part that transfers risk.
How this changes an agency proposal
The old proposal had one line for WhatsApp Business API implementation, priced as a block of hours that were mostly spent navigating consoles. That line should be split rather than deleted, and priced differently on each side.
| Proposal line item | Before: console-era implementation | Now: agent-assisted implementation |
|---|---|---|
| Setup execution (agent-assisted) | The bulk of the line: asset discovery, number add and OTP, API registration, template creation, webhook pointing, a test send. | A small, explicitly fast block priced in supervised hours. The agent runs the sequence; you review the outputs, supply the sample data, and QA the test send and the webhook. |
| Verification & compliance handling | Bundled invisibly inside implementation, or absorbed as "admin". | Its own line, priced on documents and reviews: collecting and matching legal-name documentation, driving Business Verification, chasing status, and handling the identity-side questions. |
| Template strategy | A one-shot set of templates delivered with setup. | A priced revision loop, because approval can take up to 24 hours, rejections are itemised, and appeals need a sample. Price the loop, not the first draft. |
| Agent access & governance | Did not exist. | New line: scope selection, separate dev and prod apps, a revocation audit cadence, and a written position on prompt injection through tool output. |
| Billing & entitlement operations | Buried in "support", if it was billed at all. | A monthly retainer line: billing objects, the currency and time-zone lock, quota ceilings, capacity upgrades and OBA eligibility. |
Five edits in practice, in the order they land in a document:
- Split the old single line into setup execution (agent-assisted) and verification & compliance handling. They are different work with different risk.
- Re-price the setup hours; do not delete them. Keep the line, shrink the hours, raise the rate — what is left is supervision, sample data and QA, not clicking.
- Add a template strategy line with an explicit revision loop, and put the 24-hour approval window in the client-facing schedule so a slow approval cannot be read as your delay.
- Add an agent access & governance line, including who owns the app, which scopes are granted, and when they are audited.
- Add a billing & entitlement ops retainer, because the things that bite monthly (billing objects, quota ceilings, capacity) are not one-time setup work.
What still needs a human above is also what a client will ask about next: not how the setup works, but what happens once their customers start talking to a Meta agent. That is a different surface with a different thesis — our read on the Meta Project Hatch / Muse agent opportunity covers the customer-facing side; this page covers the implementation side.
The MCP server is now a pattern, not a story (18 September 2026)
As of 18 September 2026, an official MCP server is the default way a platform exposes itself to an agent, and the pattern now spans the stack an agency cares about: PayPal, Stripe, GitHub, Notion, Slack, Salesforce, Atlassian, X Ads MCP (the ads surface, not the core X API), Google Ads, Microsoft Azure and the Microsoft Learn server, plus Linear, Sentry, Supabase, HubSpot, Figma, Vercel and Cloudflare. Meta's entry is the newest and the most consequential for agencies, because it automates an onboarding chore rather than an API read. The full row-by-row comparison, with each vendor's own documentation link, lives on the agent plugins for AI agencies roundup.
Frequently asked questions
How long does WhatsApp Business API setup take?
There is no Meta-published end-to-end number, so no honest page can quote one. The clock is set by the gates rather than the clicks: template approval can take up to 24 hours, a partner-led Business Verification submission averages 5 minutes, and Official Business Account status requires a business registered on the WhatsApp Business Platform for at least 30 days.
Can you set up the WhatsApp Business API without a developer?
Partly, as of 15 September 2026. The console-and-API chores - adding a number, verifying it over OTP, registering it for the Cloud API, creating templates, pointing webhooks and firing a test send - can now be run by an agent of your choosing through Meta's WhatsApp Business Tools MCP server. The steps that remain are admin and identity steps rather than developer steps: app and business admin access, accepting the Terms of Service, and Business Verification.
What is the MCP server for WhatsApp Business?
Meta's official one is WhatsApp Business Tools MCP, a remote MCP server at https://mcp.facebook.com/whatsapp_business_tools that authenticates with your Meta developer account over OAuth and acts on the businesses you administer. It manages WhatsApp Business Platform setup and debugging - accounts, phone numbers, templates, webhooks and test messages - rather than linking WhatsApp to a chat automator.
Is WhatsApp Business setup still billable work?
Yes, for the gated half. The console-walking time collapses, but verification handling, template policy work, webhook and CRM integration, and monitoring and entitlement operations keep their billable basis. The setup hours that survive are supervision, sample data and QA of the test send and webhook, not clicking.
Sources
- Meta for Developers — “Announcing WhatsApp Business Tools MCP: Set up and manage WhatsApp business from your AI agent”, 15 September 2026: developers.facebook.com
- Meta for Developers — WhatsApp Business Tools MCP reference (the 18
whatsapp_biz_*tools, endpoint, OAuth, scopes and validated clients): developers.facebook.com - Meta for Developers — MCP overview (“Official remote MCP servers for integrating Facebook, Instagram, WhatsApp, and Meta Ads capabilities into your agentic workflows.”): developers.facebook.com
- TechCrunch — “Meta now lets AI agents handle the boring parts of WhatsApp Business setup” (Sarah Perez, 15 September 2026): techcrunch.com
- Meta for Developers — Template review (24-hour approval window, rejection reasons, appeals, sensitive-identifier rule): developers.facebook.com
- Meta for Developers — Register a business phone number (registration is API-only): developers.facebook.com
- Meta for Developers — Official Business Accounts (verification precondition and the 30-day registration clock): developers.facebook.com
- Meta for Developers — Partner-led business verification (partner-only; 5-minute average turnaround, three submissions per client): developers.facebook.com
- Meta for Developers — Business Verification (completion runs in Business Manager, by a Business Admin): developers.facebook.com
- Meta for Developers — WhatsApp Business Platform pricing (per-message billing): developers.facebook.com
Accuracy note: this page describes a beta release. Meta's tool reference was read on 18 September 2026 and lists 18 whatsapp_biz_* tools; Meta says the interface and tool set are in beta and may change, and that the server is rolling out gradually. No Meta-published end-to-end setup timeline exists, so none is stated here; the 24-hour template window, the 5-minute partner-led verification average and the 30-day OBA clock are the gates Meta does publish. The claim that the agent creates the WhatsApp Business Account comes from Meta's blog post and press coverage, not from a tool in the reference, and is flagged as unconfirmed on this page. Every figure and quotation above is drawn from the sources listed, all read on 18 September 2026.