01
Overview
Meta has launched WhatsApp Business Tools MCP, a first-party Model Context Protocol server designed to let AI coding agents help set up and manage parts of the WhatsApp Business Platform. Instead of moving repeatedly between Meta's Developer Console, Business Manager, API documentation and a code editor, a developer can describe supported setup tasks to an agent and let that agent carry them out through the MCP connection.
02
What is WhatsApp Business Tools MCP?
WhatsApp Business Tools MCP is an official agent-facing interface for WhatsApp Business Platform setup and testing. Launch reporting based on Meta's developer announcement names Claude, Cursor, Codex and ChatGPT among the compatible coding-agent environments.
The important distinction is that this is not a new consumer WhatsApp chatbot and it is not a replacement for the WhatsApp Business Platform. It is a tool layer that lets an authenticated AI agent perform supported configuration work against the platform.
03
What can it do?
At launch, Meta says the MCP can assist with several common onboarding and development jobs: creating a WhatsApp Business Account; adding and verifying a business phone number; registering the number for Cloud API access; checking required Terms of Service state; creating or editing message templates; checking template approval state; sending test messages; configuring and testing webhooks; and identifying setup blockers involving items such as payment methods or Business Verification.
Those capabilities make the release especially relevant to developers who configure WhatsApp integrations infrequently. The MCP changes the interface for the work—from navigating several consoles and documents to directing an agent conversationally—but it does not remove Meta's underlying account, verification, permission or policy requirements.
04
Which AI agents work with it?
Launch material and reporting identify Claude, Cursor, Codex and ChatGPT as discovery or usage surfaces. Availability can change as agent clients add or modify MCP support, so this should be treated as a launch-state list rather than a permanent compatibility guarantee.
05
Authentication and permissions
The agent does not receive unrestricted access to every Meta asset a developer can reach. Reporting based on Meta's documentation says the connection uses Facebook Login for Business and specific permissions. State-changing operations remain tied to an authenticated human/admin context, reads operate within the user's access context, and tool calls are logged.
This matters because MCP makes actions easier to request, not permissionless. A business should still review which account and business assets are selected during connection and which permissions the agent receives.
07
Is it available to everyone?
No universal-access claim should be made yet. Meta is rolling the tool out gradually, and launch reporting says it may not be available to every developer immediately. If it is not visible in an agent or account, rollout status, account eligibility and client-side MCP support are all possible factors to check before assuming the product is broken.
08
Is it for production messaging?
Meta's launch positioning describes the current tool as intended for development and testing rather than as a production messaging-at-scale system. Businesses still use the underlying WhatsApp Business Platform and Cloud API for production messaging. The MCP helps configure and test that environment.
09
Pricing
No standalone price for WhatsApp Business Tools MCP was verified at launch. That should not be interpreted as proof that every related WhatsApp Business Platform action is free; existing platform pricing and account requirements remain separate questions.
10
Why this launch matters
The larger shift is that a major business-messaging platform is exposing operational setup to general-purpose coding agents through a standard protocol. MCP started as a way for models to discover context and tools, but releases like this increasingly let agents perform real administrative work after authentication.
For businesses, that can shorten the path from 'we want WhatsApp messaging' to a testable integration. For developers, it can reduce the amount of one-off console work involved in onboarding. The trade-off is that permission review, human oversight and verification become more important because the agent can now request state-changing actions rather than merely explain documentation.
11
FAQ
Can ChatGPT configure WhatsApp Business with MCP?
Meta's launch material lists ChatGPT among the agent environments where WhatsApp Business Tools MCP can be discovered or used. Exact availability may vary during rollout.
Can Claude or Codex use WhatsApp Business Tools MCP?
Yes, Claude and Codex are named among supported/discoverable coding-agent environments in launch reporting based on Meta's announcement.
Can the MCP create WhatsApp message templates?
Meta says supported workflows include creating and editing messaging templates and checking their approval status.
Can it configure webhooks?
Yes. The launch includes webhook setup/testing workflows, alongside test messages and setup checks.
Does it bypass Business Verification?
No. The MCP can help identify verification or configuration blockers; it does not eliminate Meta's verification and policy requirements.
Is WhatsApp Business Tools MCP a production messaging API?
No. It is an agent-facing setup and management tool around the WhatsApp Business Platform. Meta currently positions it for development and testing rather than production messaging at scale.
12
Sources and verification note
Material capabilities above are based on Meta's September 15, 2026 developer announcement as described by TechCrunch, Mint and other launch reporting. The dedicated first-party Meta page should be rechecked immediately before publication because its indexed URL did not surface directly in this radar run. Volatile rollout, compatibility and permission details should be verified again before approval.
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.