Plenty of people answer clients on two numbers: a work WhatsApp and a personal one where old clients still write. Running multiple WhatsApp accounts in one MCP server keeps a single entry in your AI client and lets the agent pick the account per call, instead of juggling two servers with the same 37 tool names.
How it works in WACrew
Each WhatsApp number runs in its own collector (one container per number, each with its own panel). The MCP server, wacrew-mcp from version 0.1.3, can talk to several of them:
- the main account comes from
WAC_CLOUD_URL,WAC_CLOUD_USERandWAC_CLOUD_PASS, as usual; - the others go in
WAC_CONTAS, asname=https://login:password@address, separated by spaces; WAC_CONTA_NOMEnames the main account (defaultprincipal).
With more than one account configured, every tool gains an optional conta parameter (an enum of the names) and the server tells the agent at the start of the session which accounts exist and which is the default.
Claude Code example
claude mcp add wacrew \
-e WAC_CLOUD_URL=https://work.example.com \
-e WAC_CLOUD_USER=admin -e WAC_CLOUD_PASS=change-me \
-e WAC_CONTA_NOME=work \
-e WAC_CONTAS="personal=https://admin:other-pass@personal.example.com" \
-- npx -y wacrew-mcp
Then "who is waiting on my personal WhatsApp?" becomes caixa_de_entrada { conta: "personal" }, and a call with no conta goes to work. Special characters in a password must be URL-encoded inside WAC_CONTAS (@ becomes %40).
In Antigravity
The plugin form has only three fields, so the panel URL field accepts the extra accounts after a space: https://work.example.com personal=https://admin:other-pass@personal.example.com. Same result, one server with a conta parameter. See WhatsApp in Antigravity.
One server or two?
one server, WAC_CONTAS | two servers | |
|---|---|---|
| entries in the client | one | two, with the same tool names under different prefixes |
| choosing the account | conta parameter, default for the main one | the agent picks the server |
| where it fits | clients with a single MCP form (Antigravity plugin) | setups where each account has its own skills or permissions |
Both work. Chats and slugs belong to each account, so whichever you choose, the agent should read, answer and watch a chat in the account it lives in; the server's instructions say exactly that.
FAQ
Can one collector hold two numbers? No. Each number is one linked-device session, so run one collector per number; the MCP server is what joins them.
What happens if I pass a name that does not exist? The call is rejected with the list of valid accounts before anything runs.
Does the watch script follow both accounts? Run one watch per account: PLANTAO_CLOUD=pessoal selects the second collector's credentials.
Which version do I need? wacrew-mcp 0.1.3 or newer. npx -y wacrew-mcp always fetches the latest.

