Meta Muse already works with WhatsApp, but only in one direction: you can message Muse from WhatsApp, the same way you would message a contact. What Muse still cannot do is look into your WhatsApp. It cannot read your existing chats, search them, or send a reply on your behalf.
That second direction is what an MCP server adds. MCP (the Model Context Protocol) is the open standard that lets an AI app call outside tools, and Muse can use any remote MCP server through a custom connector. This guide connects Muse to WhatsApp using Automata, a free, open-source WhatsApp MCP server that lets you choose exactly which chats Muse can see and which actions it can take.
Don't want to run anything yourself? Automata has a hosted option at mcp.getautomata.app. Sign up, pair WhatsApp, and use https://mcp.getautomata.app/mcp as the URL in step 2.
Muse on WhatsApp vs Muse with your WhatsApp
These two things sound alike and are easy to mix up:
| Built-in WhatsApp integration | Muse + Automata | |
|---|---|---|
| Direction | You message Muse from WhatsApp | Muse reaches into your WhatsApp |
| Read your chats | No | Yes, only the chats you allow |
| Search old messages | No | Yes |
| Send a reply for you | No | Yes, only if you enable it, one token at a time |
| Who sees what | Your conversation with Muse | Only the chats on the connector token |
The built-in integration is a convenient way to talk to an assistant. It is not a way to give that assistant your inbox. If you want Muse to answer questions like "what did the supplier confirm last week?" or "draft a reply to Client A", it needs a tool that can read and write your chats. Automata is that tool.
What you need
- A WhatsApp account. Use a spare number while testing, because unofficial clients carry some risk of rate limits or bans.
- A Muse account that can create custom connectors. Meta is still rolling out Muse features, so if you do not see custom connector support yet, check back after your account updates.
- Automata, either hosted at mcp.getautomata.app (no server to run), or your own instance with a public HTTPS URL. Muse runs in Meta's cloud, so it cannot reach
localhostor a private network. For self-hosting, the quickest option is the one-click Railway template; you can also self-host with Docker. - A WhatsApp account already paired in Automata and a connector token. If you have not done that yet, follow steps 1 to 3 of How to connect WhatsApp to Claude; they are identical for every client.
- About ten minutes.
How the connection works
Three pieces are involved, and only the middle one is new:
- Muse is the MCP client. It sends requests to a URL from Meta's cloud and attaches your key.
- Automata is the MCP server. It checks the key on every request, enforces which chats are allowed, and exposes the WhatsApp tools.
- WhatsApp is paired to Automata as a linked device, so Muse never touches your phone or your account credentials.
This is separate from the built-in WhatsApp integration. That one connects your WhatsApp number to Muse, so you can chat with it. Automata connects Muse to your WhatsApp chats, so it can work with them. You can use both at once.
Because the permission check happens in Automata and not in the prompt, Muse cannot talk its way into a chat you did not allow. Read more about how Automata enforces permissions.
Step 1: Get your endpoint and key
Open your Automata dashboard and create a connector token for your WhatsApp connection. Each connector token has two settings. Chats decides which conversations it can see. Actions decides which tools it can call: the read tools, and send-text-message to send. The two are independent, so a token that can send can send to any chat on its list.
A new WhatsApp token starts with all chats and all actions, so narrow both: choose Only selected chats, then Only selected actions with just the read tools: get-connection-status, list-chats, read-messages, and search-messages. To let Muse reply in one chat only, create a separate token for that chat with sending enabled. You need two values:
Endpoint: https://your-automata.example.com/mcp
Authorization: Bearer <connector-token>If you use hosted Automata, the endpoint is always https://mcp.getautomata.app/mcp, and you create the token from your hosted dashboard.
Automata uses a bearer API key rather than OAuth sign-in, so you will give Muse the key, not log in to anything. The MCP clients docs cover the other endpoint formats.
Anyone with the token can use the chats it allows. Do not paste it into a public chat or a screenshot, and do not type it into your conversation with Muse. If it leaks, revoke that one token in Automata and create a new one.
Step 2: Ask Muse to create a custom connector
Muse does not have an "add MCP server" button. You add one by asking Muse, in a normal chat, to create a custom connector. Give it the name, the transport, the URL, and how the server authenticates, all in one message:
Create a Custom Connector for a new remote MCP server, then connect to it:
Name: Automata WhatsApp
Transport: remote streamable HTTP
URL: https://your-automata.example.com/mcp
Auth: API key sent as Authorization: BearerMuse recognizes that this is not one of its catalog connectors and sets it up as a custom one. It will tell you the connector can act on your WhatsApp account through Automata, and may ask you to confirm before it continues.
Step 3: Enter the key in the secure prompt
When Muse asks for the key, enter your connector token in its secure credentials prompt, not as a normal chat message. Anything you type into the conversation can end up in your chat history, while the secure prompt stores the key with the connector.
If Muse offers only an OAuth sign-in and no API key option, say so and ask it to use an API key sent as a bearer token. Automata does not use OAuth for connector tokens.
Step 4: Confirm the tools are connected
Once the key is saved, Muse tests the connector and lists the tools it found. It may also save the connector as a reusable skill, so you do not need to repeat this setup in future chats. You can review or disconnect it later from Settings → Connectors.
The tool count depends on your token. Automata only registers the tools in the token's Actions setting, so a read-only token shows fewer tools than one that can also send messages. If the count is lower than you expected, check the token's Actions in your dashboard. Chat choices never change the count.
Step 5: Test it
Start with a safe, read-only request before asking for anything that sends a message. Try:
Use the Automata WhatsApp connector to check the WhatsApp connection status.
Then move to prompts that match the chats you allowed:
- List my chats, then summarize what Client A asked for since Monday.
- Find the delivery date the supplier confirmed in the Suppliers group.
- Check the Project Launch chat and list every question I have not answered yet.
- Draft a reply to Client A confirming Thursday. Do not send it.
That last prompt is the one the built-in integration cannot handle at all. With a token that has sending enabled for a single chat, you can go one step further and ask Muse to send the reply it drafted. Muse asks for your approval before it sends.
Keep it safe
- Start read-only. Limit the token to one or two chats and the read tools first. If Muse needs to reply in one chat, create a separate token for that chat with sending enabled.
- Keep approvals on. Muse asks before important actions by default. Read the message it is about to send, and keep that confirmation on so every outgoing message is one you approved.
- Use a separate token for Muse. You can then revoke it without breaking Claude or any other client.
- Watch for prompt injection. A message in an allowed chat can contain instructions aimed at the AI. Keep sending off unless you need it, and review anything Muse proposes before approving it.
- Keep a spare number for experiments and avoid bulk or unsolicited messaging.
Troubleshooting
| Symptom | Likely cause and fix |
|---|---|
| Muse cannot reach the server | The URL is not public or not HTTPS. Muse runs in Meta's cloud, so use your deployed Automata URL, not localhost, and make sure it ends in /mcp. |
Muse reports a 401 error | The key is missing, invalid, expired, or revoked. Create a new connector token and save it again through the secure prompt. |
| Muse only offers OAuth | Ask it to create the connector with an API key sent as a bearer token. Automata does not support OAuth sign-in for connector tokens. |
| No custom connector option | Custom connectors may not have reached your account yet. Check Settings → Connectors and try again later. |
| Fewer tools than expected | The token's Actions setting allows only some tools. Edit the token and add the tools you need, then reconnect the connector in Muse. (Chat choices don't change the tool count.) |
| A chat is missing from the results | It is not allowed on this token, or it has no stored messages yet. Check the chat permissions and your history sync. |
| Sending fails, or there is no send tool | No send tool: the token doesn't include send-text-message. "not scoped to": the recipient isn't on the token's chat list. "is not a WhatsApp account": use international format, digits only. "connection is down" or "could not verify the recipient": the account is disconnected; reconnect it from the dashboard. |
More fixes are in the troubleshooting guide.
Frequently asked questions
Can Meta Muse read my WhatsApp chats?
Not on its own. The built-in WhatsApp integration lets you message Muse from WhatsApp, but it does not give Muse access to your existing chats. To let Muse read and search your messages, connect it to a WhatsApp MCP server such as Automata through a custom connector.
Can Muse send WhatsApp messages for me?
Only through a tool that can send. With Automata, Muse can send a message if the connector token includes the send-text-message action and the recipient is on the token's chat list. Muse asks for your approval before sending, and a read-only token cannot send anything.
Is it free to connect Muse to WhatsApp?
Yes. Automata is MIT licensed and free to self-host, including the one-click Railway template. A hosted version is available at mcp.getautomata.app.
Do I still need the built-in WhatsApp integration?
No, the two are independent. The built-in integration lets you talk to Muse from inside WhatsApp. Automata lets Muse work with your chats. Use whichever you need, or both.
Does it work with WhatsApp Business?
It works with the WhatsApp Business app, because Automata pairs any WhatsApp account as a linked device, the same way WhatsApp Web does. It does not use the WhatsApp Business API, so no Meta business verification is needed.
Will my WhatsApp number get banned?
Unofficial clients always carry some risk, especially with repeated pairing or unsolicited messages. Use a spare number while testing, keep sending off unless you need it, and never use it for bulk messaging.
Next steps
- Turn this connection into a daily brief with the free AI chief of staff tutorial.
- Use the same WhatsApp connection from Claude, ChatGPT, Grok Bot, or Cursor, and see every endpoint format in the MCP clients guide.
- Read the WhatsApp MCP overview for what each tool does and how scoped access compares to other servers.
Comments
Questions, corrections, or your own setup? Join in below. Pick any name to post.