Meta releases WhatsApp Business Tools MCP for Claude, Cursor, Codex and ChatGPT

Meta released a new Model Context Protocol server on 15 September 2026 that lets an AI coding agent set up and manage WhatsApp Business messaging by conversation. Meta's own blog post, written by product marketing lead Zoë Lieberman, says the server is currently discoverable on Claude, Cursor, Codex and ChatGPT, and covers account creation, phone number verification, Cloud API registration, message template authoring, webhook configuration, and sending a test message. Meta says the release is built for development and testing, not production sending at scale.

What the agent can actually do

The setup path is the busiest change. Getting a business onto WhatsApp used to mean moving between the Meta Developer Console, Business Manager, the API reference and an editor to connect and verify a phone number and check three prerequisites (Terms of Service, payment method, Business Verification) that Meta says "usually fail quietly". The MCP walks the same path from a chat window: the agent creates the WhatsApp Business account, adds the phone number, prompts the developer for the one-time SMS or voice code, and registers the number for the Cloud API.

The same MCP also handles the recurring work: creating and editing message templates with headers, body, footers and buttons, configuring webhooks for incoming messages, sending a real test message to check the whole path, and inspecting the account so an agent can be asked what is configured and what is missing.

The guardrails Meta names

Every state-changing action requires a signed-in admin, not an app-level credential, according to the blog post. The developer signs in through Facebook Login for Business and grants a specific set of scopes, so nothing lands in the agent's prompt history. Meta writes that before any tool runs the server confirms the caller is an app admin, resolves the attached business, and checks that the Terms of Service are signed. Every read runs under the developer's viewer context, and every invocation is logged.

Access is scoped to the businesses the developer picks at connect time. Handing the agent access does not give it every Meta account the developer administers.

How this fits alongside Meta's other MCP

Meta launched a broader Developer Tools MCP in June, since renamed to Meta Social Technologies MCP, which lets an agent discover Graph API endpoints, search the docs and inspect an app. Meta says the two are complementary: install both if you need both. Meta also notes the WhatsApp MCP is rolling out gradually and may not be available to every developer yet.

The pattern is not new

Meta joins a list of platforms that already ship MCP servers for their developer surface, including Stripe, PayPal, GitHub, Notion, Slack, Salesforce, Atlassian, X, Google and Microsoft. What is new here is what the MCP is pointed at: first-time WhatsApp Business onboarding, a job most developers do once and forget, so the pain of doing it well by hand had piled up in the docs rather than in a tool. A team already building against WhatsApp Cloud API has less to gain from this than a team standing up a new integration.

Source

Announcing WhatsApp Business Tools MCP: Set up and manage WhatsApp business from your AI agent, Zoë Lieberman, Meta for Developers, 15 September 2026. Reporting: Meta lets Claude and Codex configure WhatsApp Business via MCP, Paul Hill, The New Stack, 15 September 2026, and Meta now lets AI agents handle the boring parts of WhatsApp Business setup, Sarah Perez, TechCrunch, 15 September 2026.