verygoodplugins/whatsapp-mcp is where many lharries/whatsapp-mcp users end up. Its LICENSE states it is a fork of the original (MIT, with the original copyright kept), it is maintained by Very Good Plugins, and it had commits on November 14, 2026. WACrew is an independent project on Baileys.
Side by side
| verygoodplugins/whatsapp-mcp | WACrew | |
|---|---|---|
| Base | Fork of lharries/whatsapp-mcp | Independent |
| Requirements | Go 1.26+, Python 3.11+, uv, FFmpeg optional | Node 20+ and FFmpeg, or Docker |
| Storage | Local SQLite | Files per chat in data/ |
| Highlights | Quoted replies, @-mentions, read receipts, call history, webhooks with signed POSTs, sender_display as "Name (phone)", LID lookups | Wait-time inbox, transcription, image and video understanding, style and review, CRM, calendar |
| Sending | Direct, with quote and mention options | Ticketed, human-paced, confirm mode by default |
| License | MIT | Apache 2.0 |
Why choose the fork
- You already use lharries/whatsapp-mcp and want fixes without changing anything structural. Its README notes that updates do not require re-pairing.
- You need precise group replies: quoted messages with the right attribution and @-mentions are well documented.
- You want webhooks to push inbound messages, reactions and calls to another service.
- Call history in SQLite is unusual and useful for some workflows.
Why choose WACrew
- You answer clients and need to know who has waited longest across dozens of groups.
- Voice notes, screenshots and screen recordings are part of how your clients talk.
- You want replies that pass a review for robotic tells and arrive at a human pace, with an approval step by default.
- You want a web panel for you and your team, not only an agent.
FAQ
Is verygoodplugins/whatsapp-mcp compatible with lharries configs? It keeps the Go bridge plus Python server layout, so the client config has the same shape. Check its README for new environment variables.
Why does GitHub show its license as Other? The LICENSE file starts with a fork notice before the MIT text, so GitHub's detector does not label it as plain MIT.
Can WACrew send webhooks? It has an external control API and a public REST API (docs/api-v1.md) rather than inbound message webhooks.



