
mcp-whatsapp-web
WhatsApp Web MCP Server
MCP server for WhatsApp via whatsapp-web.js: send/receive messages, media, chats, groups, contacts
Package Details
mcp-whatsapp-web
Environment Variables
infoLog level for the log file (logs/mcp-whatsapp.log)
warnLog level for stderr (visible in most MCP client logs)
Set to false to show the browser window instead of running headless (debugging aid)
Browser 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.
Where the WhatsApp session (browser profile) is stored (default: <working directory>/whatsapp-sessions)
Phone 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
Path to an ffmpeg binary (only needed to override the ffmpeg installed automatically via the ffmpeg-static npm package)
Pin the WhatsApp Web version. Only set this if a WhatsApp-side update breaks the client.
60000Connection health check interval in milliseconds (<=0 disables)
45000How long tool calls wait for the WhatsApp client to become ready before erroring
When set, additionally exposes the MCP endpoint at http://127.0.0.1:<port>/mcp (Streamable HTTP) from the same process
127.0.0.1Bind address for the HTTP endpoint (do not expose publicly; the endpoint controls your personal WhatsApp account)
Enable OAuth for the HTTP endpoint: /mcp requires a bearer token and clients authenticate via a browser page showing the WhatsApp QR code / pairing form