You have a client call at three, and the thread with them is four hundred messages deep. You need three things: what they asked, what you promised, and what is still open. Scrolling for them costs twenty minutes you do not have.
This guide shows how to summarize a WhatsApp chat with Claude before a meeting, using the Blueticks WhatsApp MCP server. It covers the setup, the exact prompt, the failure modes, and the limits. The workflow reads only. It does not send.
Can Claude summarize a WhatsApp chat before a meeting?
Yes. With the Blueticks WhatsApp MCP server connected, Claude can find one chat, read its recent messages, and summarize them in the conversation. You get the open questions, the dates, and who owes the next reply. The summary sends nothing. In the setup described here, the server runs on your own machine and uses your Blueticks API key.
The Model Context Protocol is, in its own words, "an open-source standard for connecting AI applications to external systems" (MCP introduction). The Blueticks server is one such connection. It exposes your connected WhatsApp as tools that Claude can call.
What must be connected before Claude can read your chats?
You need a Blueticks API key and the @blueticks/mcp server entry in Claude. Start by linking your WhatsApp number in the Blueticks app.
- Link your WhatsApp number to Blueticks.
- Copy your Blueticks API key. Treat it as a password.
- Add the server entry from the Blueticks MCP docs to your Claude config. The entry runs
npx -y @blueticks/mcpwithBLUETICKS_API_KEYset. - Restart Claude and ask whether WhatsApp is connected.
What breaks: the engine depends on where it runs. The pricing page says Basic and Standard run in the browser through WhatsApp Web and the extension. Pro runs in the cloud 24/7. Yearly prices are $7, $20, and $45 per user per month for Basic, Standard, and Pro. If you need a summary at any hour, Pro is the plan that fits.
For scheduling messages in the app, see how to schedule WhatsApp messages.
What do you ask Claude to get the summary?
Ask for one named chat, recent messages only, and a fixed set of outputs. This prompt returns a summary of one client thread from recent messages, with open questions and dates, and it sends nothing.
Summarize my WhatsApp thread with [exact chat name] from recent messages before my meeting. List the open questions, every date or deadline mentioned, and who owes the next reply. Do not send anything.
- Ask Claude whether your WhatsApp is connected. If it is not, stop and fix the connection in the Blueticks app first.
- Paste the prompt with the exact chat name in place of the placeholder.
- Claude searches your chats for that name, then reads its recent messages with the
list_messagesaction. - Check every date in the summary against the thread before you rely on it.
What breaks: two chats with similar names. Claude may read the wrong thread and summarize it with confidence. Use the full name, or the phone number, and check that the first line of the summary names the right client.
A composite example, not a real customer: "The summary put the deadline in the first line. I had not noticed it was Thursday, not Friday, until I read it."
For a daily digest instead of a one-off summary, see the WhatsApp chief-of-staff workflow.
How does Claude read the thread without sending anything?
Claude reads through the chats tool, using its list, search, and list_messages actions. Those are read actions. Sending goes through scheduled_messages.
The public docs list chats as a tool that lists and searches chats and lists messages. They describe scheduled_messages as the tool that sends text, media, or polls, optionally on a schedule, and that lists, gets, updates, and cancels them. The docs describe no read-only mode for the server.
So the protection sits in how you run the conversation:
- Keep the summary in its own conversation. Do not ask for a send in the same thread.
- Read the tool calls Claude reports before you approve anything that sends.
- Use the summary recipe above. It needs
chatsand nothing else.
What if the thread goes further back than the loaded history?
Recent messages alone can miss older ones. The chats tool has a load_more_history option, and the Blueticks MCP docs say it pulls older messages from the phone. Run it before the summary when the window looks empty or too short.
- If the summary finds nothing older, or the thread looks thin, ask Claude to load more history for that chat.
- Wait for the load to finish, then ask for the summary again.
- Compare the earliest message date in the summary with what you remember of the thread.
What breaks: a quiet client can return zero recent messages. Empty is not the same as no conversation. Load more history before you conclude nothing happened. The docs do not say how long a history load takes or whether the phone must be online, so test it on one thread before you rely on it on the morning of a meeting.
Which WhatsApp MCP tools does Claude get, and what does each do?
The Blueticks server exposes nine tools: scheduled_messages, chats, groups, audiences, campaigns, contacts, engine, webhooks, and utils. The meeting summary uses chats. The docs name the engine tool without describing it. The rest handle sending, groups, contact lists, campaigns, and webhooks.
| Tool | What the public docs say it does | Used in the summary |
|---|---|---|
chats | List and search chats, list messages, load older history | Yes |
engine | Named in the docs, no detail given | Not described in the docs |
scheduled_messages | Send text, media, or a poll, optionally scheduled. List, get, update, cancel | No |
groups | Create, update, get groups | No |
audiences | Append contacts with per-contact variables | No |
campaigns | Create, pause, resume, cancel campaigns | No |
webhooks | Register HTTPS callbacks for message, session, and campaign events | No |
contacts | Named in the docs, no detail given | No |
utils | Named in the docs, no detail given | No |
The docs name contacts, engine, and utils without describing them. This table follows the public docs at the time of writing. Check the docs page for changes before you build on any tool.
MCP vs the WhatsApp Business API: when to use which?
Use the Blueticks MCP when you want Claude to read and act on your own WhatsApp number.
The WhatsApp Business Messaging Policy, last updated 23 September 2026, allows contact only with people who have given you their number and opted in to later messages. The policy is written for businesses. Treat the MCP the same way.
Start on a paid plan from $7 per user per month billed yearly at blueticks.co/signup. Link your number, then add the MCP entry to Claude once the engine is green. Compare the plans on the pricing page.
What are the limits and good practices?
The MCP reads and acts on your real WhatsApp account, so WhatsApp's rules apply to every action it takes. Read as much as you like. Send only to people who gave you their number and opted in.
- Read first, send deliberately. Reading is what the summary does. Keep sending as a separate step, and check the recipient count before anything dispatches.
- Own number, real consent. The MCP sends from your account. Message only people who gave you their number and opted in.
What the pricing page does not say. It gives 50, 100, and 200 AI credits per month for Basic, Standard, and Pro. It states no call allowance for any plan. It says MCP access is included in every paid tier, and it does not describe MCP access on the free plan. Do not build a daily workflow around a call count that is not published.
What can't Claude do natively, and how does Blueticks add it?
In this setup, Claude reaches WhatsApp through the MCP server. Blueticks supplies the connection in two parts: an API with your key, and the MCP server that exposes it to Claude as tools. The pricing page says Basic and Pro include API access.
If a summary comes back empty, load more history and try again before you change anything in Claude.
For the longer walkthrough of the connection, see connect Claude to WhatsApp.
Frequently asked questions
Can Claude read my WhatsApp chats? Yes. With the MCP connected, Claude can list and search your chats and read the messages in a thread. The summary recipe uses exactly that.
Does Claude send anything when it summarizes? Not in the recipe. The send tool exists, so an instruction not to send is only a request. Keep sends out of the summary conversation and check any send before you approve it.
Is MCP access included on the free plan? The pricing page says MCP access is included in every paid tier. It does not state free-plan access. Check the pricing page before you plan around it.
Does this work with my own WhatsApp number? Yes. The engine links your own number to Blueticks, and Claude reads and sends through that connection.
Connect Claude to your WhatsApp today
Link your number, create an API key, add the entry to Claude, and ask for one summary before your next meeting. Start with a paid plan at blueticks.co/signup. Then ask Claude who is waiting on you, and read the answer before you walk in.
