Skip to content
Custom Connectors

Connect WhatsApp Business to Claude Code

Let Claude draft replies and send approved templates in WhatsApp Business. From the terminal, inside the sessions where you already work.

How do you connect WhatsApp Business to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect WhatsApp Business, you add a WhatsApp Business MCP server: a small hosted service that exposes WhatsApp Business's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own WhatsApp Business account. No API keys pasted into config files.

claude mcp add --transport http whatsapp-business https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in WhatsApp Business once connected?

Full read-write WhatsApp Business access lets Claude draft a reply inside an open conversation, send approved template messages, mark chats read, send interactive button or list menus, and queue outbound messages once you approve. The triage and customer replies that used to mean switching apps happen where the conversation already lives, within Meta's session and template rules.

  • Draft a reply inside an open customer conversation, preserving context
  • Send a pre-approved template message after you approve it
  • Send an interactive button or list menu to triage incoming chats
  • Mark conversations read as you clear the queue
  • Pull every chat matching a query and propose batched replies
  • Queue an outbound message within the allowed customer session window

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same WhatsApp Business access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the WhatsApp Business API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when WhatsApp Business changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build WhatsApp Business connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same WhatsApp Business connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own WhatsApp Business account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on WhatsApp Business's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to WhatsApp Business?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the WhatsApp Business account it signs in with. Revoking access is one click in WhatsApp Business.

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.