Do you need Meta's Cloud API if you already use Wati MCP?

Yes. Wati MCP manages contacts, conversations, campaigns, and templates through Claude, but it still needs an active WhatsApp Business Account and phone number that only Meta's Cloud API onboarding sets up, including the permanent access token and webhook configuration.

What is the Wati MCP server URL for Claude?

Wati's documented server URL is https://mcp.wati.io/mcp. You add it under Claude's Customize > Connectors menu as a remote MCP custom connector, then authenticate with OAuth before any tool becomes available.

Is there a separate server URL for EU accounts?

Yes. Wati or Astra accounts hosted on the EU instance use https://eu-mcp.wati.io/mcp instead of the default URL. Using the wrong region's address is the most common reason a Claude connection fails on the first try.

How does Claude authenticate with Wati MCP?

The connection uses OAuth, meaning you log in and grant access rather than pasting an API key directly into Claude. This keeps your Wati credentials out of the chat window and lets you revoke access anytime from your account settings.

Can Claude send a WhatsApp campaign without human approval?

No safe setup should allow that. Every message, template, or automation rule Wati MCP triggers passes through Claude's connector authentication first, and you should treat each campaign send as a step to review, not a background action.

What happens if you message a contact outside the active conversation window?

Meta's template rules mean free-form replies only work inside an active customer-service conversation. Outside that window, only pre-approved template messages will deliver, so campaigns and reactivation outreach must always use an approved template, not a plain message.

Connect Claude to WhatsApp Business API in 2026

Most guides treat Claude and WhatsApp as separate projects: one for developers wiring up Meta's API, one for marketers running campaigns. That split is unnecessary once you understand what each layer actually does.

Meta's Cloud API gives you the messaging infrastructure: a verified number, tokens, webhooks.

Wati MCP gives you a way to operate that infrastructure from inside a Claude conversation, in plain language, without writing API calls yourself.

This guide covers Meta's onboarding sequence, the exact Claude connector steps, the current Wati MCP server URL and its EU alternative, a simple way to verify your connection, and the practical use cases and safeguards that matter once real contacts are involved.

How Does Meta's WhatsApp Cloud API Onboarding Work?

Meta's Cloud API onboarding is a fixed sequence you complete once per WhatsApp Business Account, and every later integration depends on it.

The Eight Setup Steps You'll Walk Through

Meta's own get-started documentation lays out an eight-step onboarding sequence that takes you from a blank developer account to a working test number.

Step	What Happens
1	Create a Meta app and add the WhatsApp product
2	Select or create a business portfolio
3	Connect or create a WhatsApp Business Account
4	Generate a temporary access token
5	Select a phone number for testing
6	Send a test message to confirm setup
7	Configure webhooks for inbound events
8	Create a system user and issue a permanent token

If you have not walked through this before, our guide on setting up WhatsApp Business API covers the same ground in more depth, including common approval delays worth planning around.

Which Permissions Does the Permanent Token Need?

The permanent token is what keeps your integration alive after the temporary one expires, and Meta scopes it tightly on purpose.

Meta's documentation names three permissions for this step: business_management, whatsapp_business_messaging, and whatsapp_business_management.

Skip any one of them and later steps, like sending template messages, will fail with permission errors rather than obvious ones.

Why Add Wati MCP on Top of the Cloud API?

The Cloud API gives you a working phone number and token. It does not give you a way to manage contacts, run campaigns, or read conversations without writing code against Meta's endpoints yourself.

Wati MCP fills that gap. It sits between Claude and your WhatsApp account as a conversational operations layer, so tasks that would otherwise mean API calls become plain prompts instead.

Aspect	Meta WhatsApp Cloud API	Wati MCP
Role	Underlying messaging infrastructure	Conversational operations layer
You work in	Meta's developer console, raw API calls	Claude, plain-language prompts
Handles	Phone numbers, tokens, webhooks	Contacts, conversations, campaigns, templates, automation
Best for	One-time infrastructure setup	Day-to-day WhatsApp operations

Think of the Cloud API as the pipe and Wati MCP as the tap you actually turn.

For a deeper look at how the WhatsApp MCP server fits alongside the Cloud API rather than replacing it, that piece walks through the architecture in more detail.

How Do You Connect Claude to Wati MCP?

Connecting Claude to Wati MCP takes about five minutes once your WhatsApp Business Account exists, and it does not require any code.

Step-by-Step: Adding the Custom Connector

Claude's remote MCP flow lives under Customize, then Connectors. Follow these steps in order.

Open Claude and go to Settings, then Customize.
Select Connectors, then choose Add custom connector.
Paste in the Wati MCP server URL for your region.
Confirm the connector name and select Add.
Authenticate through the OAuth prompt that appears.
Grant access when Claude asks for confirmation.

Anthropic's connector documentation notes that Pro and Max users can add a connector directly, while Team and Enterprise plans route setup through an organization owner first, who configures the connector before individual members connect.

Choosing the Right Server URL for Your Region

Wati documents the Claude MCP server for standard accounts. If your Wati account runs on the EU instance, use https://eu-mcp.wati.io/mcp instead; pasting the default URL into an EU account is the single most common cause of a failed first connection.

Authenticating with OAuth

Wati's documented connection method uses OAuth rather than a static API key pasted into chat. You log in through a normal authentication screen, grant Claude access to your Wati account, and revoke that access later from your account settings if needed.

Nothing about your Wati password ever appears inside the Claude interface itself.

How Do You Verify the Connection Works?

A working connection should answer a simple, low-risk prompt correctly before you trust it with anything customer-facing.

Once the connector shows as active, try a prompt like: "Using Wati MCP, list my five most recent WhatsApp conversations."

If Claude returns real conversation data instead of an error or a generic answer, the connector is authenticated and reading from your account correctly. Run this check again after any Wati password change, since OAuth sessions can expire without warning.

9 Practical Wati MCP Use Cases Inside Claude

Once connected, Wati MCP turns a Claude conversation into a working console for contacts, conversations, campaigns, and templates.

Managing Contacts and Segmentation

Ask Claude to pull a contact list, add a new lead, or check whether someone already exists before you message them. This keeps segmentation work inside the same chat where you plan a campaign, instead of switching tools mid-task.

Reading Conversations in the Team Inbox

Claude can list your ongoing conversations so you can spot unanswered chats, review tone, or hand a summary to a teammate. It reads what is already in your Team Inbox rather than creating a second inbox to maintain.

Sending Session Messages Inside the Service Window

Within an active customer conversation, Claude can send a session message on your behalf, useful for quick replies drafted with AI help but still sent under your review. This only works while the conversation window is open.

Sending Template Messages and Campaigns

For outreach outside an open conversation, Claude sends approved template messages instead, the only message type Meta allows once a session has closed.

This is the mechanism behind broadcast-style outreach, and our guide on sending bulk WhatsApp messages covers the volume and pacing considerations that apply either way.

Browsing Your Approved Template Library

Before drafting a campaign, ask Claude to list your approved templates so you are not guessing which wording Meta has already cleared. This avoids drafting copy that then gets rejected at send time.

Syncing Contacts with Google Sheets

Wati MCP can sync contact and campaign data with Google Sheets, letting a marketing team keep segmentation lists in a familiar spreadsheet while Claude reads and writes to them directly.

Automating Rules for Repetitive Work

Rather than manually tagging or routing every inbound message, Claude can set up automation rules that trigger based on conditions you describe. This pairs well with the patterns covered in automating WhatsApp support, applied through natural-language setup instead of a rules builder UI.

Triggering Webhooks for Other Systems

When a WhatsApp event needs to reach another system (a CRM, a helpdesk, a custom dashboard), Claude can create a webhook pointed at that system, so the data flows out automatically rather than through manual export.

Building WhatsApp AI Agents on Top of It All

Combine conversation reading, template sending, and automation rules, and you have the building blocks of a WhatsApp AI agent that qualifies leads or answers routine questions before a human steps in.

If you are exploring what an AI agent actually does in a WhatsApp context, this is the layer that makes it work.

What are Meta's Template and Customer-Service Window Rules?

Meta only allows free-form messaging inside an active customer-service conversation; everything outside that window has to use a pre-approved template.

Meta's template documentation explains that businesses need approval on message templates before sending them outside an open conversation, covering wording, formatting, and category.

This is why every campaign built through Wati MCP should pull from your approved template library rather than freehand text, and why checking WhatsApp service message pricing alongside template rules matters before scaling outreach: session messages and template messages are billed and governed differently.

This also underpins good conversational marketing statistics: reactivation outreach depends entirely on approved templates, not on an open window that may have already closed.

Ecommerce teams running order updates through WhatsApp API for ecommerce flows hit this rule constantly, since post-purchase messages often land outside the service window.

Getting your creative promotional message templates approved ahead of a campaign avoids a last-minute scramble.

What Permissions Does Claude Need Before It Can Send a Message?

Claude cannot use Wati MCP at all until you complete the OAuth authentication step, and that authentication is the first safeguard, not an afterthought.

Because the connection runs through Claude's own connector framework, every tool call (sending a message, creating a contact, firing a webhook) sits behind that same authenticated session rather than a loose API key floating in chat history.

On Team and Enterprise plans, an organization owner configures the connector before individual members can even attempt to connect, adding an admin-level checkpoint above the individual OAuth grant.

Free plan users are capped at one custom connector, which in practice forces a deliberate choice about what gets connected rather than adding tools casually. Treat every campaign send as something you review before it fires, not something you assume Claude will handle silently in the background.

Ready to Run WhatsApp Campaigns from Claude?

Connecting Claude to WhatsApp Business API is a one-time setup, but the daily payoff is running contacts, conversations, and campaigns without leaving a chat window.

If you want a walkthrough tailored to your own WhatsApp setup, book a demo with Wati and bring your specific use case.