Meta opens WhatsApp Business setup to AI coding agents
On September 15, 2026 Meta announced WhatsApp Business Tools MCP, a server that connects AI coding agents such as Claude, Cursor, Codex and ChatGPT to the WhatsApp Business Platform. Account creation, phone number verification, message templates, a test message and webhook configuration can be driven from inside the agent. Meta labels the release a beta, frames it as a development and testing tool, and is rolling it out gradually.
Setup bureaucracy moves out of the console and into the agent
According to a post on the Meta for Developers blog dated September 15, 2026, Meta announced WhatsApp Business Tools MCP, a server built on the Model Context Protocol. In Meta's description, it connects a service provider's AI coding agent, meaning Claude, Cursor, Codex or ChatGPT, to the WhatsApp Business Platform. The official documentation lists the supported clients as Claude Code, Claude Desktop, the OpenAI Codex app and ChatGPT. The post starts from a familiar pain: setting up a WhatsApp Business integration means bouncing between the Developer Console, Business Manager, the API reference and a code editor, and pasting an access token somewhere it should not go. Naming varies slightly: the blog URL says Business Messaging MCP, while the title and documentation say WhatsApp Business Tools. The documentation marks the release as beta and warns that the interface and tool set may change. In Türkiye, Webrazzi covered the story on September 16, citing Meta's official blog.
From the Terms of Service check to webhooks: the steps the agent runs and the security frame
Meta's post walks through the setup flow in order: the agent checks Terms of Service status, creates a WhatsApp Business Account (WABA), adds a phone number, verifies it with a one-time code and registers it with the Cloud API. It can also create and edit message templates and link to the approval process, send a real test message from the registered number and configure webhooks. Prerequisites such as Terms of Service, a payment method and business verification are surfaced early. The documentation's tool set matches: listing businesses, accounts and phone numbers, phone registration, template creation, update and deletion, sending template messages, webhook configuration, and payment and business verification settings. On security, authentication runs through Facebook Login for Business, an OAuth flow with a Meta developer account and specific scoped permissions; Meta stresses that no tokens land in the prompt history. Before any tool runs, the server checks that the user is an admin of the app, confirms the connected business and the Terms of Service signature, and logs every invocation. Meta draws a clear line: the release is built for development and testing workflows, "not production sending at scale".
Repeated setup steps go to agents, the approval processes stay put
Meta's move is a concrete example of large platforms opening their setup and management surfaces to AI agents. MCP is the protocol that lets agents call tools in external systems; Meta uses it to turn clicks in the Developer Console into tools an agent can invoke. For agencies and service providers on the WhatsApp Business Platform the meaning is clear: opening a WABA, verifying a number, creating templates and wiring webhooks, steps repeated for every new client, can now be managed from a chat window. Meta also points to the complementary Meta Social Technologies MCP server for discovering Graph API endpoints, debugging errors and searching the documentation. The limits still matter. Meta states that the release is meant for development and testing, not production-scale sending; processes on Meta's side such as template approval do not disappear, the agent only links to them. The sources contain no figures, usage statistics or pricing, and give neither a general availability timeline nor the scope after beta.
For businesses in Türkiye: no country detail in the sources, but the preparation order is clear
First the boundary: neither Meta's post, the documentation page nor Webrazzi's coverage gives any information specific to Türkiye or any region. No country or language restriction is stated, but given Meta's gradual rollout note, whether developers in Türkiye can reach the server today cannot be confirmed from the sources. For SMEs that talk to customers over WhatsApp through a Cloud API integration, the manual part of setup is account creation, number verification, template creation and webhooks; running those steps from an agent has the potential to shorten integration time. The order works like this: first complete the prerequisites Meta lists, Terms of Service, a payment method and business verification, because in Meta's account the agent surfaces these gaps at the start. Then confirm that whoever runs the setup has a Meta developer account and admin rights on the app; the server checks this before every tool. Next, run the setup with the agent in a test environment and send the test message from the registered number. Production sending at scale, as Meta states, is outside this release; that layer still runs on the existing Cloud API flow.
The UNALSOFT view
Our reading is this: in WhatsApp integrations, businesses get stuck not on the code but on the setup bureaucracy. An agent that runs those steps in a single window is a gain that lands on day one. That is why the order we recommend to clients in our agentic AI work is this: close prerequisites such as business verification and the payment method first, run the setup with the agent in a test environment, mature your template content and customer flow there, and only then move to production. Meta positions this release as a testing tool, and that is how we recommend using it.
Want to set up your WhatsApp Business integration with agent support?
Let's look together at your setup order, from prerequisites to the test environment and from templates to webhooks. A short conversation is enough to start.