What is WhatsApp Business Tools MCP?
Meta introduced WhatsApp Business Tools MCP in September 2026 as a way for AI coding agents to work directly with the WhatsApp Business Platform.
The important change is not that Claude or ChatGPT suddenly became WhatsApp itself. The change is that Meta now exposes a standardized MCP tool surface so a compatible agent can perform supported administrative and development tasks on your behalf after you authenticate and grant access.
Meta’s own developer index describes the server as connecting an AI coding agent to the WhatsApp Business Platform so it can:
- create accounts
- add phone numbers
- build message templates
- send test messages
Launch reporting based on Meta’s documentation adds more detail, including phone-number verification, Cloud API registration, webhook testing and checking configuration blockers such as Business Verification, payment setup or Terms of Service state.
Primary source: Meta for Developers. Launch detail: TechCrunch coverage of Meta’s release.
WhatsApp Business Tools MCP does not replace the Cloud API
The cleanest architecture is:
Claude or ChatGPT → WhatsApp Business Tools MCP → WhatsApp Business Platform / Cloud API
The Cloud API remains the underlying messaging infrastructure hosted by Meta. Your production application still relies on the normal WhatsApp Business Platform, webhooks, message templates, authentication, policy rules and application logic.
The MCP sits above that infrastructure as an agent-facing control layer. It turns supported setup and configuration actions into tools that an AI assistant can call conversationally.
That means an instruction such as “register this number and help me test the webhook” can become a sequence of MCP tool calls instead of a long set of manual dashboard steps. But your production service still needs the Cloud API after the setup conversation ends.
WhatsApp’s Business Messaging Policy explicitly defines the WhatsApp Business Platform as including its APIs, including the Cloud API hosted by Meta.
Messaging policy: WhatsApp Business Messaging Policy.
What can the MCP help you do?
| Area | Agent-assisted task |
|---|---|
| Business onboarding | Create or work with a WhatsApp Business account. |
| Phone number | Add a number and guide the verification/registration flow. |
| Cloud API | Help register the business/number for Cloud API access. |
| Templates | Create and manage message templates from natural-language instructions. |
| Test messaging | Send test messages during setup. |
| Webhooks | Help configure or test webhook behavior. |
| Setup health | Surface blockers such as incomplete verification, payment configuration or Terms acceptance. |
The exact tool schema can change because the service is new and still rolling out. Treat the live MCP tool list as the authority for what your connected agent can currently do.
This is mainly for development, configuration and testing
The new MCP should not be confused with a production customer-messaging engine.
Its value is reducing the setup burden around WhatsApp Business infrastructure. It can help an AI agent configure resources and prove that a test path works, but Meta’s launch positioning is centered on development and testing rather than high-volume production sending.
For a real production deployment you still need:
- your application or backend
- production-safe credentials and access controls
- webhook handling
- message/template policy compliance
- logging and monitoring
- error handling and retries
- human escalation where required
- appropriate consent and privacy controls
Think of the MCP as an intelligent setup console, not a replacement for your WhatsApp production architecture.
Before you connect the MCP
Before giving an AI agent control over WhatsApp Business setup, confirm that the Meta account you plan to authenticate has the business and developer access needed for the assets you want to manage.
In practice, the setup can involve:
- a Meta business portfolio/business account you are authorized to manage
- a Meta developer app configured for WhatsApp Business messaging where required
- the phone number you intend to add or register
- ability to receive the phone-number verification code
- acceptance of the applicable WhatsApp/Cloud API terms
- Business Verification or payment configuration if Meta requires them for your intended use
If the agent can connect but an onboarding action still fails, the missing requirement may be on the Meta side rather than inside Claude or ChatGPT.
How to connect WhatsApp Business Tools MCP to Claude
Anthropic supports remote MCP servers as custom connectors on Claude, Cowork and Claude Desktop. The feature is available on Free, Pro, Max, Team and Enterprise, although Free users are limited to one custom connector.
Claude web / Desktop custom connector
- Open Claude and go to Customize → Connectors.
- Select Add custom connector.
- Use a clear name such as WhatsApp Business Tools.
- Enter the remote MCP endpoint:
https://mcp.facebook.com/whatsapp_business_tools. - Complete Meta’s authentication/authorization flow when prompted.
- Enable the connector in the conversation where you want to use it.
- Start with a read-only discovery request before asking Claude to change anything.
Claude Code
Current setup documentation for Meta’s server uses a remote HTTP MCP connection. A commonly documented Claude Code command is:
claude mcp add --transport http whatsapp_business_tools https://mcp.facebook.com/whatsapp_business_tools
After adding the server, authenticate the Meta connection and inspect the available tools before running write operations.
Anthropic emphasizes that custom connectors can access and modify data in connected services. Only connect remote MCP servers you trust and review the permissions being requested.
Claude connector documentation: Get started with custom connectors using remote MCP.
How to connect WhatsApp Business Tools MCP to ChatGPT
ChatGPT’s current MCP access is more plan-dependent than Claude’s.
OpenAI says full MCP support, including write and modify actions, is rolling out in beta to ChatGPT Business, Enterprise and Edu. Those are the relevant plans if you want ChatGPT to perform state-changing WhatsApp setup actions such as creating resources, registering a number or modifying a template.
OpenAI currently says Pro users can connect MCPs with read/fetch permissions in developer mode, but full MCP is not available to Pro. That means Pro is not the right path for the complete WhatsApp Business setup workflow described in this article.
ChatGPT Business / Enterprise / Edu
- Use ChatGPT on the web. OpenAI currently says custom MCP apps are web-only.
- Have the appropriate workspace admin/owner enable Developer Mode.
- Go to Settings or Workspace Settings → Apps → Create, depending on your role and workspace.
- Provide the remote MCP endpoint:
https://mcp.facebook.com/whatsapp_business_tools. - Select/configure the authentication mechanism and complete Meta authorization.
- Use Scan Tools so ChatGPT discovers the tools exposed by the server.
- Create the draft app, test it privately, and review every write action before publishing it to a workspace.
OpenAI says ChatGPT may ask for confirmation before write/modify actions depending on app permissions, context and potential impact. Some especially risky actions can be blocked rather than offered for approval.
OpenAI MCP documentation: Developer mode and MCP apps in ChatGPT.
Claude vs ChatGPT: current MCP access for this workflow
| Platform | Current MCP support | Suitable for WhatsApp setup writes? |
|---|---|---|
| Claude Free | Remote custom connectors supported; limited to one custom connector. | Potentially yes, subject to connector permissions and Meta authorization. |
| Claude Pro / Max | Remote custom connectors supported. | Yes, subject to permissions. |
| Claude Team / Enterprise | Remote custom connectors supported; an Owner/Primary Owner adds organization connectors first. | Yes, subject to organization controls and permissions. |
| ChatGPT Pro | Custom MCP read/fetch in developer mode. | No for the full workflow. OpenAI says full MCP write/modify is not currently available to Pro. |
| ChatGPT Business | Full MCP in beta on web. | Yes, with admin/owner developer-mode setup and action approvals. |
| ChatGPT Enterprise / Edu | Full MCP in beta on web, with additional RBAC/admin controls. | Yes, subject to configured action access. |
Start with safe discovery prompts before making changes
Do not make “set everything up” your first prompt on a live business account. Start by confirming that authentication and scope are correct.
Safer first prompts include:
- “List the WhatsApp businesses I am authorized to manage. Do not change anything.”
- “Show the WhatsApp Business accounts available to this connection.”
- “Check the onboarding status for my selected business and tell me what is missing before making changes.”
- “List my current message templates and their status. Do not edit them.”
- “Explain which tools you can call through this MCP before using any write action.”
Once those requests return the expected business and account scope, move to one change at a time.
Message templates still follow WhatsApp’s normal messaging rules
MCP does not bypass WhatsApp Business policy.
WhatsApp’s current Business Messaging Policy says a business can initiate conversations on the WhatsApp Business Platform only with an approved message template. After a user sends the business a message, the business can send non-template replies within the 24-hour customer-service window.
Outside that 24-hour window, the business must use an approved template for outbound messaging.
The policy also says automation can be used during the 24-hour window, but businesses must provide a prompt, clear and direct escalation path such as a human agent, phone number, email, web support or other supported route.
The MCP can help create or test a template. It cannot turn a non-compliant message into a compliant one simply because an AI agent generated it.
Policy source: WhatsApp Business Messaging Policy.
Use the MCP to shorten webhook setup and debugging
For a real Cloud API integration, inbound messages and delivery events normally need to reach your application through webhooks.
The new MCP can help reduce the back-and-forth involved in setup and testing. A useful development workflow is:
- Ask the agent to inspect the current WhatsApp Business setup.
- Register or verify the test phone number.
- Configure the webhook callback and required subscription.
- Send a test message.
- Confirm that your application receives the expected webhook event.
- Ask the agent to explain any failure before changing additional settings.
This is one of the strongest MCP use cases because the agent can connect the configuration task with the error that appears during testing, rather than forcing you to manually compare multiple dashboards and docs.
Security: treat this as privileged infrastructure access
WhatsApp Business Tools MCP exposes actions against real business infrastructure. A wrong tool call can affect a phone number, template, webhook or account configuration.
Use these controls:
- Authenticate with the least-privileged Meta identity that can complete the job.
- Confirm the business and app scope before approving changes.
- Separate development and production where possible.
- Keep write confirmations enabled.
- Do not paste permanent access tokens into prompts.
- Review message targets before any test send.
- Log configuration changes.
- Disconnect or revoke access when the integration is no longer needed.
Anthropic warns that custom MCP connectors can access and modify connected services. OpenAI similarly warns that untrusted MCP servers can increase prompt-injection and data-exposure risk. In this case the server is Meta’s, but the consequences of its tool calls still depend on the account and permissions you grant.
Common reasons the setup can fail
| Problem | What to check |
|---|---|
| No businesses are visible | Make sure the authenticated Meta account actually has access to the intended business portfolio. |
| Phone number cannot be registered | Confirm number ownership, verification-code access and current onboarding state. |
| Template operation fails | Check message-template policy, category/content requirements and account permissions. |
| Webhook test fails | Check callback reachability, verify token, subscriptions and application response. |
| Cloud API setup is blocked | Look for Terms acceptance, Business Verification, app configuration or payment requirements. |
| Claude cannot connect | Confirm the remote MCP URL and complete Meta authentication; Claude remote connectors connect from Anthropic’s cloud. |
| ChatGPT can read but cannot change anything | If you are on Pro, this matches OpenAI’s current limitation: Pro custom MCP is read/fetch only. Full writes require Business or Enterprise/Edu. |
| ChatGPT custom app is unavailable | Confirm you are on web, the workspace plan supports full MCP, and an admin/owner has enabled Developer Mode. |
Moving from a successful test to production
A successful MCP-driven test means the integration path works. It does not mean the production system is finished.
Before going live:
- Separate production credentials and configuration from test assets.
- Verify every approved message template you intend to use.
- Implement webhook validation and durable event handling.
- Add retries, idempotency and monitoring.
- Respect opt-in, consent and WhatsApp Business messaging policies.
- Keep high-impact administrative changes behind human approval.
- Monitor quality and account health after launch.
For production customer conversations, your application should call the Cloud API directly through a controlled backend rather than relying on an open-ended AI chat as the runtime for every customer message.
Fast setup checklist
- Confirm you are working with the WhatsApp Business Platform / Cloud API, not the ordinary personal WhatsApp app.
- Verify your Meta business and developer access.
- Add Meta’s remote MCP endpoint:
https://mcp.facebook.com/whatsapp_business_tools. - Authenticate through Meta and review the requested permissions.
- Start with a read-only discovery prompt.
- Check Terms, verification, payment and number-onboarding blockers.
- Register or verify the phone number one step at a time.
- Create or inspect a test message template.
- Configure and test the webhook.
- Send a test message only after confirming the recipient and message type.
- For ChatGPT, use Business/Enterprise/Edu if the workflow needs write actions.
- Move production sending into a controlled application using the Cloud API.
BeeVaults takeaway: Meta’s WhatsApp Business Tools MCP makes the configuration layer conversational. Claude can connect to the remote server as a custom connector, while ChatGPT’s full write-capable path currently requires Business, Enterprise or Edu. The MCP can reduce setup friction, but the Cloud API remains the real messaging infrastructure, and WhatsApp’s normal template, 24-hour window, permission and policy rules still apply.