← Back to blog

WhatsApp Business MCP: Meta's setup server vs. the inbox your team actually works in

Published On November 18, 2026

WhatsApp Business MCP: Meta's setup server vs. the inbox your team actually works in

Summary

  • “WhatsApp Business MCP” may refer to three different tools: Meta’s official setup server, Cloud API wrappers that send messages, and inbox MCP servers that read existing conversations.
  • Meta’s server, announced September 15, 2026, supports configuration of WhatsApp Business Accounts, phone numbers, templates, and webhooks. It does not read chat history; Cloud API messages are delivered through business-hosted webhooks.
  • Cloud API messaging has been priced per delivered template since July 1, 2025. Effective October 1, 2026, U.S. and North America rates are US$0.0250 for marketing templates and US$0.0034 for utility templates. The first 1,000 monthly service messages are free.
  • For teams already using the Business app, Kondo’s WhatsApp MCP server connects an AI agent to the existing inbox without Cloud API registration, reading messages through the user’s linked device so data remains on the local machine.

The phrase "WhatsApp Business MCP" now denotes at least three distinct tools, and the official Meta server is almost certainly not the one a given team requires. Most searches for the phrase come from organisations seeking an AI agent that can read their WhatsApp conversations, surface unread chats and draft replies. Meta's server does none of that. Understanding what each layer does — and which problem each one solves — is the purpose of this analysis.

The phrase denotes three distinct categories:

  1. WhatsApp Business Tools MCP — Meta's official server, announced 15 September 2026, engineered for developers setting up and configuring the Cloud API platform.
  2. Community and hosted Cloud API wrappers — open-source or SaaS tools that send and receive messages programmatically via the Cloud API, built by third parties.
  3. Inbox MCP servers — tools that connect an AI agent to the WhatsApp Business app conversations your team already has, on the number you already use.

Only the third category reads existing chats. The first two configure or send. That distinction is the load-bearing point of the analysis that follows.

What Meta Shipped: WhatsApp Business Tools MCP

Meta announced WhatsApp Business Tools MCP on September 15, 2026. The MCP server connects AI coding agents—including Claude, Cursor, Codex, and ChatGPT—to the WhatsApp Business Platform within a developer’s existing workflow.

It cannot read a business’s chat history. This is an intentional scope boundary, not a technical limitation to bypass. As The New Stack reports, the server does not provide access to historical business conversations.

Instead, it supports developer configuration and testing tasks, including:

  • Creating WhatsApp Business Accounts (WABAs)
  • Adding and verifying phone numbers through SMS or voice OTP
  • Registering numbers for Cloud API access
  • Creating, viewing, editing, and deleting message templates
  • Configuring and testing webhooks
  • Sending test messages
  • Checking setup status, including Terms of Service acceptance, payment setup, and business-verification status

Access is limited to businesses explicitly selected by the developer. Connecting an agent does not grant access to every Meta account available to that user. Read operations run in the connecting user’s context, invocations are logged, and state-changing actions require authenticated user authorization rather than an app-level credential.

The server is currently in beta and is being rolled out gradually, so its tools and interface may change.

Meta Social Technologies MCP is a separate, complementary server. Its focus is broader developer support: discovering Graph API endpoints, searching Meta documentation, inspecting integration apps, and troubleshooting platform errors. The two services are not interchangeable. WhatsApp Business Tools MCP supports WhatsApp configuration, while Meta Social Technologies MCP supports development across Meta’s ecosystem. As Mixdesk explains, Business Tools MCP operates above the Cloud API and does not provide a customer-service inbox or live support workflow.

Where Conversations Actually Land: The Webhook Problem

Meta’s setup server exists because the WhatsApp Cloud API does not provide an inbox that businesses can poll or use to retrieve conversations. Inbound messages are delivered only through webhook POST requests to an HTTPS endpoint that the business owns and maintains. There is no API for retrieving historical conversations.

Operating a reliable webhook receiver requires real infrastructure, including:

  • A public HTTPS endpoint with a valid TLS certificate
  • Support for Meta’s hub.challenge verification process
  • X-Hub-Signature-256 HMAC validation for every incoming request
  • A queue or similar mechanism that allows the endpoint to return 200 OK immediately and avoid timeout failures

If the webhook remains unavailable for an extended period, Meta may permanently drop undelivered messages. Conversation history exists only where the receiving system stores it—such as a CRM, database, or support platform. Meta’s MCP server can help configure the webhook destination, but it does not access or retain the messages delivered through it.

This is why Cloud API setup and inbox functionality are separate problems. The Cloud API is the delivery channel; the inbox, CRM, or support platform is what captures, stores, and operationalizes the conversations. Configuring the delivery channel does not create an inbox.

[@portabletext/react] Unknown block type "image", specify a component for it in the `components.types` prop

The three categories compared

| WhatsApp Business Tools MCP (Meta, official) | Cloud API wrappers (community / hosted) | Inbox MCP (e.g. Kondo)

Primary job | Set up and configure the Cloud API platform | Send and receive messages programmatically | Read existing chats and draft replies

Reads existing conversations? | No | No — receives new messages via webhook only | Yes

Connects to | WhatsApp Business Platform (API layer) | WhatsApp Business Platform (API layer) | The existing WhatsApp Business app (linked device)

Outbound messages | Test messages only | Sends directly; metered per message | Saves drafts for human review only

Typical user | Developer standing up a new number | Developer or automation builder | Sales teams, recruiters, support teams

Setup | Connect agent, sign in with Meta account | Requires App ID, Phone Number ID, and API tokens as environment variables | Install desktop app, add MCP endpoint, authorize

The first two columns are infrastructure for developers building messaging features; the third is an inbox professionals use every day.

Cloud API Wrappers: Capabilities and Cost

Community wrappers, such as networkerman/whatsapp-cloud-api-mcp-server, and hosted connectors, such as Zapier’s WhatsApp Business MCP, expose tools for programmatic messaging. Zapier’s server, for example, offers tools to send freeform, media, and template messages, as well as retrieve attachments. It does not provide a tool for listing or reading existing chats.

These tools remain subject to Cloud API rules, including the 24-hour customer-service window. When a customer contacts a business, the message opens a 24-hour window for freeform responses; each subsequent customer message restarts that window. Outside the window, the business must use a Meta-approved message template, which may be billed.

Pricing is therefore relevant. Since July 1, 2025, the WhatsApp Business Platform has billed per delivered template message rather than per 24-hour conversation. Effective October 1, 2026, U.S. and North America rates are US$0.0250 for marketing messages and US$0.0034 for utility messages. The first 1,000 monthly service messages are free; additional service messages are billed.

A broad toolset connected to a live messaging API is a tradeoff, not a defect. Because sending occurs through code, an incorrect prompt or automated action can result in a billable message or a message sent outside Meta’s approved template and service-window requirements. These tools are best suited to developers who can review and control the actions an agent takes.

For teams seeking a lower-risk approach—reading and drafting within the WhatsApp Business inbox they already use, without connecting an agent to a live sending API—Kondo’s inbox MCP server is the relevant alternative, discussed next.

The Inbox Your Team Actually Uses: Kondo’s MCP Server

Kondo is a professional direct-message inbox for LinkedIn, WhatsApp, and iMessage, designed for sales teams, recruiters, founders, coaches, investors, creators, and their AI agents. For WhatsApp, it addresses the inbox workflow that Meta’s setup server does not provide.

Kondo’s MCP server connects an AI agent to WhatsApp Business conversations already available on the user’s local machine. It does not use the Cloud API to read messages and operates with the business number already in use.

Setup

  1. Install the Kondo Desktop app for macOS, Windows, or Linux.
  2. Add https://mcp.trykondo.com/mcp as a Streamable HTTP MCP server in your AI client.
  3. Sign in to Kondo and authorize the connection. You can disconnect it at any time through Kondo → Settings → MCP.

For AI clients that support skill-based setup, use: Set up Kondo for me.

The MCP server is compatible with Claude, ChatGPT, Gemini, Copilot, and Cursor.

What the agent can do

  • List and search chats and contacts
  • Identify unread messages and conversations awaiting a response
  • Read conversation history, including voice-note transcripts
  • Draft replies for review
  • Apply or remove labels
  • Add contact notes and follow-up reminders
  • Archive, ignore, or restore chats
  • Mark conversations read or unread, and mute or unmute them

What the agent cannot do

The agent cannot send messages. AI-generated responses are saved as drafts for a team member to review and send manually. Kondo’s MCP toolset includes no send function and does not support automated outreach sequences.

Messages and contacts remain on the user’s computer. Kondo reads them through the existing WhatsApp linked device, and credentials are not shared with the AI assistant. This is the practical distinction from a Cloud API wrapper: an incorrect prompt creates a draft rather than a billable outbound message.

Requirements

A Kondo Business plan account, which includes a 14-day money-back guarantee, and the Kondo Desktop app running on the same machine. The MCP server is available only while the desktop app remains open.

[@portabletext/react] Unknown block type "image", specify a component for it in the `components.types` prop

Can You Use Both? The Coexistence Model

Coexistence allows a WhatsApp Business number that already contains customer conversations to operate on both the Business app and the Cloud API. It is designed for teams that need automation without moving their number or abandoning their existing inbox.

Meta’s coexistence flow enables one number to remain active in both environments, with one-to-one chats and contacts mirrored between them. This allows teams to send automated template messages—such as shipping updates, appointment reminders, and OTP codes—through the Cloud API while continuing to manage inbound conversations and follow-ups in the WhatsApp Business app. Kondo can provide an AI layer for the app-based inbox workflow.

Before adopting coexistence, teams should understand its constraints:

  • It is not self-service; a Meta-approved Solution Partner must initiate onboarding.
  • The number must run WhatsApp Business app version 2.24.17 or later.
  • The number must have been actively used in the Business app for at least seven days before onboarding.
  • A number already registered as a standard Cloud API number cannot be enrolled in coexistence. The documented recovery process requires deleting the WABA registration, re-registering the number in the Business app, and waiting one to two months before retrying.
  • Broadcast lists become read-only after coexistence is enabled.
  • Some customers may see the phone number rather than the business display name in the chat header.
  • Meta Verified subscriptions have been reported to stop working after coexistence is enabled.

For teams already operating in the WhatsApp Business app without prior Cloud API registration, coexistence can be a viable option. For numbers with a more complex Cloud API history, the setup process may involve significant friction.

Which Path Should You Take?

The right option depends on the work you need to perform.

For developers setting up a new WhatsApp Business account for Cloud API messaging: Start with WhatsApp Business Tools MCP. It supports WABA creation, phone-number verification, template setup, and webhook configuration in a connected developer workflow, reducing the need to switch among Meta Business Manager interfaces.

For sales teams, recruiters, and entrepreneurs already using the WhatsApp Business app: Choose an inbox MCP. The Cloud API is not designed to read or manage the existing inbox. Kondo’s WhatsApp MCP server connects to the conversations already in place, without Cloud API registration or per-message charges for reading chats. Teams working in both channels can also use Kondo’s LinkedIn MCP server to manage LinkedIn conversations through the same inbox layer.

For organizations that need high-volume programmatic sending and an inbox team on the same number: Use the coexistence model. Meta’s setup server configures the Cloud API side, while Kondo supports the team’s inbox workflow. Coexistence requires careful planning: onboarding sequence matters, and recovery from a failed setup can take months rather than days.

Frequently asked questions

What is WhatsApp Business MCP?

The label usually denotes an MCP server that connects an AI assistant to WhatsApp. It covers three separate tools: Meta's official setup server, community Cloud API wrappers that send messages, and inbox servers such as Kondo that read existing chats and draft replies.

Is there an official WhatsApp Business MCP server?

Yes. Meta announced WhatsApp Business Tools MCP on 15 September 2026. It is a developer tool for configuring the Cloud API: creating a WhatsApp Business Account, verifying a number, managing templates and test messages, and setting up webhooks. It is in beta with a gradual rollout.

Can Claude or ChatGPT read my WhatsApp messages?

Not through Meta's MCP server, which cannot access chat history. To give Claude, ChatGPT, Gemini or Cursor access to a WhatsApp inbox, an inbox MCP server such as Kondo is connected to the WhatsApp Business app already in use. It reads through the user's own linked device, so messages stay on the computer; the AI provider selected is the only outside service that sees message content.

Do I need the WhatsApp Cloud API to give an AI agent access to my inbox?

No. The Cloud API has no inbox to read — inbound messages arrive only as webhooks to a server the business owns. An inbox MCP server connects to the WhatsApp Business app conversations already on the computer, with no API registration, tokens or per-message fees.

Can an AI agent send WhatsApp messages automatically?

With Kondo, no. Every AI-generated reply is saved as a draft, and a person reviews and sends it manually. There is no send tool in Kondo's tool set. Cloud API wrappers are a separate category: they expose sending as a call from code, and they are metered and bound by the 24-hour service window and template rules.

What is the difference between WhatsApp Business Tools MCP and Meta Social Technologies MCP?

They are complementary servers. WhatsApp Business Tools MCP configures the WhatsApp platform: accounts, numbers, templates and webhooks. Meta Social Technologies MCP is broader developer tooling — discovering Graph API endpoints, searching Meta's docs and troubleshooting integration errors.

Can I use the WhatsApp Business app and the Cloud API on the same number?

Yes, through Meta's coexistence flow, but it is not self-serve. A Meta-approved Solution Partner must initiate it, the number needs seven days of active Business app use, and broadcast lists become read-only. Numbers already registered for the Cloud API must be deregistered first.