How to Connect WhatsApp to Claude (MCP Setup Guide, Plus a Pre-Call Thread Summary)

You have a client call in twenty minutes and a WhatsApp thread that runs to two hundred messages. You need the open decisions, not a scroll through the whole history. Connecting Claude to WhatsApp gets you there, and the first thing it should do is read, not send.

Connect WhatsApp to Claude by adding the Blueticks MCP server to your MCP client and authenticating with a Blueticks API key. Claude can then read your chats, summarize them, and send or schedule 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_), or use the remote connector login.
3. Add the Blueticks MCP server to Claude.
4. Restart Claude and confirm the WhatsApp tools load.
5. Ask Claude for a read-only summary of one thread and its open decisions, then confirm nothing was sent.

There are two ways to wire this up, and most people on the web should pick the first. The remote connector connects Claude to Blueticks over a URL and a login, with nothing to install and no key to store. The MCP server path runs the @blueticks/mcp package locally and authenticates with a bt_live_ key, which suits Claude Code, Cursor, and anyone who prefers key-based auth. Both reach the same WhatsApp tools.

Can Claude connect to WhatsApp?

Yes. Claude connects to WhatsApp through the Blueticks MCP server. You link your WhatsApp number to Blueticks, add Blueticks to Claude as a connector (a hosted URL with a login, or the @blueticks/mcp server with an API key), and Claude can read, send, and schedule WhatsApp from your own number. Setup takes a few minutes and does not require the WhatsApp Business API.

The fastest way: connect with the remote connector (no install, no key)

If you use Claude on the web or in the desktop app, you can skip the config file and the API key. Blueticks runs a hosted MCP endpoint that Claude connects to over a URL, and you approve access with a login instead of a pasted key. The endpoint is live: https://api.blueticks.co/mcp answers as an MCP server with OAuth enabled.

1. In your Blueticks dashboard, open the Claude connector setup. It shows your connector URL. Menu names change, so follow what the dashboard shows.
2. Copy the MCP endpoint: https://api.blueticks.co/mcp.
3. In Claude, open the connectors settings (the menu name moves between builds), add a custom connector, name it Blueticks, paste the URL, and connect.
4. Claude sends you to Blueticks to log in and approve access. This is standard OAuth: you authorize on a Blueticks screen, and you can revoke it anytime. No key touches the Claude config.
5. Back in Claude, ask something read-only like "list my recent WhatsApp chats" to confirm the WhatsApp tools loaded.

Because the endpoint is hosted, nothing runs on your machine, and because it uses OAuth there is no bt_live_ key to copy, store, or rotate. Whether the connector is included on your plan depends on the current table at blueticks.co/pricing, so check that before you commit.

Prefer an API key, or connecting from Claude Code or Cursor? The MCP-server setup below is the right fit.

How to connect WhatsApp to Claude (MCP integration)

To connect WhatsApp to Claude, you link your 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. None of it involves Meta's developer console. The messages Claude sends come from your own WhatsApp account, not from a separate business identity.

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 WhatsApp the way you would link WhatsApp Web: scan a QR code so your session is live. The engine holds your WhatsApp connection. The MCP server you add later gives Claude tools that drive that engine.

If you need sends to fire while your computer is closed, the Pro plan includes always-on 24/7 sending. The Basic plan runs in the browser, so it does not send while WhatsApp Web is closed.

Step 2: Generate a Blueticks API key (bt_live_)

The key is how Claude proves it is allowed to act as you. Open the Blueticks API dashboard, click "Create key," and copy the value immediately. Blueticks shows it once (Blueticks API authentication). The key starts with 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.

Check the key before you wire it into Claude. GET /v1/ping validates the key and returns your account ID plus the WhatsApp engines currently connected (Blueticks API authentication). If ping returns 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 @blueticks/mcp, a local stdio MCP server that your client launches on demand with npx, so there is nothing to install into a project (Blueticks MCP docs). You register it in your client's MCP configuration and pass the key from Step 2 as an environment variable. The config block Blueticks documents for Claude Desktop and Claude Code is:

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

Cursor takes the same command and the same BLUETICKS_API_KEY variable through its own settings (Blueticks MCP docs). Config file locations and menus move as clients update, so if a screen does not match, follow the current steps in the Blueticks docs rather than an old screenshot.

Step 4: Authenticate and verify the tools load

Fully restart Claude after saving the config. MCP servers are read at startup, so a window you never closed will not 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 something read-only first, such as "list my recent WhatsApp chats" or "what WhatsApp tools do you have?" If Claude answers using the tools, you are connected. If it says it has no WhatsApp access, the server did not start or the key did not authenticate. The troubleshooting section covers both.

Step 5: Get a read-only first result

Your first win should not be a sent message. Ask Claude for a summary of one long thread and its open decisions. The recipe is in the next section. Once it returns, check your WhatsApp: the thread should show no new outbound message from this session.

Sending a test message comes later, once you trust the setup. Tell Claude in plain language to message someone, for example "Send a WhatsApp to +1 555 010 0199 saying the invoice is attached and I'll follow up Friday." The message leaves from your number and appears in your sent messages, because it is your account sending.

How do I summarize a long WhatsApp thread with Claude before a client call?

Ask Claude to find the chat by name, read its recent messages, and list the key points and open decisions: who owes what, and what is still unresolved. It is one request from you, and it sends nothing. Run it the morning of the call, so the summary reflects the latest messages.

Use this prompt, replacing the bracketed name:

Find the chat with [client name] and read its last 200 messages. Summarize the key points in five bullets. Then list the open decisions: who owes what, and what is still unresolved. Read only. Do not send, schedule, or reply to anything.

The output should come back in two parts. First, five bullets of key points. Second, a short table you can scan during the call. The rows below are an illustrative shape, not real output:

The read-only part is the prompt doing its job. Reading the chats uses the chats tools, which read and search conversations (Blueticks MCP docs). Sending is a separate tool family, and the prompt rules it out explicitly. Check afterward anyway.

What breaks: the summary is only as current as the engine's copy of the thread. If your session is disconnected, re-link your number before you trust the output. If the thread is longer than the number of messages you asked for, the summary covers the window you named, not the whole history.

Skip Meta's developer console for this. You do not need a Business API account, a provider contract, or per-message fees to let Claude read and message people from your own WhatsApp. Create a Blueticks account and connect Claude.

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

MCP, the Model Context Protocol, is an open standard for connecting AI applications like Claude to outside tools and data. Claude runs an MCP client, Blueticks runs an MCP server that exposes WhatsApp tools, and Claude calls those tools to read or send messages (modelcontextprotocol.io).

The moving parts are worth knowing, because they decide where things break:

• The MCP client is Claude. It asks for tools when it needs to act.
• The MCP server is Blueticks (@blueticks/mcp). It advertises the WhatsApp tools and runs them.
• The tools are the actions: read a chat, send a message, start a campaign. Each one wraps a Blueticks /v1 API call authenticated with your key (Blueticks MCP docs).

So when you ask Claude to summarize a client thread, Claude picks the chats tool, the Blueticks server makes the /v1 call, and your engine returns the messages. If you want the background on this pattern, the primer on WhatsApp and MCP walks through the architecture.

What can Claude do with WhatsApp once connected?

Once connected, Claude can read and search your conversations, help you triage them, draft replies, and send, schedule, and manage messages, campaigns, groups, and contacts from your number. The Blueticks server exposes nine tool families (Blueticks MCP docs).

Lead with reading. Claude can pull recent chats, search history, and load older messages through the chats tools. 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. For the full morning routine built on this loop, see the chief-of-staff guide to AI WhatsApp assistants, which covers the triage rubric and the approval gate. This article keeps to setup and the single-thread summary.

Then there is the write path:

• Send now: "Text Maria the meeting moved to 3pm." A straight send from your number.
• Schedule: "Send this reminder to every client on Monday at 9am." The queue fires later. The companion guide on scheduling WhatsApp messages from Claude via MCP covers timing and recurrence.
• Campaigns and audiences: build a templated campaign and append contacts through the campaigns and audiences tools.
• Groups, contacts, webhooks, engine, utils: manage groups, pull contact data, register callbacks, check engine state.

You never call these by name. You describe the outcome and Claude picks the tool. If it picks wrong, correct it in plain language.

Here is the failure mode to know up front: sends and reads both depend on your engine being live. If your WhatsApp session dropped, a send will not fire until the session is back. On Basic, the browser has to stay open. That is a Blueticks connection state, not an MCP bug, and it is the 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 live WhatsApp Web session. It is not Meta's WhatsApp Business API (the Cloud API), which sends from a separate business number and bills per message.

When Claude sends through Blueticks, the message goes out as you, from the number your contacts already recognize. The Business API is a different product. Meta has charged per message since July 1, 2025, and the rate depends on the template's category and the recipient's country calling code (Meta's WhatsApp pricing docs).

Pick by what you are doing. If you want Claude to handle your everyday WhatsApp from your own number, this MCP setup fits and the Business API is overkill. If you are building an app that sends OTP codes or order updates to thousands of strangers from a brand number, that is the Business API, and Blueticks is not a substitute. Do not conflate the two. Neither path comes with a guarantee against restrictions, so keep your volume and message content sensible.

Which MCP clients can I use?

Any MCP-compatible client can run a standard stdio server, and Blueticks documents ready-made configs for Claude Desktop, Claude Code, and Cursor. They all use the same @blueticks/mcp server and the BLUETICKS_API_KEY variable (Blueticks MCP docs).

In practice, most people use Claude Desktop for "message this person" chat work, and Claude Code when they want WhatsApp actions inside a coding or automation workflow. The config is the same everywhere. Only the file where each client keeps it differs.

Troubleshooting: tools not loading or auth failing

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

When Claude says it has no WhatsApp access:

1. Restart Claude completely. MCP servers load at launch. Quit fully and reopen. 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. The key shows only once, so generate a fresh one if you are 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.
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 (Blueticks API authentication).
5. Confirm the engine is live. Tools can load fine while sends and reads fail because the WhatsApp session is disconnected. Re-link your number and try again.

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 behind a bt_live_ key. Open-source WhatsApp MCP servers are self-hosted, so you run and maintain the session and the server yourself.

Both connect WhatsApp to Claude over the same protocol, so the difference is less about capability and more about who keeps it running:

If you want to own every layer and do not mind babysitting a session, a self-hosted server is a legitimate path. If you want Claude messaging people without becoming your own uptime team, the managed route wins on the thing that matters day to day: it still works next month. The best WhatsApp MCP servers comparison lays out the field.

FAQ

Can Claude connect to WhatsApp? Yes. Claude connects to your WhatsApp account through the Blueticks MCP server, either the hosted remote connector (a URL plus a login) or the local @blueticks/mcp server with a bt_live_ API key. Once connected, Claude can read, send, and schedule WhatsApp from your own number, without the WhatsApp Business API.

How do I connect WhatsApp to Claude? The fastest way is the remote connector. Link your WhatsApp number to Blueticks, add a custom connector in Claude pointing at https://api.blueticks.co/mcp, and approve access with a Blueticks login. If you prefer key-based auth, or you use Claude Code or Cursor, add the @blueticks/mcp server with a bt_live_ key as BLUETICKS_API_KEY. Either way, verify by asking Claude to list your chats.

Do I need an API key, or can I connect with just a login? You can connect with just a login. The remote connector uses OAuth: you add the Blueticks MCP URL to Claude, then authorize on a Blueticks screen, and no bt_live_ key is stored in your Claude config. The API-key path is still the better fit for Claude Code, Cursor, and scripted setups. You can revoke access anytime from your Blueticks settings.

Can Claude summarize a WhatsApp chat without sending anything? Yes. Ask for a summary of one named thread and its open decisions, and say "read only, do not send." That is one request from you, and it reads the thread without sending a message. Confirm afterward that the thread shows no new outbound message from this session.

How is this different from scheduling WhatsApp from Claude? This guide covers connecting the MCP server and checking that it works, plus a read-only summary. Scheduling from Claude is what you do once the tools are live, and it has its own timing, recurrence, and delivery details. 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 live 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.

Why aren't the WhatsApp tools showing up in Claude? Almost always because Claude was not fully restarted after you edited 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.