WhatsApp Web MCP Server
io.github.mario-andreschak/mcp-whatsapp-web
About WhatsApp Web MCP Server
WhatsApp Web MCP Server is an MCP server published by the GitHub account mario-andreschak. WhatsApp MCP via web.js or browserless Baileys: messages, media, chats, groups and contacts
It runs on your own machine: your AI client starts it from the npm package mcp-whatsapp-web at version 1.2.0.
It asks for no keys or passwords.
Version 1.2.0 was published on 5 September 2026, and the source code is public, so you can read it before installing.
Written from the registry entry. 9 automated checks on the registry entry and the package code: 7 pass, 0 warn, 0 fail, 2 info. How we check.
What it asks for
| Variable | Required | Secret | Description |
|---|---|---|---|
WHATSAPP_BACKEND | No | No | WhatsApp backend: webjs uses a persistent browser profile; baileys connects without a browser and requires separate pairing |
BAILEYS_SESSION_DIR | No | No | Baileys credentials and synchronized history directory (default: <working directory>/baileys-sessions). Use a private absolute path, owned by one server process. |
LOG_LEVEL | No | No | Log level for the log file (logs/mcp-whatsapp.log) |
LOG_STDERR_LEVEL | No | No | Log level for stderr (visible in most MCP client logs) |
WHATSAPP_HEADLESS | No | No | webjs only: set to false to show the browser window instead of running headless |
WHATSAPP_NO_SANDBOX | No | No | webjs only: explicitly disable the browser sandbox for containers that require it. The sandbox is enabled by default. |
BROWSER_EXECUTABLE_PATH | No | No | webjs only: browser executable. Chrome and Edge are auto-detected; set this to use a specific browser. Chrome/Edge is required for sending videos and GIFs. |
WHATSAPP_SESSION_DIR | No | No | webjs only: persistent browser profile directory (default: <working directory>/whatsapp-sessions) |
WHATSAPP_PAIRING_PHONE_NUMBER | No | No | 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 |
FFMPEG_PATH | No | No | Path to an ffmpeg binary (only needed to override the ffmpeg installed automatically via the ffmpeg-static npm package) |
WA_WEB_VERSION | No | No | webjs only: pin the WhatsApp Web version if a WhatsApp-side update breaks the client. |
HEALTH_CHECK_INTERVAL_MS | No | No | webjs only: connection health check interval in milliseconds (<=0 disables) |
TOOL_READY_TIMEOUT_MS | No | No | How long tool calls wait for the WhatsApp client to become ready before erroring |
MCP_HTTP_PORT | No | No | When set, additionally exposes the MCP endpoint at http://127.0.0.1:<port>/mcp (Streamable HTTP) from the same process |
MCP_HTTP_HOST | No | No | Bind address for the HTTP endpoint (do not expose publicly; the endpoint controls your personal WhatsApp account) |
MCP_OAUTH | No | No | 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 |
Checks
| Check | Result | Detail |
|---|---|---|
| Source repository linked | Pass | https://github.com/mario-andreschak/mcp-whatsapp-web |
| Version pinned | Pass | Every package has an explicit version |
| Secrets requested | Info | Asks for no secrets |
| Known package registry | Pass | All packages come from npm, PyPI, OCI, NuGet or MCPB |
| Namespace ownership | Info | Name verified via GitHub account mario-andreschak |
| Registry text aimed at the AI | Pass | Description and settings contain no hidden characters or instructions to the AI |
| Install scripts | Pass | mcp-whatsapp-web@1.2.0 runs nothing at install |
| Code red flags | Pass | Read 44 files in mcp-whatsapp-web@1.2.0: no obfuscation, encoded execution, credential reads or data-collection endpoints found |
| Text aimed at the AI | Pass | No hidden characters or instructions to the AI in 44 files, including comments and the README |
Popularity & health: 57 / 100
Worked out from public numbers and our own checks, not from user reviews or ratings. It says how used and how looked-after a server is, not whether it is safe.
11 forks, 0 merged pull requests. Sources: GitHub, npm, PyPI (pypistats.org) and Hacker News (Algolia), fetched 2026-10-31.
What people say
No Hacker News threads link to its source code.
Look further: search Reddit, search Hacker News, read its GitHub issues. These are not reviews we checked.
Facts
| Registry name | io.github.mario-andreschak/mcp-whatsapp-web |
|---|---|
| Publisher | GitHub account mario-andreschak |
| How the name is verified | Name verified via GitHub account mario-andreschak. The registry ties the name prefix to that account or domain; it does not check the code. |
| Type | Local: runs on your machine from a package |
| Packages | npm mcp-whatsapp-web 1.2.0 (stdio) |
| Version | 1.2.0 |
| Published | |
| Last updated | |
| Source repository | https://github.com/mario-andreschak/mcp-whatsapp-web |
| Website | https://github.com/mario-andreschak/mcp-whatsapp-web |
| Category | Browser automation (assigned by keyword rule, not by hand) |
Related servers in Browser automation
- Browserless7/8Official Browserless MCP server: browser automation, scraping,…
- Crawlora MCP4/4Hosted MCP: 3926 structured web-data tools across 488 platform groups.
- Zamery Browser7/7Use your existing Firefox and logged-in tabs, limited to tabs or…
- Kaption WhatsApp7/7Read and manage your WhatsApp conversations through the KaptionAI…
- NodeLane Act5/6Use Reddit, Zhihu, X and WhatsApp through your signed-in browser…
- LinkedIn7/7Read LinkedIn profiles, companies, jobs and messages via your own…