emailmd
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
WhatsApp MCP via web.js or browserless Baileys: messages, media, chats, groups and contacts
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 18/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 30/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install WhatsApp Web MCP Server. Follow https://mcp.popnx.com/i/mario-andreschak-mcp-whatsapp-web.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
1 setting(s) to fill in (BROWSER_EXECUTABLE_PATH) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server WhatsApp Web MCP Server for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "whatsapp-web": { "command": "npx", "args": [ "-y", "mcp-whatsapp-web" ], "env": { "BROWSER_EXECUTABLE_PATH": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For BROWSER_EXECUTABLE_PATH, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the WhatsApp Web MCP Server tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
BROWSER_EXECUTABLE_PATH 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.Descriptions are as written by the maker.
SettingsDeveloperEdit Config
{
"mcpServers": {
"whatsapp-web": {
"command": "npx",
"args": [
"-y",
"mcp-whatsapp-web"
],
"env": {
"BROWSER_EXECUTABLE_PATH": "your-value"
}
}
}
}Use WhatsApp Web MCP Server and tell me what you can do for me, then show me one thing✓ If Claude says it is using WhatsApp Web MCP Server or shows a WhatsApp Web MCP Server tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
WHATSAPP_BACKEND WhatsApp backend: webjs uses a persistent browser profile; baileys connects without a browser and requires separate pairing · default webjsBAILEYS_SESSION_DIR Baileys credentials and synchronized history directory (default: /baileys-sessions). Use a private absolute path, owned by one server process.LOG_LEVEL Log level for the log file (logs/mcp-whatsapp.log) · default infoLOG_STDERR_LEVEL Log level for stderr (visible in most MCP client logs) · default warnWHATSAPP_HEADLESS webjs only: set to false to show the browser window instead of running headlessWHATSAPP_NO_SANDBOX webjs only: explicitly disable the browser sandbox for containers that require it. The sandbox is enabled by default. · default falseWHATSAPP_SESSION_DIR webjs only: persistent browser profile directory (default: /whatsapp-sessions)WHATSAPP_PAIRING_PHONE_NUMBER 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 codeFFMPEG_PATH Path to an ffmpeg binary (only needed to override the ffmpeg installed automatically via the ffmpeg-static npm package)WA_WEB_VERSION webjs only: pin the WhatsApp Web version if a WhatsApp-side update breaks the client.HEALTH_CHECK_INTERVAL_MS webjs only: connection health check interval in milliseconds (<=0 disables) · default 60000TOOL_READY_TIMEOUT_MS How long tool calls wait for the WhatsApp client to become ready before erroring · default 45000MCP_HTTP_PORT When set, additionally exposes the MCP endpoint at http://127.0.0.1: /mcp (Streamable HTTP) from the same processMCP_HTTP_HOST Bind address for the HTTP endpoint (do not expose publicly; the endpoint controls your personal WhatsApp account) · default 127.0.0.1MCP_OAUTH Enable OAuth for the HTTP endpoint: /mcp requires a bearer token and clients authenticate via a browser page showing the WhatsApp QR code / pairing formDescriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect WhatsApp Web MCP Server yet
WhatsApp Web MCP Server runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect WhatsApp Web MCP Server
B · Others in Chat & email that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
1 setting(s) to fill in (BROWSER_EXECUTABLE_PATH) · Install Node.js on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server WhatsApp Web MCP Server for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user whatsapp-web --env BROWSER_EXECUTABLE_PATH=your-value -- npx -y mcp-whatsapp-web 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For BROWSER_EXECUTABLE_PATH, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the WhatsApp Web MCP Server tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
BROWSER_EXECUTABLE_PATH 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.Descriptions are as written by the maker.
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user whatsapp-web --env BROWSER_EXECUTABLE_PATH=your-value -- npx -y mcp-whatsapp-webYou should see WhatsApp Web MCP Server listed as connected
Use WhatsApp Web MCP Server and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using WhatsApp Web MCP Server or shows a WhatsApp Web MCP Server tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
WHATSAPP_BACKEND WhatsApp backend: webjs uses a persistent browser profile; baileys connects without a browser and requires separate pairing · default webjsBAILEYS_SESSION_DIR Baileys credentials and synchronized history directory (default: /baileys-sessions). Use a private absolute path, owned by one server process.LOG_LEVEL Log level for the log file (logs/mcp-whatsapp.log) · default infoLOG_STDERR_LEVEL Log level for stderr (visible in most MCP client logs) · default warnWHATSAPP_HEADLESS webjs only: set to false to show the browser window instead of running headlessWHATSAPP_NO_SANDBOX webjs only: explicitly disable the browser sandbox for containers that require it. The sandbox is enabled by default. · default falseWHATSAPP_SESSION_DIR webjs only: persistent browser profile directory (default: /whatsapp-sessions)WHATSAPP_PAIRING_PHONE_NUMBER 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 codeFFMPEG_PATH Path to an ffmpeg binary (only needed to override the ffmpeg installed automatically via the ffmpeg-static npm package)WA_WEB_VERSION webjs only: pin the WhatsApp Web version if a WhatsApp-side update breaks the client.HEALTH_CHECK_INTERVAL_MS webjs only: connection health check interval in milliseconds (<=0 disables) · default 60000TOOL_READY_TIMEOUT_MS How long tool calls wait for the WhatsApp client to become ready before erroring · default 45000MCP_HTTP_PORT When set, additionally exposes the MCP endpoint at http://127.0.0.1: /mcp (Streamable HTTP) from the same processMCP_HTTP_HOST Bind address for the HTTP endpoint (do not expose publicly; the endpoint controls your personal WhatsApp account) · default 127.0.0.1MCP_OAUTH Enable OAuth for the HTTP endpoint: /mcp requires a bearer token and clients authenticate via a browser page showing the WhatsApp QR code / pairing formDescriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
1 setting(s) to fill in (BROWSER_EXECUTABLE_PATH) · Install Node.js on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server WhatsApp Web MCP Server for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "whatsapp-web": { "command": "npx", "args": [ "-y", "mcp-whatsapp-web" ], "env": { "BROWSER_EXECUTABLE_PATH": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For BROWSER_EXECUTABLE_PATH, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the WhatsApp Web MCP Server tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
BROWSER_EXECUTABLE_PATH 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.Descriptions are as written by the maker.
In the WhatsApp Web MCP Server settings, BROWSER_EXECUTABLE_PATH is empty; add your key and save
Use WhatsApp Web MCP Server and tell me what you can do for me, then show me one thing✓ If Cursor says it is using WhatsApp Web MCP Server or shows a WhatsApp Web MCP Server tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
WHATSAPP_BACKEND WhatsApp backend: webjs uses a persistent browser profile; baileys connects without a browser and requires separate pairing · default webjsBAILEYS_SESSION_DIR Baileys credentials and synchronized history directory (default: /baileys-sessions). Use a private absolute path, owned by one server process.LOG_LEVEL Log level for the log file (logs/mcp-whatsapp.log) · default infoLOG_STDERR_LEVEL Log level for stderr (visible in most MCP client logs) · default warnWHATSAPP_HEADLESS webjs only: set to false to show the browser window instead of running headlessWHATSAPP_NO_SANDBOX webjs only: explicitly disable the browser sandbox for containers that require it. The sandbox is enabled by default. · default falseWHATSAPP_SESSION_DIR webjs only: persistent browser profile directory (default: /whatsapp-sessions)WHATSAPP_PAIRING_PHONE_NUMBER 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 codeFFMPEG_PATH Path to an ffmpeg binary (only needed to override the ffmpeg installed automatically via the ffmpeg-static npm package)WA_WEB_VERSION webjs only: pin the WhatsApp Web version if a WhatsApp-side update breaks the client.HEALTH_CHECK_INTERVAL_MS webjs only: connection health check interval in milliseconds (<=0 disables) · default 60000TOOL_READY_TIMEOUT_MS How long tool calls wait for the WhatsApp client to become ready before erroring · default 45000MCP_HTTP_PORT When set, additionally exposes the MCP endpoint at http://127.0.0.1: /mcp (Streamable HTTP) from the same processMCP_HTTP_HOST Bind address for the HTTP endpoint (do not expose publicly; the endpoint controls your personal WhatsApp account) · default 127.0.0.1MCP_OAUTH Enable OAuth for the HTTP endpoint: /mcp requires a bearer token and clients authenticate via a browser page showing the WhatsApp QR code / pairing formDescriptions are as written by the maker.
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
1 setting(s) to fill in (BROWSER_EXECUTABLE_PATH) · Install Node.js on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server WhatsApp Web MCP Server for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "whatsapp-web": { "type": "stdio", "command": "npx", "args": [ "-y", "mcp-whatsapp-web" ], "env": { "BROWSER_EXECUTABLE_PATH": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For BROWSER_EXECUTABLE_PATH, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the WhatsApp Web MCP Server tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
BROWSER_EXECUTABLE_PATH 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.Descriptions are as written by the maker.
In the WhatsApp Web MCP Server settings, BROWSER_EXECUTABLE_PATH is empty; add your key and save
Use WhatsApp Web MCP Server and tell me what you can do for me, then show me one thing✓ If VS Code says it is using WhatsApp Web MCP Server or shows a WhatsApp Web MCP Server tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
WHATSAPP_BACKEND WhatsApp backend: webjs uses a persistent browser profile; baileys connects without a browser and requires separate pairing · default webjsBAILEYS_SESSION_DIR Baileys credentials and synchronized history directory (default: /baileys-sessions). Use a private absolute path, owned by one server process.LOG_LEVEL Log level for the log file (logs/mcp-whatsapp.log) · default infoLOG_STDERR_LEVEL Log level for stderr (visible in most MCP client logs) · default warnWHATSAPP_HEADLESS webjs only: set to false to show the browser window instead of running headlessWHATSAPP_NO_SANDBOX webjs only: explicitly disable the browser sandbox for containers that require it. The sandbox is enabled by default. · default falseWHATSAPP_SESSION_DIR webjs only: persistent browser profile directory (default: /whatsapp-sessions)WHATSAPP_PAIRING_PHONE_NUMBER 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 codeFFMPEG_PATH Path to an ffmpeg binary (only needed to override the ffmpeg installed automatically via the ffmpeg-static npm package)WA_WEB_VERSION webjs only: pin the WhatsApp Web version if a WhatsApp-side update breaks the client.HEALTH_CHECK_INTERVAL_MS webjs only: connection health check interval in milliseconds (<=0 disables) · default 60000TOOL_READY_TIMEOUT_MS How long tool calls wait for the WhatsApp client to become ready before erroring · default 45000MCP_HTTP_PORT When set, additionally exposes the MCP endpoint at http://127.0.0.1: /mcp (Streamable HTTP) from the same processMCP_HTTP_HOST Bind address for the HTTP endpoint (do not expose publicly; the endpoint controls your personal WhatsApp account) · default 127.0.0.1MCP_OAUTH Enable OAuth for the HTTP endpoint: /mcp requires a bearer token and clients authenticate via a browser page showing the WhatsApp QR code / pairing formDescriptions are as written by the maker.
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
JSON settings are under “For developers” below
Claude Code
claude mcp add --scope user whatsapp-web --env BROWSER_EXECUTABLE_PATH=your-value -- npx -y mcp-whatsapp-webClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"whatsapp-web": {
"command": "npx",
"args": [
"-y",
"mcp-whatsapp-web"
],
"env": {
"BROWSER_EXECUTABLE_PATH": "your-value"
}
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"whatsapp-web": {
"command": "npx",
"args": [
"-y",
"mcp-whatsapp-web"
],
"env": {
"BROWSER_EXECUTABLE_PATH": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"whatsapp-web": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"mcp-whatsapp-web"
],
"env": {
"BROWSER_EXECUTABLE_PATH": "your-value"
}
}
}
}WHATSAPP_BACKEND envBAILEYS_SESSION_DIR envLOG_LEVEL envLOG_STDERR_LEVEL envWHATSAPP_HEADLESS envWHATSAPP_NO_SANDBOX envBROWSER_EXECUTABLE_PATH required envWHATSAPP_SESSION_DIR envWHATSAPP_PAIRING_PHONE_NUMBER envFFMPEG_PATH envWA_WEB_VERSION envHEALTH_CHECK_INTERVAL_MS envTOOL_READY_TIMEOUT_MS envMCP_HTTP_PORT envMCP_HTTP_HOST envMCP_OAUTH envDescriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
npm: mcp-whatsapp-webBased on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The registry name was verified with the GitHub account mario-andreschak, which owns the repo
Code last changed 8 days ago
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
No entries on OSV.dev for mcp-whatsapp-web@1.2.0
Checks only this package version, not every dependency · checked Nov 15, 2026
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/mario-andreschak-mcp-whatsapp-web)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 8 days ago, and the latest version (1.2.0) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: emailmd, Kite Discord Bot Builder, e2a — email for AI agents, Infobip MCP, kernelCAD
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
Build and fix Discord bots from a chat. Kite hosts them 24/7, with no code to deploy.
Authenticated email gateway for AI agents — per-agent inboxes, HITL approval, SPF/DKIM verified.
Infobip MCP server for omnichannel communication and messaging. SMS, RCS, WhatsApp, Viber and more.
CAD in ChatGPT and Claude: editable parts, STEP/STL/drawings, in-chat 3D, automatic checks.
| This one WhatsApp Web MCP Server | emailmd | Kite Discord Bot Builder | e2a — email for AI agents | Infobip MCP | kernelCAD | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Cloud or install on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | Yes | No |
| Basic checks | 3/3 | 5/5 | 4/4 | 4/4 | 4/4 | 4/4 |
| License | MIT | MIT | AGPL-3.0 | Apache-2.0 | MIT | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Automation of Whatsapp Messages without Meta (Business-)API is against WhatsApp' Terms of Service! You take full responsibility for everything you do with this MCP-Server. It is possible that your account will be flagged/restricted.
A Model Context Protocol (MCP) server for WhatsApp Web, implemented in TypeScript. This project is a TypeScript port of the original whatsapp-mcp repository.
With this MCP server, you can:
MCP_HTTP_PORT to additionally expose http://127.0.0.1: /mcp, or run HTTP-only with --http)request_pairing_code tool, or automatically printed to stderr at startup via WHATSAPP_PAIRING_PHONE_NUMBER), and an optional OAuth flow for HTTP clients (MCP_OAUTH=true) where the browser authorization page shows the WhatsApp QR code — unlinking WhatsApp revokes tokens so clients automatically re-authenticateThis MCP server consists of:
webjs backend: Google Chrome or Microsoft Edge (auto-detected; needed for video/GIF codec support; other operations can use Puppeteer's bundled Chromium)baileys: install optional dependencies, including the native better-sqlite3 module. No Chrome, Edge, or Chromium is needed at runtime.FFmpeg is bundled automatically via the ffmpeg-static npm package — no manual installation needed. You can point the FFMPEG_PATH environment variable at your own binary to override it.
npx mcp-whatsapp-web
git clone https://github.com/mario-andreschak/mcp-whatsapp-web.git
cd mcp-whatsapp-web
npm install
npm run build
Copy the example environment file and modify as needed:
cp .env.example .env
You can select the backend with WHATSAPP_BACKEND, adjust logging levels, pin the WhatsApp Web version, or override the auto-detected browser (BROWSER_EXECUTABLE_PATH) and ffmpeg binary (FFMPEG_PATH). WHATSAPP_HEADLESS=false shows the web.js browser window, and WHATSAPP_SESSION_DIR relocates its persistent profile. Without these settings the sign-in is kept in a fixed place for your user account, so it no longer matters which folder a program starts the server from (see Keeping the link).
WHATSAPP_BACKEND=webjs is the default and preserves existing sessions and MCP tool names. It uses a dedicated persistent LocalAuth profile, not your personal Chrome profile. It now keeps the browser's native user agent and graphics defaults, omits Puppeteer's automation banner flag, and leaves the browser sandbox enabled. Containers that require disabling the sandbox can explicitly set WHATSAPP_NO_SANDBOX=true. These settings do not guarantee that automation is undetectable.
To use the optional Baileys backend, set these variables in your MCP client configuration or .env, then restart the server:
WHATSAPP_BACKEND=baileys
#BAILEYS_SESSION_DIR=C:/path/to/your/baileys-sessions
BAILEYS_SESSION_DIR is optional; without it the sign-in lives in the standard place described in Keeping the link. Pair this backend separately with get_qr_code or request_pairing_code. The existing WHATSAPP_PAIRING_PHONE_NUMBER option also works. Baileys cannot reuse the web.js browser profile. You can switch back to webjs and resume its existing session.
Baileys links as a Chrome device (shown as "Chrome (Windows)" or "Chrome (Mac OS)" under Linked devices). WhatsApp currently ends new links that claim to be the Desktop app with status 428 ("Connection Terminated") before a QR code appears. Desktop would request the full chat history; Chrome receives recent history, and live messages are stored from then on. BAILEYS_BROWSER=Desktop restores the old behaviour. At startup the backend also looks up the current WhatsApp Web version from web.whatsapp.com, because WhatsApp refuses clients that report an outdated one; WA_WEB_VERSION pins it, and a failed lookup falls back to the version bundled with Baileys.
Baileys and SQLite are pinned optional dependencies installed by normal npm install. If your package manager omitted them, run npm install --include=optional. SQLite uses a native addon; a supported prebuilt binary or a local native build toolchain is required. To avoid downloading Chromium when installing for Baileys or an existing system browser, use:
$env:PUPPETEER_SKIP_DOWNLOAD = 'true'
npm install --include=optional npm run build
On macOS/Linux, the equivalent installation command is PUPPETEER_SKIP_DOWNLOAD=true npm install --include=optional. Selecting Baileys loads only its driver and never starts or cleans up browser processes. An unavailable backend produces an error; it never silently switches drivers or retries a send through another backend.
session.sqlite inside the sign-in folder. Keep the whole folder private and out of version control. Only one running server may own a sign-in folder. Use separate folders for independent accounts.logout tool, ends it; both revoke the OAuth access tokens. Baileys HTTP OAuth state is stored separately from web.js in oauth-store.json inside the sign-in folder.get_backend_status reports the active backend, authentication, stored record counts and history synchronization state. Being connected does not mean history has finished arriving. An available history state means local data is available, not that WhatsApp supplied a complete archive.list_messages may request up to 100 additional older messages when a known chat has fewer than requested, with a bounded wait and a per-chat cooldown. Late history batches are persisted for subsequent queries. WhatsApp may still supply only part of an account's history.@c.us phone-number inputs, @s.whatsapp.net, groups and @lid identifiers are supported; known LID/phone mappings are persisted. Message IDs from web.js cannot be passed to Baileys or vice versa.The Baileys backend is opt-in and pinned to 7.0.0-rc14. Review upstream changes before upgrading, especially authentication and message-format migrations. See the Baileys documentation and release history.
You should only need to scan the QR code once. After that the server stays linked, even when it is restarted, started by a different program, or loses its internet connection for a while.
Where the sign-in lives. By default the sign-in is kept in one fixed place for your user account, whatever folder a program starts the server from:
| System | Baileys | web.js |
|---|---|---|
| Windows | %LOCALAPPDATA%\mcp-whatsapp-web\baileys-sessions | %LOCALAPPDATA%\mcp-whatsapp-web\whatsapp-sessions |
| macOS | ~/Library/Application Support/mcp-whatsapp-web/baileys-sessions | ~/Library/Application Support/mcp-whatsapp-web/whatsapp-sessions |
| Linux | ~/.local/share/mcp-whatsapp-web/baileys-sessions (or under $XDG_DATA_HOME) | ~/.local/share/mcp-whatsapp-web/whatsapp-sessions |
BAILEYS_SESSION_DIR (or WHATSAPP_SESSION_DIR for web.js), that folder is always used.baileys-sessions (or whatsapp-sessions) folder inside the folder the server was started from. If such a sign-in exists and no folder is set, the server keeps using it and says so in its log.get_backend_status shows it too, as connection.signInFolder.Moving the sign-in. Stop every program that runs the server, move the whole folder (all files in it) to the new place, then either put it in the standard place above or point BAILEYS_SESSION_DIR at it, and start the server again.
Using it from more than one program. Two programs cannot share one sign-in at the same time. The second one waits and takes over by itself when the first one closes. If both should run at the same time, give the second program its own folder (BAILEYS_SESSION_DIR) and link it as its own device by scanning a new QR code. WhatsApp allows several linked devices per phone. Never copy a sign-in folder to a second program: the two copies would keep pushing each other off.
When the connection drops. The server reconnects by itself: quickly at first, then every five minutes for as long as it runs, so it recovers on its own when the network comes back. Asking for WhatsApp (for example check_auth_status or any tool) makes it try again at once. get_backend_status tells you in plain words what is going on: connection.state is linked, reconnecting, waiting_for_link, waiting_for_other_program or stopped, with since, lastReason and the next attempt.
What really ends a link. Only these need a new QR code:
logout tool.