01
Overview
WhatsApp Business Tools MCP lets an MCP-capable AI coding agent perform supported WhatsApp Business Platform setup and testing tasks on your behalf. The safest way to use it is to treat the agent as an authenticated configuration assistant: give it a specific job, review the account and permissions it is acting on, and verify each state-changing result.
This guide covers the launch-state workflow without relying on UI labels that may change during Meta's gradual rollout.
02
Before you start
You need access to the relevant Meta developer/business assets and an AI coding environment that supports the WhatsApp Business Tools MCP connection. Meta's launch material names Claude, Cursor, Codex and ChatGPT among supported or discoverable environments.
You should also know which business, app and phone number you intend to configure. The MCP does not bypass WhatsApp Terms, phone verification, payment requirements, Business Verification or other platform policies.
03
1. Connect the WhatsApp Business Tools MCP
Add or discover the WhatsApp Business Tools MCP from your MCP-capable agent environment, then authenticate with the Meta account that has access to the relevant developer app/business.
Launch reporting based on Meta's documentation says the connection uses Facebook Login for Business and specific permissions. Select only the business assets the workflow actually needs. Do not assume that connecting an agent gives it unrestricted access to every Meta account you administer.
Because availability is rolling out gradually, the MCP may not yet appear for every developer or in every client. If it is missing, first verify rollout availability and the agent client's current MCP support.
04
2. Ask the agent to inspect prerequisites
Before creating or changing resources, ask the agent to check the current setup state. Useful checks include whether the required WhatsApp Terms have been accepted, whether the correct business is selected, whether a payment method or Business Verification requirement is blocking setup, and whether a WhatsApp Business Account already exists.
This inspection-first approach reduces the chance of creating duplicate or unnecessary resources.
05
3. Create or select a WhatsApp Business Account
If the business does not yet have the required account, the MCP can help create a WhatsApp Business Account as part of onboarding. If an account already exists, direct the agent to use the existing resource rather than creating another one.
Always verify the business/account identity before approving a state-changing action.
06
4. Add and verify the phone number
The launch workflow supports adding a phone number and guiding verification. Phone ownership verification still requires the underlying Meta/WhatsApp verification process; the agent does not bypass it.
After verification, the agent can help register the number for Cloud API access. Confirm that the resulting phone number and WhatsApp Business Account are the intended resources before moving on.
07
5. Create or edit message templates
You can describe the message template you need in natural language and ask the agent to create it, or ask it to modify an existing template. Meta's launch material also describes checking template approval status.
Template approval remains governed by WhatsApp's rules. An AI-generated template is not automatically approved simply because the MCP created it.
For production use, review the final copy, variables, language and business purpose yourself before relying on it.
08
6. Send a test message
Once the test environment is ready, ask the agent to send a test message from the registered number. Keep this stage focused on development/testing and verify the destination and content before approving the action.
Meta currently positions WhatsApp Business Tools MCP as development and testing tooling rather than a replacement for production messaging infrastructure at scale.
09
7. Configure and test webhooks
The MCP can help configure webhook callback URLs and subscriptions and test whether events are reaching your integration. This is useful because webhook setup commonly requires work across Meta configuration screens and application code.
A sensible workflow is: ask the agent to inspect the current webhook configuration; specify the callback URL and events you need; review the proposed changes; apply them; trigger a test event; and verify that your application actually receives and processes it.
Do not treat an agent's statement that a webhook is configured as sufficient proof. Check the receiving application's logs or event handling as well.
11
9. Review permissions and state-changing actions
MCP makes operational work conversational, but it does not make it consequence-free. Before approving changes, confirm which business/app/account is in scope, which phone number is being changed, what template or webhook will be created, and whether the action is reversible.
Reporting based on Meta's launch documentation says reads run in the user's access context, tool invocations are logged, and state-changing actions require an authenticated user context. Those controls help, but human review remains appropriate for business messaging infrastructure.
12
What to do if WhatsApp Business Tools MCP is not showing
Because the release is gradual, absence does not necessarily mean a configuration error. Check whether your chosen agent client currently supports/discovers the server, whether your Meta account is in the rollout, whether you are signed into the correct developer/business account, and whether the required permissions and business prerequisites are satisfied.
There is not yet enough stable first-party rollout documentation to promise a universal country, account tier or date for access.
13
What the MCP does not replace
It does not replace the WhatsApp Business Platform or Cloud API for production messaging. It does not bypass phone verification, Business Verification, payment requirements, template review or WhatsApp policies. It also does not guarantee that an integration works simply because configuration calls succeeded; your application still needs to handle API responses, webhook events, errors and production operational requirements correctly.
14
Practical prompts
Rather than asking an agent to 'set up everything,' use bounded instructions such as: inspect my current WhatsApp Business setup and list missing prerequisites without changing anything; use the existing WhatsApp Business Account and tell me which phone-number verification step is required next; draft a utility message template for this stated purpose but do not submit it until I approve the copy; inspect my webhook subscriptions and explain what would change before applying anything; or send one test message to the approved test destination and report the API result.
The principle is simple: inspect first, scope the action, review the proposed change, execute, then verify independently.
15
FAQ
Can I use WhatsApp Business Tools MCP with ChatGPT or Claude?
Meta's launch material names ChatGPT and Claude, along with Cursor and Codex, among supported/discoverable agent environments. Availability can vary during rollout.
Can the agent verify my phone number automatically?
The MCP supports the phone onboarding/verification workflow, but it does not bypass proof-of-ownership requirements such as verification codes.
Can it create WhatsApp templates?
Yes. Meta says the agent can create or edit templates and surface approval status. WhatsApp's template rules and approval process still apply.
Can it set up webhooks?
Yes. Webhook callback and subscription setup/testing are among the announced workflows. Verify the receiving application separately.
Should I use it to send production campaigns?
Not as a replacement for production messaging infrastructure. Meta currently describes the MCP as development/testing tooling; production messaging remains on the WhatsApp Business Platform/Cloud API and subject to its normal rules.
16
Verification note
This guide reflects the September 15, 2026 launch state reported from Meta's developer announcement. The dedicated Meta documentation, current agent-client support, rollout eligibility and permission scopes should be rechecked before publication because those details can change quickly during an initial rollout.
Sources
Primary and supporting sources
Use the linked documentation to check current pricing, access and product behaviour. The dates above describe this article; they do not guarantee that every vendor claim remains current.