You may modify this by using the option below: - `--webhook-secret="secret"` - **Webhook Payload Documentation** For detailed webhook payload
Most team communication work still happens through a UI a human drives. Go Whatsapp Web Multidevice MCP server moves it into the conversation instead. You may modify this by using the option below: - --webhook-secret="secret" - Webhook Payload Documentation For detailed webhook payload schemas, security implementation, and integration examples, see [Webhook Payload.
The server publishes 14 tools. What each one is for:
Multi — device support**: You can now connect and manage multiple WhatsApp accounts simultaneously in a singleX-Device — Id header, orexample — Hello @628974812XXXX, @628974812XXXXavailable — mark as online (suppresses phone notifications)unavailable — register pushname without going online (default, preserves phone notifications)none — skip presence entirely (pushname won't be registered, contacts may see "-" as name)Per — Device Webhook** - Each device can have its own webhook URLLinux — - sudo apt updateVariable — DescriptionAPP_PORT — Application portAPP_HOST — Host address to bind the serverAPP_DEBUG — Enable debug loggingBecause this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Configuration is passed through the environment: CGO_CFLAGS_ALLOW, APP_BASE_PATH, WHATSAPP_WEBHOOK_SECRET, CHATWOOT_URL, CHATWOOT_API_TOKEN, CHATWOOT_ACCOUNT_ID, CHATWOOT_INBOX_ID, CHATWOOT_DEVICE_ID. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the team communication options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Go Whatsapp Web Multidevice's toolset — Multi, X-Device, example and 11 more — is a fair guide to whether it matches your workflow. It is maintained by aldinokemal; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Go Whatsapp Web Multidevice's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Multi | device support**: You can now connect and manage multiple WhatsApp accounts simultaneously in a single |
| X-Device | Id header, or |
| example | Hello @628974812XXXX, @628974812XXXX |
| available | mark as online (suppresses phone notifications) |
| unavailable | register pushname without going online (default, preserves phone notifications) |
| none | skip presence entirely (pushname won't be registered, contacts may see "-" as name) |
| Per | Device Webhook** - Each device can have its own webhook URL |
| Linux | - sudo apt update |
| Variable | Description |
| APP_PORT | Application port |
| APP_HOST | Host address to bind the server |
| APP_DEBUG | Enable debug logging |
| APP_OS | OS name (device name in WhatsApp) |
| APP_BASIC_AUTH | Basic authentication credentials |
| Variable | Description | Required |
|---|---|---|
| CGO_CFLAGS_ALLOW | Configuration value read at startup. | Optional |
| APP_BASE_PATH | Filesystem location the server is allowed to use. | Optional |
| WHATSAPP_WEBHOOK_SECRET | Credential the server authenticates with. | Yes |
| CHATWOOT_URL | Endpoint or connection string the server talks to. | Yes |
| CHATWOOT_API_TOKEN | Credential the server authenticates with. | Yes |
| CHATWOOT_ACCOUNT_ID | Configuration value read at startup. | Optional |
| CHATWOOT_INBOX_ID | Configuration value read at startup. | Optional |
| CHATWOOT_DEVICE_ID | Configuration value read at startup. | Optional |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.