go-whatsapp-web-multidevice: A WhatsApp REST API with support for UI, Multi Account, Webhooks, MCP, and Chatwoot.
What problem it solves
Applications need a consistent way to send and receive WhatsApp messages, manage connected accounts, and forward activity to other systems. Integrators also need configurable event delivery, device-scoped operations, and interfaces suitable for automation clients.
Key features
REST API for WhatsApp messaging — Expose WhatsApp messaging through an HTTP API with a machine-readable OpenAPI contract. The API covers message sending and additional operations documented in the project references.
Source: README
Multi-account device management — Connect and manage multiple WhatsApp accounts from one server instance. Device-scoped requests can identify the target device through a header or query parameter, with a new API for managing devices.
Source: README
Configurable webhook events — Forward received messages and other WhatsApp events to a webhook, then filter events by type or JID. Devices can use separate webhook URLs, event filters, and signing secrets, with global webhook fallback behavior.
Source: README
MCP server and OAuth support — Serve the REST API and an MCP endpoint from the same process, with MCP available at `/mcp`. Optional OAuth 2.1 authentication supports remote MCP clients that cannot provide a Basic Auth header.
Source: README
Messaging automation and media handling — Automate common messaging behaviors such as replies, read receipts, media downloads, call rejection, presence, and scheduled sends. Media workflows include image and video compression, sticker conversion, and support for common image formats.
Source: README
Who it may suit
This project may suit developers building REST-based WhatsApp integrations, automation workflows, or MCP-connected tools. It may also suit operators that need multi-account management and webhook-based event processing.
Topics to discuss
Which REST API and MCP workflows should receive the most documentation and examples?
How should multi-account deployments handle device routing, credentials, and webhook isolation?
Which integrations and operational use cases should the community prioritize next?
Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.
Read the original README https://github.com/aldinokemal/go-whatsapp-web-multidevice#readme
ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.
Comments
…