What is the WhatsApp Business Tools MCP?

It is a remote MCP server from Meta at https://mcp.facebook.com/whatsapp_business_tools that lets an AI agent set up and manage the WhatsApp Business Platform for you. Meta announced it on September 15, 2026. It works over Streamable HTTP with OAuth sign-in, and the tools are all prefixed whatsapp_biz_.

Which AI clients can connect to it?

Meta's documentation lists Claude Code, Claude Desktop, the OpenAI Codex app and ChatGPT. A client that only supports local (stdio) servers can use the mcp-remote bridge. Meta says the server is rolling out gradually and may not be available to everyone yet.

Can I run my customer conversations through it?

No. Meta describes it as built for development and testing workflows, not production sending at scale. It sends a message when you ask it to, but it does not receive customer replies, assign chats or keep conversation history. That is what a messaging platform and a team inbox are for.

What permissions does it ask for?

Three OAuth scopes: business_management, whatsapp_business_management and whatsapp_business_messaging. You choose which businesses and apps to share on the consent screen, and you can revoke access under Settings, Business Integrations on Facebook.

Do I still need Business Verification, Terms of Service and a payment method?

Yes. The tool does not remove Meta's requirements. You need admin access to the business and to a WhatsApp-enabled app, and an admin must accept the WhatsApp Business Cloud API Terms of Service before messaging and phone registration work. Meta's announcement also lists a payment method and Business Verification as the usual silent failures.

Does the MCP server change what Meta charges for messages?

Nothing in Meta's documentation says so. Messages you send are still billed by Meta per message by category and country. See our WhatsApp Business API pricing guide for the current rates.

Is this the same as connecting an MCP server to MonoChat?

No, they point in opposite directions. Meta's server lets an AI coding agent configure your WhatsApp account. In MonoChat you add MCP servers so that your own AI assistants can call tools, such as your CRM or calendar, while answering customers.

Meta's WhatsApp Business Tools MCP: what it can do, what it can't, and where a messaging platform still fits

On September 15, 2026 Meta released an MCP server that lets an AI coding agent set up the WhatsApp Business Platform: register a number, create templates, configure webhooks, send a test message. Here are the real tools, the OAuth scopes, the limits Meta states, and how it relates to running customer conversations.

MonoChat Team Updated: October 22, 2026 5 min read

On this page

What the server is
The tools Meta lists
Permissions and security
What you still need first
What it does not do
When it is useful, and when it is not
Do not mix up the two directions of MCP
What this means in MonoChat
Sources

On September 15, 2026 Meta published WhatsApp Business Tools MCP, an MCP server that connects an AI agent such as Claude, ChatGPT or Codex to the WhatsApp Business Platform. Instead of moving between the Developer Console, Business Manager and the API reference, you ask the agent to do the setup. This guide lists what the server does, using Meta’s own documentation, and where it stops.

The short version: it is a setup and testing tool for people building on the API. It is not a way to answer customers. If you run support or sales on WhatsApp with a team, you still need a place where conversations arrive, are assigned and are answered.

What the server is

Server: WhatsApp Business Tools, at https://mcp.facebook.com/whatsapp_business_tools, a remote server over Streamable HTTP.
Clients Meta documents: Claude Code (claude mcp add --transport http ..., then /mcp to sign in), Claude Desktop (Settings, Connectors, Add custom connector), the OpenAI Codex app and ChatGPT. Clients that only run local servers can use the mcp-remote bridge.
Sign-in: OAuth with your Meta developer account. You must sign in again when you restart the client.
Availability: Meta says it is rolling out gradually, so it may not be available to everyone yet, and that it is in beta, so the tool set may change.

If you are new to the protocol itself, start with MCP for customer messaging.

The tools Meta lists

All tools are prefixed whatsapp_biz_. Grouped by job:

Job	Tools
Discovery	`whatsapp_biz_businesses`, `whatsapp_biz_accounts`, `whatsapp_biz_phone_numbers`
Phone number onboarding	`whatsapp_biz_add_phone_number`, `whatsapp_biz_send_verification_code`, `whatsapp_biz_verify_phone_number`, `whatsapp_biz_register_phone_number`
Message 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` (asks you to confirm the target before sending)
Webhooks	`whatsapp_biz_configure_webhooks`, `whatsapp_biz_subscribe_webhook`
Account setup	`whatsapp_biz_configure_payments`, `whatsapp_biz_verify_business`, `whatsapp_biz_system_user_token`

Meta’s examples are plain requests: “List the businesses I can manage on WhatsApp”, or “Create a marketing template named order_update in en_US”. Most tools work at the level of one business, so a session normally starts by listing your businesses. The system user token tool only returns a link; you generate the token yourself in Business Settings.

Permissions and security

The server asks for three OAuth scopes:

business_management: find and act on the businesses you selected during consent
whatsapp_business_management: manage WhatsApp accounts, phone numbers, templates and webhooks
whatsapp_business_messaging: send messages from registered numbers

You pick the businesses and apps to share on the consent screen, and you can revoke access under Settings, Business Integrations on Facebook. Meta states that reads run under your own user context, that every invocation is logged, and that actions which change state need an authenticated person rather than an app-level credential. Requests are rate limited per user per tool.

What you still need first

The server does not bypass Meta’s rules. Before it can register a number or send a message you need:

Admin access (MANAGE role) to the business.
A WhatsApp-enabled app you administer, connected to that business. Business admin alone is not enough.
Accepted WhatsApp Business Cloud API Terms of Service. Messaging and phone registration are blocked until an admin accepts them.
A payment method and Business Verification. Meta’s announcement says these usually fail quietly, and the server checks them up front.

When something is missing, the tool returns an error that explains the fix and links to the right page.

What it does not do

It is not for production traffic. Meta calls it built for development and testing, not sending at scale.
Free-form text still follows the 24-hour rule. Outside the customer service window you must send an approved template, as with any API call.
It has no inbox. It cannot hold conversation history, route a chat to the right agent, apply working hours or hand over from an AI to a person.
It does not change billing. Meta still charges for messages by category and country; see WhatsApp Business API pricing.

When it is useful, and when it is not

Useful for a developer or agency that sets up many numbers and templates, checks why a webhook is not firing, or wants to confirm an integration end to end with a real test message. Templates are a good example: drafting a first version through an agent is quick, but Meta still reviews every template, and wording that suits the category matters more than speed. Our template message examples show what passes review.

Not the right tool when the goal is to serve customers: receive replies, answer within the 24-hour window, assign a chat, keep notes, run campaigns to opted-in contacts. For that you connect your own WhatsApp Business account to a platform.

Do not mix up the two directions of MCP

Meta’s server lets an AI agent configure your WhatsApp account. The MCP support in MonoChat goes the other way: you add MCP servers so that your AI assistant can use tools while it answers customers, such as looking up an order or booking a slot, with role permissions, allowlists and tool call logs. If you already run your own agent, connect your own AI agent to WhatsApp explains the options.

What this means in MonoChat

MonoChat is an official Meta Business Partner. You connect your own WhatsApp number to Meta’s Cloud API, Meta bills you directly for messages and MonoChat adds no markup. Connecting is a guided flow in the app, so you do not need an agent or code to get started: the support guide walks through it, and templates can be created inside MonoChat or in WhatsApp Manager (template messages guide). Your team then answers WhatsApp, Instagram, Messenger, TikTok, Telegram and web chat from one unified team inbox, and AI assistants can use tools through MCP integration. If you are still choosing a setup route, read WhatsApp Cloud API first. The Basic plan is free and Growth is $120 a month; see pricing or start at app.monochat.ai.

Sources

Meta for Developers, Announcing WhatsApp Business Tools MCP, September 15, 2026
Meta for Developers, WhatsApp Business Tools MCP documentation
Meta for Developers, WhatsApp Business Platform pricing

Put this into practice with MonoChat

All guides