Compared · whatsapp
25 WhatsApp MCP servers. Which one to use.
Every WhatsApp server we index, with whether its source is still reachable and whether we hold a screening verdict. None currently carry a source-liveness flag.
Scope: 25 servers, mostly mirrored from the MCP registry as of 2026-09-08. Most servers whose authors never published to the registry are absent, so treat this as close to the registry's view rather than a complete census.
| Server | Publisher | Source | Screened | Quality | Install |
|---|---|---|---|---|---|
| WhatsApp Web MCP Server | io.github.mario-andreschak | no flag | REVIEW | 100 | npm mcp-whatsapp-web |
| DarkFunnels | ai.darkfunnels | no flag | REVIEW | 95 | remote endpoint |
| SMS and WhatsApp Messaging | dev.hatchloop | no flag | REVIEW | 90 | remote endpoint |
| WhatsApp Connect | io.github.Idle-Sync | no flag | REVIEW | 90 | not published |
| io.github.drsound/markdown-to-whatsapp | io.github.drsound | no flag | REVIEW | 90 | npm markdown-to-whatsapp |
| WhatsApp Messaging API | io.github.jevil25 | no flag | REVIEW | 90 | npm whatsapp-messaging-api-mcp |
| WhaTools — WhatsApp tools | tools.wha | no flag | REVIEW | 90 | remote endpoint |
| WASync — WhatsApp Platform API | app.wasync | no flag | REVIEW | 85 | remote endpoint |
| WhatsApp MCP by TimelinesAI | io.github.InitechSoftware | no flag | REVIEW | 85 | remote endpoint |
| io.github.mcp-dir | no flag | REVIEW | 85 | remote endpoint | |
| Green API WhatsApp | com.green-api | no flag | REVIEW | 83 | remote endpoint |
| Guarded WhatsApp | io.github.peter-tnc-453 | no flag | REVIEW | 82 | pypi guarded-whatsapp-mcp |
| ManyContacts - WhatsApp Business CRM | io.github.ManyContacts | no flag | REVIEW | 81 | npm @manycontacts/mcp |
| ManyContacts - WhatsApp Business MCP | io.github.ManyContacts | no flag | REVIEW | 81 | npm @manycontacts/mcp |
| com.jojapi/whatsapp-wyjbao | com.jojapi | no flag | REVIEW | 80 | remote endpoint |
| uni-msg WhatsApp | com.uni-msg | no flag | REVIEW | 80 | npm uni-msg-mcp-server |
| WhatsApp MCP | io.github.adelaidasofia | no flag | REVIEW | 79 | pypi adelaidasofia-whatsapp-mcp |
| io.github.codespar/mcp-whatsapp-cloud | io.github.codespar | no flag | REVIEW | 76 | npm @codespar/mcp-whatsapp-cloud |
| WhatsApp MCP Server | io.github.nakulben | no flag | REVIEW | 76 | pypi jina-whatsapp-mcp |
| ai.izap/whatsapp | ai.izap | no flag | REVIEW | 75 | remote endpoint |
| io.2chat/whatsapp | io.2chat | no flag | REVIEW | 75 | remote endpoint |
| io.github.meharajM/whatsapp-mcp | io.github.meharajM | no flag | REVIEW | 75 | npm @mhrj/whatsapp-mcp |
| io.github.gaviwhatsapp/whatsapp | io.github.gaviwhatsapp | no flag | REVIEW | 72 | npm @gaviwhatsapp/mcp |
| io.github.kalki-kgp/whatsapp-macos | io.github.kalki-kgp | no flag | REVIEW | 71 | pypi whatsapp-mcp-macos |
| ai.smithery/samihalawa-whatsapp-go-mcp | ai.smithery | no flag | REVIEW | 52 | remote endpoint |
“Repo unreachable” means the source returned a not-found from two vantage points, which can also happen when a repository is made private or moved - see source liveness. “Screened” is the advisory verdict on the listing text, never a safety clearance; the methodology spells out what each dimension does and does not test.