WhatsApp Web MCP Server
MCP server for WhatsApp via whatsapp-web.js: send/receive messages, media, chats, groups, contacts
Verdict not yet evaluated for this tool. The semantic screen takes adversarial cases first; coverage rolls out as the corpus expands (15/150 labels to graduation). The deterministic conformance probe is built but has not yet run on the public corpus, so a recorded verdict here is REVIEW or UNVERIFIED, never a clearing ALLOW. Until a verdict is recorded, an agent should treat this tool as not-yet-cleared and fall back to its own checks. Method: the eval, four-state verdict, honest limits.
Own this server? Screen its description →
LOG_LEVELLog level for the log file (logs/mcp-whatsapp.log)
LOG_STDERR_LEVELLog level for stderr (visible in most MCP client logs)
WHATSAPP_HEADLESSSet to false to show the browser window instead of running headless (debugging aid)
BROWSER_EXECUTABLE_PATHBrowser executable. Chrome and Edge are auto-detected in their standard install locations; set this only to use a specific browser. A real Chrome/Edge is required for sending videos and GIFs.
WHATSAPP_SESSION_DIRWhere the WhatsApp session (browser profile) is stored (default: <working directory>/whatsapp-sessions)
WHATSAPP_PAIRING_PHONE_NUMBERPhone number pairing: when set (international, symbol-free format, e.g. 4915112345678), an 8-character pairing code is logged to stderr on startup instead of relying on the QR code
FFMPEG_PATHPath to an ffmpeg binary (only needed to override the ffmpeg installed automatically via the ffmpeg-static npm package)
WA_WEB_VERSIONPin the WhatsApp Web version. Only set this if a WhatsApp-side update breaks the client.
HEALTH_CHECK_INTERVAL_MSConnection health check interval in milliseconds (<=0 disables)
TOOL_READY_TIMEOUT_MSHow long tool calls wait for the WhatsApp client to become ready before erroring
MCP_HTTP_PORTWhen set, additionally exposes the MCP endpoint at http://127.0.0.1:<port>/mcp (Streamable HTTP) from the same process
MCP_HTTP_HOSTBind address for the HTTP endpoint (do not expose publicly; the endpoint controls your personal WhatsApp account)
MCP_OAUTHEnable OAuth for the HTTP endpoint: /mcp requires a bearer token and clients authenticate via a browser page showing the WhatsApp QR code / pairing form
Quality scoring and progressive gates for AI-generated API tests. Stripe/Twilio profiles. Free tier.
Surface customer & prospect context from Slack, email, transcripts and tickets in any MCP client.
Give your AI agents a real WhatsApp number to send and receive messages.