How to Send a WhatsApp Message from Manus (Blueticks MCP Setup)
Manus has no built-in WhatsApp connector. You can add the Blueticks remote MCP server by URL and let the agent read chats and send from your own number. Steps, limits and risks.
Daniel Roth6 min read

On this page
To send a WhatsApp message from a Manus agent, add the Blueticks remote MCP server to Manus as a custom connector, then ask Manus to read a chat or send a message. The server URL is https://api.blueticks.co/mcp. Messages go out from your own WhatsApp number, linked the way you link WhatsApp Web.
A note on sources. Manus documents custom MCP servers in its own docs, and we followed those pages for the Manus side. We have not run this exact setup inside a Manus account ourselves, and Manus changes its menus, so treat the click path below as a guide and check it against what your account shows.
Does Manus have a WhatsApp connector?
We could not find one. Manus lists many prebuilt connectors, and its own docs say that for a service that is not in the catalog you can add it yourself as a custom MCP server if the provider offers one. Blueticks offers one, so that is the route.
This is not the Meta Cloud API and not an official Meta product. Blueticks runs a WhatsApp Web linked-device session on your own number and exposes it as MCP tools. See the hosted MCP page for the full description.
How do you connect Manus to WhatsApp?
- Link your number in Blueticks. The server sends through the WhatsApp engine on your account, so connect your number first.
- Open Connectors in Manus and add an MCP server by URL. Manus's docs say to open Connectors, select Create, and add an MCP server by URL. Older Manus guides describe a path under Settings, Integrations, Custom MCP Servers instead. Use whichever your account has.
- Enter the details. Name it "Blueticks" and use
https://api.blueticks.co/mcpas the server URL. Manus needs a server it can reach over HTTPS, and this is one. - Authenticate. If Manus offers a sign-in for the server, use it. Blueticks uses OAuth 2.0 with the authorization-code flow and S256 PKCE, so you approve access on a Blueticks page and no key is stored in Manus. If Manus only lets you set a header, create a
bt_live_key under Blueticks API and send it asAuthorization: Bearer bt_live_your_key_here. - Enable it for the task. Manus enables connectors per task. Turn on the Blueticks connector, or name it in your prompt.
- Test with a read. Ask: "Using Blueticks, list my five most recent WhatsApp chats."
Do not use the @blueticks/mcp npm package for this. It runs as a local process on your own machine, and a cloud agent cannot reach your machine.
What can the agent do once it is connected?
The server exposes twelve tools covering 62 actions, listed on the MCP page. The ones you will use most:
| Tool | What it does | Read-only? |
|---|---|---|
chats_read | Chat lookup, message history, media, poll results, participants | Yes |
chats_write | Send text, media or polls right away; mark read, react, archive | No |
scheduled_messages_read | List queued messages, check delivery and read status | Yes |
scheduled_messages_write | Send or schedule messages, edit ones not yet sent, cancel them | No |
contacts | List contacts, get a profile picture | Yes |
campaigns | Paced bulk send to an audience | No |
The rest cover groups, audiences, webhooks, tasks, the engine and utilities. Exact names can change, so ask Manus to list the tools it sees.
Example prompts:
- "Read the last 50 messages in my chat with the supplier and list what they still owe me."
- "Schedule a WhatsApp to the team group for tomorrow at 9:00 asking for status updates."
- "Check whether the message I sent to Dana yesterday was delivered and read."
Read-only or full access?
It depends on how you sign in.
- OAuth. The Blueticks server defines two scopes,
mcp:readandmcp:write. A read-only grant lets the agent read chats and blocks every write action. Whether Manus lets you approve only read access is up to Manus, so check the consent screen. If you see no choice, assume you are granting both. - API key. Do not assume a
bt_live_key is read-only. Treat it as able to read chats and send messages, keep it out of prompts and shared files, and revoke it under Blueticks API if it leaks.
Start with a read-only task. Move to sending once you have seen how Manus behaves.
Will it keep working when your computer is off?
Only if your WhatsApp session runs in the cloud. There are two options:
| Where your WhatsApp session runs | When Manus can send |
|---|---|
The Blueticks browser extension with web.whatsapp.com open in Chrome | Only while your computer is on and the browser is open |
| A Blueticks Gateway, the cloud-hosted engine (Pro plan) | Always, including with your computer off |
Manus runs in the cloud, so it can start a task while your laptop is closed. If your session is extension-hosted, the send will fail until the browser is back. For the details, see how a WhatsApp AI agent answers with your computer off.
What are the risks?
Several tools act immediately, so set rules in your prompt.
- Sends go out as you.
chats_writesends right away. To keep a message editable first, ask Manus to schedule it withscheduled_messages_write, then check it before it goes. - Campaigns message many people. Tell Manus to confirm the audience, text and timing with you before it creates one.
- Ban risk is real. Blueticks uses the WhatsApp Web linked-device model. We cannot promise WhatsApp will never restrict a number. Message people who expect to hear from you, and remember that consent and opt-out are your responsibility.
- Chat content is untrusted. A message from someone else can contain text that tries to steer an agent. Ask Manus to show you drafts and not to follow instructions found inside chats.
To cut Manus off, from lightest to firmest: disconnect the connector in Manus, revoke the key under Blueticks API if you used one, or remove the Blueticks device under Linked Devices in WhatsApp on your phone.
FAQ
Is there an official Manus and Blueticks integration?
No. Manus connects to Blueticks as an ordinary remote MCP server added by URL.
Is there a free plan?
The connector has no extra charge and works on any plan. The free plan allows 5 requests per 6 hours, shared with the API, and paid plans have no request limit, per the MCP page and the pricing page. Always-on sending needs the Pro plan with a Gateway.
Does it work the same as in Claude or Grok?
The server is the same. Only the way each app adds it differs. See WhatsApp MCP for Claude and Grok, and the comparison of WhatsApp MCP servers if you are still choosing.
Should I use the REST API instead?
If the job is a script or a scheduled worker with no agent in the loop, yes. See the WhatsApp API for AI agents.


