How to Connect WhatsApp to Claude (MCP Integration Setup Guide)

Connect WhatsApp to Claude by adding the Blueticks MCP server to your MCP client and authenticating with a Blueticks API key. Claude can then send, schedule, and read WhatsApp messages from your own number in plain language.

1. Connect your WhatsApp number to Blueticks so an engine is live.
2. Generate a Blueticks API key (it starts with bt_live_).
3. Add the Blueticks MCP server to Claude and paste the key.
4. Restart Claude and confirm the WhatsApp tools load.
5. Ask Claude to send a test message, and watch it go out from your number.

How to connect WhatsApp to Claude (MCP integration)

To connect WhatsApp to Claude you link your WhatsApp number to Blueticks, create a Blueticks API key, register the Blueticks MCP server in your Claude client with that key, and verify the tools appear. Then Claude can send WhatsApp from Claude directly.

This is a five-step setup and none of it involves Meta's developer console. You're wiring your own WhatsApp number into Claude through a WhatsApp MCP server, so the messages Claude sends come from you, not from a separate business identity. The steps below are the current happy path. Where a config detail can drift between clients, I point you at the live Blueticks docs instead of guessing.

Step 1 — Connect your WhatsApp number to Blueticks

Before Claude can touch WhatsApp, you need a running Blueticks engine tied to your number. Sign up at blueticks.co, then link your WhatsApp the way you'd link WhatsApp Web: scan a QR code so your session is live. The engine is the part that actually holds your WhatsApp connection. The MCP server you add later just gives Claude a set of tools that drive that engine.

If you want the offline version, where sends fire even when your laptop is closed, that's the Blueticks Pro gateway that parks your session on Blueticks' servers. Either way, the requirement for this step is the same: a connected number Claude can send through.

Step 2 — Generate a Blueticks API key (bt_live_)

The key is how Claude proves it's allowed to act as you. Open the Blueticks API dashboard, click "Create key," and copy the value immediately, because it's shown once and never again (dev.blueticks.co). The key is formatted bt_live_… and should be treated as a password. Never paste it into a chat, commit it to a repo, or drop it in a public config.

You can sanity-check the key before you wire it into Claude. The Blueticks API exposes a GET /v1/ping endpoint that validates the key and returns your account ID plus the connected WhatsApp engine info (dev.blueticks.co). If ping comes back with your engine, the key works and your number is reachable. If it errors, fix that here, not three steps later inside Claude.

Step 3 — Add the Blueticks MCP server to Claude

Claude reaches WhatsApp through the @blueticks/mcp server, a stdio MCP server you run on demand with npx, so there's nothing to install into a project (Blueticks MCP docs). You register it in your Claude client's MCP configuration and hand it the key from Step 2 as an environment variable. The config block Blueticks documents for Claude Desktop is:

{
  "mcpServers": {
    "blueticks": {
      "command": "npx",
      "args": ["-y", "@blueticks/mcp"],
      "env": {
        "BLUETICKS_API_KEY": "bt_live_your_key_here"
      }
    }
  }
}

Claude Code and Cursor use the same server and the same BLUETICKS_API_KEY variable, just in each client's own config location (Blueticks MCP docs). Config file paths and UI move around as clients update, so if a screen doesn't match, follow the current setup steps in the Blueticks docs at dev.blueticks.co rather than an old screenshot. The one constant is what you're doing: point your MCP client at the Blueticks MCP server and authenticate with your bt_live_ key.

Step 4 — Authenticate and verify the tools load

Fully restart Claude after saving the config. MCP servers are read at startup, so a running window won't pick up a server you just added. When Claude relaunches, it starts the Blueticks server, passes your key, and the WhatsApp tools become available in that session.

To verify, ask Claude something read-only first, like "list my recent WhatsApp chats" or "what WhatsApp tools do you have?" If the mcp WhatsApp tools loaded, Claude answers using them. If it says it has no WhatsApp access, the server didn't start or the key didn't authenticate, and the troubleshooting section below covers both.

Step 5 — Send your first WhatsApp message from Claude

Now do the real thing. Tell Claude, in plain language, to message someone: "Send a WhatsApp to +1 555 010 0199 saying the invoice is attached and I'll follow up Friday." Claude maps that to the Blueticks send tool, and the message leaves from your WhatsApp number. Watch your phone. It shows up in your sent messages like anything else you'd type by hand, because it is your account sending.

That's the whole Claude WhatsApp integration. Everything after this is Claude choosing the right tool for what you ask.

Skip Meta's developer console entirely. You don't need a Business API account, a provider contract, or per-message fees to let Claude message people from your own WhatsApp. Create a Blueticks account, generate a key, and connect Claude in a few minutes. Get your Blueticks API key.

What is MCP, and how does Claude use it to reach WhatsApp?

MCP, the Model Context Protocol, is an open standard that connects AI applications like Claude to external tools and data through a consistent interface. Claude runs an MCP client, Blueticks runs an MCP server exposing WhatsApp tools, and Claude calls those tools to send or read messages.

The Model Context Protocol documentation describes MCP as "an open-source standard for connecting AI applications to external systems" and compares it to a USB-C port for AI: one standardized way to plug an AI app into outside data, tools, and workflows (modelcontextprotocol.io). Before MCP, every AI-to-tool link was a bespoke integration. MCP replaces that with a common protocol, which is why the same Blueticks server works across Claude Desktop, Claude Code, and Cursor without a rewrite.

The moving parts are worth getting straight, because they decide where things can break:

• The MCP client is Claude. It's the side that wants to do something and asks for tools.
• The MCP server is Blueticks (@blueticks/mcp). It advertises a set of WhatsApp tools and knows how to run them.
• The tools are the actual actions: send a message, list chats, start a campaign. Each one wraps a Blueticks /v1 API call under the hood.

So when you ask Claude to message a client, Claude picks the send tool, the Blueticks server translates it into a /v1 call authenticated with your key, and your engine delivers it on WhatsApp. If you want the deeper background on this pattern, the primer on WhatsApp and MCP walks through the architecture without assuming you've set anything up yet.

What can Claude do with WhatsApp once connected?

Once connected, Claude can read and search your WhatsApp conversations, help you triage them, and draft replies, and it can also send, schedule, and manage messages, campaigns, groups, and contacts from your number. The Blueticks server exposes nine tool families covering the full set.

Lead with the part that's underrated: reading and triage. Claude can pull recent chats, search conversation history, and load older messages through the chats tools (Blueticks MCP docs). That means you can ask "which WhatsApp threads from this week still need a reply?" and get a triaged list, then "draft a friendly follow-up to the three that mention pricing" and review the drafts before anything sends. The read-triage-draft loop is where the whatsapp Claude combo saves the most time, because reading and prioritizing is the tedious part, not typing.

Then there's the write path, where Claude actually acts:

• Send now: "Text Maria the meeting moved to 3pm." Straight send from your number.
• Schedule: "Send this reminder every client on Monday at 9am." Claude sets it and the queue fires later. I don't re-teach scheduling here; the companion guide on scheduling WhatsApp messages from Claude via MCP covers timing, recurrence, and the gotchas in depth. This article is the connect-and-setup half; that one is the day-to-day scheduling half.
• Campaigns and audiences: build a templated campaign and append contacts with personalization variables through the campaigns and audiences tools.
• Groups and contacts: create and manage groups, pull contact data.
• Webhooks, engine, utils: register delivery and session callbacks, check engine state, run utility calls.

The nine families in full are scheduled_messages, chats, groups, campaigns, audiences, contacts, webhooks, engine, and utils (Blueticks MCP docs). You never call them by name. You describe what you want and Claude picks the tool. If it picks wrong, you correct it in plain language, the same way you'd redirect a capable assistant.

Here's the failure mode to know up front: Claude can only send when your engine is live. If your WhatsApp session dropped or, on the free path, your computer is asleep, a send won't fire until the session is back. That's a Blueticks connection state, not an MCP bug, and it's the single most common "why didn't it send" surprise.

Is this the WhatsApp Business API?

No. Blueticks sends from your own personal WhatsApp number through its engine, which drives a real WhatsApp Web session. It is not Meta's WhatsApp Business API (the Cloud API), which sends server-side from a separate business number and bills per message.

This distinction matters more than any other line in this guide, so I'll be blunt about it. When Claude sends a message through Blueticks, it goes out as you, from the number your contacts already recognize, riding a live WhatsApp session. There's no Meta approval, no message templates to pre-clear, no per-conversation pricing. The WhatsApp Business API is a different product entirely: Meta moved it to per-message pricing effective July 1, 2025, with rates that vary by template category and country (Meta's WhatsApp pricing docs), and a number registered on the Cloud API can't be used with the normal WhatsApp app.

So pick by what you're doing. If you're a person or a small team who wants Claude to handle your everyday WhatsApp from your own number, this MCP setup is the right tool and the API is overkill at roughly a hundred times the setup cost. If you're building an app that fires OTP codes or ships order updates to thousands of strangers from a brand number, that's the Business API, and Blueticks isn't a substitute for it. Don't conflate them, and don't let anyone sell you one as the other.

Which MCP clients can I use?

Any MCP-compatible client works, because Blueticks ships a standard stdio MCP server. Blueticks documents ready-made configs for Claude Desktop, Claude Code, and Cursor, and the same @blueticks/mcp server plus BLUETICKS_API_KEY pattern applies to other MCP clients.

MCP's whole point is build-once, connect-everywhere. The protocol is supported across a wide range of AI clients and development tools (modelcontextprotocol.io), so the Blueticks WhatsApp mcp server isn't locked to one app. In practice most people connect WhatsApp to Claude specifically, using Claude Desktop for chat-style "message this person" work and Claude Code when they want WhatsApp actions inside a coding or automation workflow.

The config differs only in where each client stores it. Claude Desktop uses its MCP settings file, Claude Code uses ~/.claude.json, and Cursor has its own MCP config, but all three take the identical server command and key variable (Blueticks MCP docs). If you're weighing options across the ecosystem, the roundup of the best WhatsApp MCP servers compares approaches so you can see where the Blueticks server fits.

Troubleshooting: tools not loading or auth failing

If the WhatsApp tools don't appear or auth fails, the cause is almost always one of four things: Claude wasn't fully restarted, the key is wrong or malformed, the JSON config has a syntax error, or your WhatsApp engine isn't connected. Work them in that order.

Run this checklist when Claude says it has no WhatsApp access:

1. Restart Claude completely. MCP servers load at launch. Quit fully and reopen, not just close the window. This fixes most "tools missing" reports on the first try.
2. Re-check the key. Confirm it starts with bt_live_, has no stray spaces or line breaks, and is the full value you copied. Since the key shows only once, generate a fresh one if you're unsure.
3. Validate the JSON. A single trailing comma or unmatched brace stops the whole MCP config from parsing, so the server never starts. Paste it into a JSON validator if in doubt.
4. Test the key outside Claude. Call GET /v1/ping with the key. If it returns your account and engine, the key is good and the problem is client-side config. If ping fails, the key or account is the issue, not Claude (dev.blueticks.co).
5. Confirm the engine is live. Tools can load fine and sends still fail if your WhatsApp session is disconnected. Re-link your number in Blueticks and try a send again.

One operator who runs a small agency put it this way: "Every time I thought MCP was broken, it was me. I'd edited the config and not quit Claude, or I'd pasted the key with a line break. Ping the key first and half your problems disappear." That's the honest pattern. The protocol rarely breaks; the setup details do.

Blueticks MCP vs open-source WhatsApp MCP servers

Blueticks is a managed WhatsApp MCP server: your session, sends, scheduling, and campaigns run on maintained infrastructure with a stable bt_live_ key. Open-source WhatsApp MCP servers are self-hosted, so you run and maintain the session and server yourself, trading setup and upkeep for full control.

Both connect WhatsApp to Claude over the same protocol, so the difference isn't capability on paper, it's who keeps it running. Weigh it by what you're optimizing for:

If you're a developer who wants to own every layer and doesn't mind babysitting a session, a self-hosted server is a legitimate path. If you want Claude messaging people reliably without becoming your own uptime team, the managed route wins on the thing that actually matters day to day: it's still working next month. For the full field, the best WhatsApp MCP servers comparison lays the options side by side.

FAQ

How do I connect WhatsApp to Claude? Link your WhatsApp number to Blueticks, create a Blueticks API key that starts with bt_live_, add the @blueticks/mcp server to your Claude client with that key as the BLUETICKS_API_KEY variable, restart Claude, and verify the WhatsApp tools load by asking Claude to list your chats. Then Claude can send and read WhatsApp from your number.

How is this different from scheduling WhatsApp from Claude? This guide is the connect-and-setup half: getting the WhatsApp MCP server wired into Claude and authenticated. Scheduling from Claude is what you do afterward, once the tools are live, and it has its own timing, recurrence, and delivery nuances. Those live in the companion guide on scheduling WhatsApp messages from Claude. Set up here, schedule there.

Does Claude send from my own WhatsApp number? Yes. Blueticks drives a real session on your own number through its engine, so messages Claude sends appear as sent by you. It is not the WhatsApp Business API and does not use a separate business number or per-message billing.

Do I need the WhatsApp Business API for this? No. The whole point of this setup is to let Claude message people from your existing WhatsApp without Meta approval, templates, or per-message fees. The Business API is for programmatic, high-volume transactional sending from a brand number, which is a different job.

Which Claude apps support the Blueticks MCP server? Any MCP-compatible client works, and Blueticks documents ready-made configs for Claude Desktop, Claude Code, and Cursor. They all use the same @blueticks/mcp server and BLUETICKS_API_KEY variable, differing only in where each client stores its config.

Why aren't the WhatsApp tools showing up in Claude? Almost always because Claude wasn't fully restarted after editing the config, the API key is malformed, the JSON has a syntax error, or your WhatsApp engine is disconnected. Restart Claude, re-check the key, validate the JSON, and test the key against GET /v1/ping before assuming anything deeper is wrong.