02 Nov 2026
AI & AutomationHow UAE Teams Can Use WhatsApp Business Tools MCP to Speed Up Custom AI Agent Setup
Meta’s WhatsApp Business Tools MCP lets AI coding agents handle account creation, phone verification, templates and webhooks. For UAE businesses building a custom WhatsApp agent that reads CRM or ERP data, this cuts the setup friction so engineering time goes to the actual workflow and guardrails.

On 15 September 2026 Meta released WhatsApp Business Tools MCP, a remote Model Context Protocol server that lets AI coding agents (Claude, Cursor, Codex, ChatGPT) manage WhatsApp Business Platform setup through conversation. The server is hosted by Meta at https://mcp.facebook.com/whatsapp_business_tools, uses Streamable HTTP and OAuth, and is still in beta with gradual rollout. For UAE companies building a custom WhatsApp AI agent that must read live stock, customer prices or appointment slots, the MCP removes the most repetitive parts of Meta’s onboarding so the engineering effort can stay on the agent’s tools, hand-offs and cost controls.
What the MCP actually does
The agent can list the businesses and WhatsApp accounts you administer, add and verify a phone number (OTP still arrives on the phone), register the number for the Cloud API, create or edit message templates, configure webhooks, and send a test message. Meta’s own description is that the agent “checks your Terms of Service status, creates a WhatsApp Business Account, adds your phone number, verifies it over OTP, and registers it for the Cloud API.” Tools are namespaced with whatsapp_biz_ and cover discovery, phone onboarding, templates, messaging and webhooks.
It is a development and testing aid, not a production-scale sending system. Production message delivery still goes through the normal Cloud API and is subject to the post-1 October 2026 service-message billing (first 1,000 free per number per month, then approximately USD 0.0157 / AED 0.0576 for UAE recipients). The MCP does not replace a Business Solution Provider or a custom webhook receiver; it just makes the initial Meta-side configuration faster and less error-prone.
Setup steps that matter for a UAE team
- Prerequisites. Admin (MANAGE) role on the Meta business and admin access to a WhatsApp-enabled app connected to that business. Accepted WhatsApp Business Cloud API Terms. A phone number you control for the OTP.
- Connect the client. For Claude Code:
claude mcp add --transport http whatsapp_business_tools https://mcp.facebook.com/whatsapp_business_tools. Similar steps exist for Claude Desktop, Codex and ChatGPT. Sign in with Meta OAuth and grant the required scopes. - Onboard the number. Ask the agent to list businesses, add the number, send the verification code, verify it with the OTP you read from the phone, then register it. Confirm status with the phone-numbers tool before moving on.
- Templates and webhooks. Describe a utility template (appointment reminder, order update) and let the agent create it. Configure the callback URL your custom agent will use. Send a test message to validate the end-to-end path.
Where this helps a custom agent
Once the number is registered and the webhook points at your system, the custom agent can:
- receive the inbound message inside the 24-hour window,
- call only the tools you define (stock check, customer-specific price, calendar slot),
- reply in Gulf Arabic or English matching the customer,
- hand off with full context when confidence is low or the request involves price, clinical advice or a complaint,
- write a draft or note back to the CRM.
The MCP does not give the coding agent access to your CRM or ERP; that integration still has to be built. What it does is remove the multi-day Meta console dance that used to sit in front of that work. Teams that already have a Meta Business Partner or internal engineering capacity can therefore move from “we need a number” to “we have a testable webhook” in hours rather than days.
Practical limits and next steps
The server is beta and may not be available on every account yet. It does not handle production volume or the customer-facing conversation logic. Arabic dialect quality, live data lookups and hard hand-offs remain the responsibility of the custom agent you build on top of the registered number. After the number is live, the cost control work is the same as any other WhatsApp agent: stay inside the free 1,000 service messages where possible, keep replies short, and log every tool call.
Related reading on Solinify:
- Meta Business Agent vs custom WhatsApp AI agent
- Service message costs after 1 October
- First agentic AI workflow: WhatsApp + CRM
- Governed WhatsApp CRM and AI agents
If the useful reply for your customers already lives in a system you control, the MCP gets the Meta side out of the way so the conversation can focus on which record the agent may read and when it must stop. That is usually a short technical review rather than another platform subscription.
Related Articles

Why 9-Second WhatsApp Response Times Close More Deals (AI Agents Explained)

Every WhatsApp Enquiry Is a Sales Opportunity — Here's How AI Captures It
Ready to build your next big thing?
Solinify Tech Studio specializes in building, launching, and scaling AI-powered products and startups. Let's turn your vision into a future-ready business.
Learn About Venture Studio→