WACrew

Comparison

lharries/whatsapp-mcp alternatives in 2026

Looking for an alternative to lharries/whatsapp-mcp? Maintained forks, TypeScript rewrites, Cloudflare-hosted servers and full apps, with license, stack and last commit for each.

Updated 3 min read
On this page
  1. Keep the same architecture, get updates
  2. Drop Go and Python
  3. Run it in the cloud instead of your laptop
  4. Use an API you already pay for
  5. A full app instead of a bridge
  6. How to choose
  7. FAQ

lharries/whatsapp-mcp is the project most people find first: about 6.9k stars, MIT license, a Go bridge on the whatsmeow library plus a Python MCP server, and 12 tools to search chats and send messages. It still works for many people. The reasons to look elsewhere are practical: its default branch has had no commits since July 13, 2025, it needs Go, Python, uv and (on Windows) a C compiler, and it is a bridge with no review layer before sending.

Below are the alternatives worth knowing, grouped by what you want to keep. Data comes from each repository's README and GitHub metadata, checked on November 14, 2026.

Keep the same architecture, get updates

ProjectWhat changesLicenseLast commit
verygoodplugins/whatsapp-mcpA maintained fork: quoted replies, mentions, read receipts, call history, webhooksMIT (fork notice in LICENSE)November 2026
FelixIsaac/whatsapp-mcp-extended26 tools by default (15 in lean mode), polls, group management, webhooks, Docker, a send allowlistMITNovember 2026

Both still run Go plus Python with SQLite, so your mental model and most config carry over. Details in verygoodplugins vs WACrew and whatsapp-mcp-extended vs WACrew.

Drop Go and Python

ProjectStackNotes
whatzmcp/whatzmcpTypeScript, Node 20+, runs with npxBuilt-in warm-up limits on sending, Docker image, MIT
jlucaso1/whatsapp-mcp-tsTypeScript on Baileys, Node 23.10+Six tools; ISC in package.json, no license file detected by GitHub; last commit January 2026
WACrewTypeScript on Baileys, Node 20+, npx -y wacrew-mcp36 tools, web panel, review before sending, Apache 2.0

More on this route in a WhatsApp MCP server without Go.

Run it in the cloud instead of your laptop

Use an API you already pay for

If WhatsApp already reaches you through an HTTP API, wrap that instead: seejux/waha-whatsapp-mcp for WAHA, the codespar packages for Evolution API, Z-API or the official Cloud API. Covered in WhatsApp MCP on WAHA or Evolution API.

A full app instead of a bridge

Every project above exposes WhatsApp as tools and leaves the rest to the agent. WACrew goes further for people who answer clients on WhatsApp: an inbox sorted by who has waited longest, transcribed voice notes, replies that pass a code review for robotic tells before they leave, delivery at a human pace that stops if the client writes again, and a per-chat Confirm mode that is on by default. The MCP server is one interface; the other is a web panel. Comparison in lharries/whatsapp-mcp vs WACrew.

How to choose

  • It works and you just want fixes: a maintained fork (verygoodplugins or whatsapp-mcp-extended).
  • You do not want Go or Python on your machine: whatzmcp or WACrew.
  • Your agent only needs to read: finereli/whatsapp-mcp.
  • You want it always on without a VPS: felipeadeildo/whatsapp-mcp on Cloudflare.
  • You serve clients in groups and need replies that sound like you: WACrew.

FAQ

Is lharries/whatsapp-mcp abandoned? It has no commits on its default branch since July 2025 and the repository is not archived. Forks carry fixes forward.

Can I migrate my history from lharries/whatsapp-mcp? The forks keep the same SQLite layout, so moving within that family is the easiest path. Projects on Baileys or Cloudflare start a new session and sync from the moment you link.

Are any of these official? No. All the WhatsApp Web based servers link as an extra device, outside WhatsApp's Business Platform. For official access use a Cloud API wrapper.