跳到正文
imBee · AI Agent 及企業客服·· 2026-09-17AI 評分55

Meta 推出 WhatsApp Business Tools MCP,讓 AI 智能體代為設定 WhatsApp Business

Meta's WhatsApp Business Tools MCP: AI Agents Can Now Set Up WhatsApp Business for You

AI 導讀

Meta 於 2026 年 9 月 15 日推出 WhatsApp Business Tools MCP,讓 AI 智能體透過對話建立 WhatsApp Business 帳戶、驗證電話號碼並註冊 Cloud API。它亦可建立和編輯訊息範本、追蹤審批、傳送測試訊息及設定 webhook;目前逐步推出,供開發和測試使用,不支援正式環境大規模發訊。

正文

Published 17 September 2026. Source: Meta for Developers, "Announcing WhatsApp Business Tools MCP: Set up and manage WhatsApp business from your AI agent", 15 September 2026.

You ask your agent to set up WhatsApp Business messaging, and it does. That's the whole pitch. In Meta's words, the agent "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 server is called WhatsApp Business Tools MCP (the same post also refers to it as Meta Business Messaging MCP), and it is "currently discoverable on Claude, Codex and ChatGPT."

Four groups of tasks the WhatsApp Business Tools MCP hands to an AI agent: account setup (WABA, phone number, OTP, Cloud API registration), template iteration, test messages and webhooks, and prerequisite checks (Terms of Service, payment method, Business Verification), each shown before and after

What used to mean moving between the Developer Console, Business Manager, the API reference and your editor becomes one request to an agent.

Meta groups the work the agent can take on into four:

  • Setup through conversation. Account, phone number, OTP verification, Cloud API registration.
  • Faster template iteration. Describe a template and the agent creates it, edits an existing one, and tracks approval.
  • Test messages and webhooks. Send test messages from the registered number and set the callback URL.
  • Prerequisites, surfaced early. Terms of Service status, payment method, Business Verification, checked before they block you.

Sign-in is Facebook Login for Business with a specific set of scopes, "so no tokens land in your prompt history." Availability is gradual: Meta says the server "may not be available to everyone yet."

Meta's getting-started line is one sentence: "Add the server to your agent's MCP configuration, sign in when prompted, and ask your agent to set up WhatsApp Business messaging." Here's what that looks like in practice, and what you need at each step.

Five-step flow of the MCP setup: add the server to the agent configuration, sign in with Facebook Login for Business, ask the agent to set up WhatsApp Business messaging, the agent creates and verifies the account and number, then build templates and test

The OTP still arrives on the phone, so keep the number to hand while the agent runs step four.
StepWho does itWhat you need
Add the server to your agent's MCP configurationYouAn MCP-capable coding agent; Meta names Claude, Cursor, Codex and ChatGPT
Sign in with Facebook Login for BusinessYouAdmin access to a Meta app with your business attached; Meta checks this before any tool runs
Ask for the setupYou, one sentenceThe phone number you want on WhatsApp
Terms of Service, WABA, number, OTP, Cloud API registrationThe agentThe OTP arrives on the number, so keep it to hand
Templates, test messages, webhook callback URLThe agent, on requestAn endpoint that can receive the webhook

One thing the announcement does not say is which regions get it first. Treat "rolling out gradually" literally: if the server has not appeared in your agent's directory yet, that is expected, not a fault on your side.

The line that matters most is near the end of Meta's post: "This release is built for development and testing workflows, not production sending at scale." Read that as a design statement, not small print. The MCP sets a channel up. It does not run it.

Two lanes: what the MCP is for (account setup, template drafting, test messages, webhooks, prerequisite checks) versus what it does not replace (production sending at scale, a shared team inbox, broadcasts and campaigns, opt-in records, routing and reporting)

The right-hand lane is where the operating cost of WhatsApp sits, and it is untouched by this release.

What it does well is the part of WhatsApp that has always been tedious: the account, the number, the first templates, the webhook. If you have a developer and a test account, it looks like the fastest route yet from nothing to a working Cloud API number. We'd say that even though it competes with part of what we do.

What it leaves untouched is everything after the first message: who answers, in which inbox, with which automations, against which opt-in records, and how you report on it. That is where the cost and the value of WhatsApp both live.

This is not a one-off. Reading the Meta for Developers blog back through the year gives you the sequence: the Meta AI Developer Assistant went live for Business Messaging on 13 May, Meta Social Technologies MCP was announced on 30 June (as Developer Tools MCP, renamed on 18 August), an MCP server for Meta's ads platform followed on 16 July, and now WhatsApp on 15 September. Meta keeps the two MCPs distinct: Social Technologies for Graph API discovery and documentation, the WhatsApp one "for WhatsApp accounts, phone numbers, templates, webhooks, and test messages."

Timeline of Meta developer tooling for AI in 2026: the Meta AI Developer Assistant went live for Business Messaging on 13 May, Meta Social Technologies MCP was announced as Developer Tools MCP on 30 June and renamed on 18 August, the ads MCP server followed on 16 July, WhatsApp Business Tools MCP on 15 September, now rolling out gradually

Three MCP servers since June, all dated from the Meta for Developers blog.

The signal for you is simple: Meta expects developers to reach its business messaging platform through agents, not consoles. Setup friction was one of the reasons businesses came to a partner. That reason is getting weaker, and we think that's fine, because setup was never the hard part.

  • The hard part is the operating model. Routing, opt-in, templates that pass review and still convert, reporting your finance team accepts.
  • The hard part is the second channel. WhatsApp rarely stays alone; Instagram, Messenger, LINE and web chat usually follow.
  • The hard part is the people. Nothing here answers a customer at 9pm on a Sunday.

Already on imBee? Nothing changes: WhatsApp Business API onboarding is part of the plan and was done with you. If there are templates you've been meaning to create, send them over.

Three checklists: if you already run WhatsApp through imBee nothing changes on your account; if you run your own Cloud API integration try the MCP on a test account first; if you are still evaluating WhatsApp decide the operating model before the tooling

Pick your column. The links for each are in the paragraphs below.

Running your own Cloud API integration? Test account first, never the live one, and keep the production pipeline you already trust.

Still evaluating WhatsApp? Decide the operating model before the tooling. Our WhatsApp Business API explainer covers the account types, and the 1 October 2026 pricing guide covers what each message will cost once you are live. If you'd rather talk it through, our team (imBee is an Official Meta Technology Partner) has set up WhatsApp for businesses across Hong Kong, Singapore, Malaysia and Indonesia and will tell you plainly whether the MCP route or a partner route fits.

Frequently asked questions

What is WhatsApp Business Tools MCP?
It is a Model Context Protocol server released by Meta on 15 September 2026. Once added to an AI agent's MCP configuration, the agent can check your Terms of Service status, create a WhatsApp Business Account, add and verify a phone number, register it for the Cloud API, create and edit message templates, track template approval, send test messages and configure webhooks, all through conversation.

Which AI agents can use it?
Meta names Claude, Cursor, Codex and ChatGPT as the coding agents it connects, and says the server is currently discoverable on Claude, Codex and ChatGPT. You sign in with Facebook Login for Business and grant a specific set of scopes, so no access tokens are pasted into the chat. Meta describes the rollout as gradual, so it may not appear for every account straight away.

Can it send customer messages at scale?
No. Meta states that this release is built for development and testing workflows, not production sending at scale. It is a setup and testing tool. Production sending, a shared inbox, broadcasts, opt-in records and reporting still sit with your own Cloud API integration or with a messaging platform such as imBee.

I'm an imBee customer. Do I need to do anything?
No. Your WhatsApp Business Account, phone number, approved templates and inbox are unchanged, because API onboarding is part of your imBee plan and was completed with you. The MCP is a developer tool for creating and testing new setups, not something that touches an account already in production.

Does this change WhatsApp Business pricing?
No. The MCP is a developer tool and Meta's announcement says nothing about message prices. Pricing is set separately by Meta's per-message rate cards, and the next change, which makes service messages and in-window utility templates billable, takes effect on 1 October 2026 regardless of how your account was set up.

Sources and further reading

imBee Editorial Team

Content and product marketing, imBee

The imBee Editorial Team writes about WhatsApp Business, omnichannel messaging and the platform changes that affect how businesses in Hong Kong, Singapore, Malaysia and Indonesia talk to their customers. Every platform fact is checked against the primary source and dated.

Questions about anything in this article? Talk to our team.

來源:imBee · AI Agent 及企業客服 · imbee.io