
This profile is part of our MCP server directory, within The MCP Guide. Profiles are checked against each vendor's own documentation. Need a server built? See MCP development.
Meta's WhatsApp Business Tools MCP server lets an AI agent set up and manage a WhatsApp Business account. It can add and verify phone numbers, create and edit message templates, configure webhooks and send messages. Meta publishes and hosts it. As of October 2026 it is in beta and rolling out gradually.
Checked against: WhatsApp Business Tools MCP documentation on 28 October 2026. eSEOspace did not install or test this server.
Key Takeaways
- The server URL is
https://mcp.facebook.com/whatsapp_business_tools, over Streamable HTTP. - Meta labels it "Beta - interface and tool set may change," and says it may not be available to everyone yet.
- You sign in with your Meta developer account and pick which businesses and WhatsApp-enabled apps the server can reach.
whatsapp_biz_send_messageis the only sending tool. Meta says it "Confirms the target with you before sending."- Meta's launch post says the release is built for development and testing, "not production sending at scale."
At a glance
| Item | Detail |
|---|---|
| Publisher | Meta |
| Official? | Yes |
| Hosting | Remote URL: https://mcp.facebook.com/whatsapp_business_tools |
| Transport | Streamable HTTP |
| Sign-in | OAuth with your Meta developer account |
| Read or write | Both |
| Price | No separate MCP price listed |
| Source code | Closed (hosted by Meta) |
| Status | Beta |
What it can do
Meta's documentation lists these tools by group:
- Discovery:
whatsapp_biz_businesses,whatsapp_biz_accounts,whatsapp_biz_phone_numbers. - Phone onboarding:
whatsapp_biz_add_phone_number,whatsapp_biz_send_verification_code,whatsapp_biz_verify_phone_number,whatsapp_biz_register_phone_number. - Templates:
whatsapp_biz_list_templates,whatsapp_biz_get_template,whatsapp_biz_create_template,whatsapp_biz_update_template,whatsapp_biz_delete_template. - Messaging:
whatsapp_biz_send_message. - Webhooks:
whatsapp_biz_configure_webhooks,whatsapp_biz_subscribe_webhook. - Account setup:
whatsapp_biz_configure_payments,whatsapp_biz_verify_business,whatsapp_biz_system_user_token.
Two details are easy to miss. whatsapp_biz_system_user_token returns a link; tokens are created in Business Settings, not by the tool. And whatsapp_biz_verify_business checks status and can start business verification.
This is mainly a setup and developer tool. Other write tools change phone numbers, templates, webhooks and payment settings, and Meta does not say they confirm first. It helps an agent get an account ready to message customers. It is not described as a customer inbox or chat-reading tool.
How to connect it
Meta's docs give these setups:
Claude Code:
claude mcp add --transport http whatsapp_business_tools https://mcp.facebook.com/whatsapp_business_tools
Then run /mcp and select whatsapp_business_tools to authenticate.
Claude Desktop: Settings > Connectors > Add custom connector. Name it WhatsApp Business Tools and enter the server URL.
Codex App: Settings > MCP Servers > Add servers. Choose Streamable HTTP, enter the name and URL, set Authentication to OAuth and click Authenticate.
ChatGPT: Settings > Plugins > Browse plugins, add a plugin with the name and URL, set Authentication to OAuth and save.
For stdio-only clients, Meta suggests the mcp-remote bridge.
Prerequisites: you need the MANAGE role on the business, admin access to a WhatsApp-enabled app, and accepted WhatsApp Business Cloud API Terms of Service. Meta says you must sign in again when you restart the client.
Security notes
The scopes are broad: business_management, whatsapp_business_management and whatsapp_business_messaging. Limit exposure at the consent screen by selecting only the businesses and apps the agent needs. Our guide on excessive MCP permissions explains the trade-off.
Points to plan for:
- Sending is gated, other writes may not be. Meta documents a confirmation for
whatsapp_biz_send_messageonly. Keep your client's approval prompt on for template deletes, webhook changes and payment setup. - Payments cost money. Meta notes that configuring payments lets an account send billable messages.
- Messaging rules still apply. Free-form text only reaches a customer inside the 24-hour customer service window. Outside it you need an approved template.
- Webhooks move data. A webhook pointed at the wrong URL sends message events to someone else. Review every webhook change.
- Spec guidance. The MCP tools specification says there should always be a human in the loop with the ability to deny tool invocations.
- Revoking access. Meta says you can review or revoke access at facebook.com under Settings > Business Integrations.
The server is in beta, so tools may change. Watch for silent changes in tool behavior, a risk covered in our page on MCP rug pull attacks. Also see the MCP security center.
Alternatives
- Infobip MCP server, which includes a WhatsApp server for sending template and media messages.
- Slack MCP server, for internal team messaging rather than customer messaging.
Next step
If you are launching WhatsApp for customer updates, use the agent for setup and template drafting first, and keep live sends with a person. eSEOspace can help you plan that through our MCP development service. See more servers in our MCP server directory.
Frequently asked questions
Is there an official WhatsApp MCP server?
Yes. Meta hosts the WhatsApp Business Tools MCP server at https://mcp.facebook.com/whatsapp_business_tools. As of October 2026 it is in beta and rolling out gradually.
Will it send messages without asking?
Meta says whatsapp_biz_send_message confirms the target with you before sending. It is the only sending tool Meta lists.
Can it read my customers' WhatsApp chats?
Meta's tool list does not include a tool for reading conversations. The tools cover account discovery, phone setup, templates, sending, webhooks and account settings.
Which AI clients does Meta document?
Claude Code, Claude Desktop, the Codex App and ChatGPT. Meta suggests mcp-remote for clients that only support stdio.











