WhatsApp Business Tools MCP: for dev and testing, not production sends
Meta says the WhatsApp Business Tools MCP is for development and testing, not production sending at scale. Use it to set up; send from your code.
Meta's WhatsApp Business Tools MCP, announced September 15, 2026, is built for development and testing workflows, not production sending at scale. Use it to set up your WhatsApp Business account from an AI agent, and keep the production path, where a Sume-rendered video goes to customers, in your own API code.
The announcement says the MCP is currently discoverable on Claude, Codex and ChatGPT, and that it is rolling out gradually, so it may not be available to everyone yet.
What does the MCP do?
Meta describes setup steps that an agent can walk through, plus template and callback help.
| Area | What the agent can do |
|---|---|
| Account setup | Check Terms of Service status, create a WhatsApp Business Account, add a phone number, verify it over OTP, register for the Cloud API |
| Templates | Create or modify message templates and give approval-tracking links |
| Testing | Send a real message from the registered number; configure callback URLs and field subscriptions |
| Prerequisites | Surface missing Terms of Service, payment methods or Business Verification early |
| Auth | Facebook Login for Business with specific scopes; Meta says no tokens land in the prompt history |
Where does a Sume video pipeline fit?
The MCP does the one-time setup. The recurring work is yours: render a clip on Sume, wait for the job to reach completed, and send the media with your WhatsApp Cloud API code. Sume jobs are asynchronous, so submit with an Idempotency-Key and learn the outcome by webhook or by polling status_url; see Jobs and results.
Keep the two concerns apart: if the agent changes templates or callbacks, your renders do not change.
- Use the MCP in a development account to stand up numbers, templates and callbacks.
- Write the production sender as ordinary code with retries and logs.
- Treat a Sume job id as the dedupe key for each customer message.
Sources
Related posts
More in Developers
- Which API key scopes does a Sume webhook receiver need?
Verifying a Sume webhook needs no API key at all. Reading the secret, rotating it, sending a test and redelivering a job each need a different scope.
- Which fields to keep from a Sume submit response
Keep the job id, status_url, result_url, events_url, cancel_url, the sync flags and next_poll_after_seconds. Use generation_limits for pacing only.
- Which login is my agent using? mcp_health auth_source on Sume MCP
Call mcp_health on the hosted Sume server to see the auth source of your session, then tools_list and account_me. Read-only OAuth and API-key sessions differ.
- Which Omni input continues a scene: end frame, reference clip or edit?
Sume has no extend button. Continue an Omni scene with a last-frame image, a 3 s reference clip, or a video edit; this table says which, with costs per 10 s.
Written by Sume