WACrew

Guide

WhatsApp MCP on WAHA or Evolution API

Already run WAHA, Evolution API, Z-API or the Cloud API? How MCP servers that wrap those APIs compare with servers that connect to WhatsApp directly, and when each makes sense.

Updated 2 min read
On this page
  1. Wrappers that exist today
  2. When a wrapper makes sense
  3. When a direct server is better
  4. Evolution API, WAHA and WACrew
  5. FAQ

There are two ways to give an agent WhatsApp through MCP. A direct server holds the WhatsApp session itself (lharries/whatsapp-mcp, whatzmcp, WACrew). A wrapper server talks to a WhatsApp HTTP API you already run, such as WAHA or Evolution API, and translates it into MCP tools. If your company already has one of those APIs in production, a wrapper can be the shortest path.

Wrappers that exist today

ServerWrapsNotes
seejux/waha-whatsapp-mcpWAHATypeScript, stdio; chats, messages, send, mark as read, MCP resources; no license detected by GitHub
@codespar/mcp-evolution-apiEvolution APIPart of codespar's Latin America server collection, MIT
@codespar/mcp-z-apiZ-API (hosted)Same collection
@codespar/mcp-whatsapp-cloud, FredShred7/whatsapp-mcp-serverOfficial Cloud APIBusiness Platform number and templates
msaelices/whatsapp-mcp-serverGreenAPI (hosted)Python, groups management; last commit April 2025

When a wrapper makes sense

  • The API is already there. Evolution API or WAHA already serves your chatbot or CRM, with its own session and webhooks. Adding a second linked device for an agent would be redundant.
  • Several systems share one number. The API is the single owner of the session; the MCP server is just one more client.
  • You need the official API. Only the Cloud API wrappers give you Meta's platform, templates and support.

When a direct server is better

  • You do not run an API yet. Deploying WAHA or Evolution API just to wrap it adds a moving part.
  • You want features above messaging. Transcription, review before sending, a wait-time inbox and CRM live in apps like WACrew, not in thin wrappers.
  • Personal use. whatzmcp or a lharries fork is simpler.

Evolution API, WAHA and WACrew

Evolution API and WAHA are APIs for developers: they give you endpoints and webhooks, and you build the product. WACrew is a product: inbox, panel, AI replies and MCP server, connecting through Baileys itself. If you already have Evolution API, you can keep it for integrations and still use WACrew on a different number for the conversations you answer personally. Comparisons: WAHA vs Evolution API and, in Portuguese, Evolution API ou WACrew.

FAQ

Is there an official WAHA MCP server? Not that we found in the WAHA repositories as of November 2026; seejux/waha-whatsapp-mcp is a community project.

Do wrappers support voice note transcription? Generally not; they expose what the API returns. Transcription would be a separate tool.

Is a wrapper safer for my number? The risk depends on the API underneath. WAHA and Evolution API on WhatsApp Web carry the same unofficial-client risk as direct servers; the Cloud API does not.