Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

WhatsApp Web MCP Server

by mario-andreschakversion 1.2.0i★ 31iRuns on your computerRepository ↗
Registry nameio.github.mario-andreschak/mcp-whatsapp-web

How to install

What it does

WhatsApp MCP via web.js or browserless Baileys: messages, media, chats, groups and contacts

  • Connects Runs on your computer
  • Account or key No key needed · 1 setting to fill in (BROWSER_EXECUTABLE_PATH)
  • Category Chat & email

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity18/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness12/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score30/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

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

Let AI install it

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.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: 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

  2. Fill in 1 setting(s)

    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.

  3. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  4. Paste these settings and save the file

    {
      "mcpServers": {
        "whatsapp-web": {
          "command": "npx",
          "args": [
            "-y",
            "mcp-whatsapp-web"
          ],
          "env": {
            "BROWSER_EXECUTABLE_PATH": "your-value"
          }
        }
      }
    }
  5. Quit Claude and open it again

  6. Try it

    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

15 optional setting(s) (works without them)

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 webjs
  • BAILEYS_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 info
  • LOG_STDERR_LEVEL Log level for stderr (visible in most MCP client logs) · default warn
  • WHATSAPP_HEADLESS webjs only: set to false to show the browser window instead of running headless
  • WHATSAPP_NO_SANDBOX webjs only: explicitly disable the browser sandbox for containers that require it. The sandbox is enabled by default. · default false
  • WHATSAPP_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 code
  • FFMPEG_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 60000
  • TOOL_READY_TIMEOUT_MS How long tool calls wait for the WhatsApp client to become ready before erroring · default 45000
  • MCP_HTTP_PORT When set, additionally exposes the MCP endpoint at http://127.0.0.1: /mcp (Streamable HTTP) from the same process
  • MCP_HTTP_HOST Bind address for the HTTP endpoint (do not expose publicly; the endpoint controls your personal WhatsApp account) · default 127.0.0.1
  • MCP_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 form

Descriptions 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

What you can do instead

A · Use an app that can connect WhatsApp Web MCP Server

  • 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
  • 1 setting(s) to fill in (BROWSER_EXECUTABLE_PATH) · Install Node.js on your computer first (one time)
  • 1 setting(s) to fill in (BROWSER_EXECUTABLE_PATH) · Install Node.js on your computer first (one time)
  • 1 setting(s) to fill in (BROWSER_EXECUTABLE_PATH) · Install Node.js on your computer first (one time)

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)

Let AI install it

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.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: 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

  2. Fill in 1 setting(s)

    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.

  3. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  4. Paste this command and press Enter

    claude mcp add --scope user whatsapp-web --env BROWSER_EXECUTABLE_PATH=your-value -- npx -y mcp-whatsapp-web
  5. Type /mcp in Claude Code

    You should see WhatsApp Web MCP Server listed as connected

  6. Try it

    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

15 optional setting(s) (works without them)

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 webjs
  • BAILEYS_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 info
  • LOG_STDERR_LEVEL Log level for stderr (visible in most MCP client logs) · default warn
  • WHATSAPP_HEADLESS webjs only: set to false to show the browser window instead of running headless
  • WHATSAPP_NO_SANDBOX webjs only: explicitly disable the browser sandbox for containers that require it. The sandbox is enabled by default. · default false
  • WHATSAPP_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 code
  • FFMPEG_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 60000
  • TOOL_READY_TIMEOUT_MS How long tool calls wait for the WhatsApp client to become ready before erroring · default 45000
  • MCP_HTTP_PORT When set, additionally exposes the MCP endpoint at http://127.0.0.1: /mcp (Streamable HTTP) from the same process
  • MCP_HTTP_HOST Bind address for the HTTP endpoint (do not expose publicly; the endpoint controls your personal WhatsApp account) · default 127.0.0.1
  • MCP_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 form

Descriptions 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)

Let AI install it

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.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: 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

  2. Fill in 1 setting(s)

    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.

  3. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  4. Fill in your key

    In the WhatsApp Web MCP Server settings, BROWSER_EXECUTABLE_PATH is empty; add your key and save

  5. Open the AI chat in Cursor in Agent mode

  6. Try it

    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

15 optional setting(s) (works without them)

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 webjs
  • BAILEYS_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 info
  • LOG_STDERR_LEVEL Log level for stderr (visible in most MCP client logs) · default warn
  • WHATSAPP_HEADLESS webjs only: set to false to show the browser window instead of running headless
  • WHATSAPP_NO_SANDBOX webjs only: explicitly disable the browser sandbox for containers that require it. The sandbox is enabled by default. · default false
  • WHATSAPP_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 code
  • FFMPEG_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 60000
  • TOOL_READY_TIMEOUT_MS How long tool calls wait for the WhatsApp client to become ready before erroring · default 45000
  • MCP_HTTP_PORT When set, additionally exposes the MCP endpoint at http://127.0.0.1: /mcp (Streamable HTTP) from the same process
  • MCP_HTTP_HOST Bind address for the HTTP endpoint (do not expose publicly; the endpoint controls your personal WhatsApp account) · default 127.0.0.1
  • MCP_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 form

Descriptions 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)

Let AI install it

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.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: 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

  2. Fill in 1 setting(s)

    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.

  3. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  4. Fill in your key

    In the WhatsApp Web MCP Server settings, BROWSER_EXECUTABLE_PATH is empty; add your key and save

  5. Open the AI chat in VS Code in Agent mode

  6. Try it

    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

15 optional setting(s) (works without them)

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 webjs
  • BAILEYS_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 info
  • LOG_STDERR_LEVEL Log level for stderr (visible in most MCP client logs) · default warn
  • WHATSAPP_HEADLESS webjs only: set to false to show the browser window instead of running headless
  • WHATSAPP_NO_SANDBOX webjs only: explicitly disable the browser sandbox for containers that require it. The sandbox is enabled by default. · default false
  • WHATSAPP_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 code
  • FFMPEG_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 60000
  • TOOL_READY_TIMEOUT_MS How long tool calls wait for the WhatsApp client to become ready before erroring · default 45000
  • MCP_HTTP_PORT When set, additionally exposes the MCP endpoint at http://127.0.0.1: /mcp (Streamable HTTP) from the same process
  • MCP_HTTP_HOST Bind address for the HTTP endpoint (do not expose publicly; the endpoint controls your personal WhatsApp account) · default 127.0.0.1
  • MCP_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 form

Descriptions 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.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use WhatsApp Web MCP Server💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user whatsapp-web --env BROWSER_EXECUTABLE_PATH=your-value -- npx -y mcp-whatsapp-web

Claude 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"
      }
    }
  }
}

Values you fill in

  • WHATSAPP_BACKEND env
    WhatsApp backend: webjs uses a persistent browser profile; baileys connects without a browser and requires separate pairing
  • BAILEYS_SESSION_DIR env
    Baileys credentials and synchronized history directory (default: /baileys-sessions). Use a private absolute path, owned by one server process.
  • LOG_LEVEL env
    Log level for the log file (logs/mcp-whatsapp.log)
  • LOG_STDERR_LEVEL env
    Log level for stderr (visible in most MCP client logs)
  • WHATSAPP_HEADLESS env
    webjs only: set to false to show the browser window instead of running headless
  • WHATSAPP_NO_SANDBOX env
    webjs only: explicitly disable the browser sandbox for containers that require it. The sandbox is enabled by default.
  • BROWSER_EXECUTABLE_PATH required env
    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 env
    webjs only: persistent browser profile directory (default: /whatsapp-sessions)
  • WHATSAPP_PAIRING_PHONE_NUMBER env
    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 env
    Path to an ffmpeg binary (only needed to override the ffmpeg installed automatically via the ffmpeg-static npm package)
  • WA_WEB_VERSION env
    webjs only: pin the WhatsApp Web version if a WhatsApp-side update breaks the client.
  • HEALTH_CHECK_INTERVAL_MS env
    webjs only: connection health check interval in milliseconds (<=0 disables)
  • TOOL_READY_TIMEOUT_MS env
    How long tool calls wait for the WhatsApp client to become ready before erroring
  • MCP_HTTP_PORT env
    When set, additionally exposes the MCP endpoint at http://127.0.0.1: /mcp (Streamable HTTP) from the same process
  • MCP_HTTP_HOST env
    Bind address for the HTTP endpoint (do not expose publicly; the endpoint controls your personal WhatsApp account)
  • MCP_OAUTH env
    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

Descriptions are as written by the maker.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
76/wk
Connection
Runs on your computer
Latest versioni
1.2.0
Published to registryi
Sep 6, 2026
Code last changedi
Nov 11, 2026
Maker
mario-andreschak
Packages
npm: mcp-whatsapp-web
Website
github.com
Registry status
Active

Which apps can use it

Based 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

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

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

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account mario-andreschak, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 8 days ago

  • ✓ Pass

    Has a licence

    Uses MIT

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

No entries on OSV.dev for mcp-whatsapp-web@1.2.0

Checks only this package version, not every dependency · checked Nov 15, 2026

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/mario-andreschak-mcp-whatsapp-web.svg)](https://mcp.popnx.com/en/servers/mario-andreschak-mcp-whatsapp-web)

Discussion

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.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Chat & emaili

  • More stars than 97% of the other 2027 servers in this category
  • Published to the registry more recently than 23% of the other 2027 servers in this category
  • Basic checks equal to or better than 99% of the other 2027 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is WhatsApp Web MCP Server safe?

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.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

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).

Is it still maintained?

The GitHub repo last changed 8 days ago, and the latest version (1.2.0) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: emailmd, Kite Discord Bot Builder, e2a — email for AI agents, Infobip MCP, kernelCAD

Similar alternatives

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

emailmd

Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.

by anypostWidely used↓ 5.4K/wk★ 1.4KUpdated 5 days ago

Computer or cloud✓ service owner · emailmd.dev

Infobip MCP

Infobip MCP server for omnichannel communication and messaging. SMS, RCS, WhatsApp, Viber and more.

by infobipEarly★ 36Updated 13 months ago

Runs in the cloud✓ service owner · infobip.com

kernelCAD

CAD in ChatGPT and Claude: editable parts, STEP/STL/drawings, in-chat 3D, automatic checks.

by w1neEarly★ 35Updated 23 days ago

Runs in the cloud✓ service owner · kernelcad.com
Compared with similar ones
This one
WhatsApp Web MCP Server
emailmdKite Discord Bot Buildere2a — email for AI agentsInfobip MCPkernelCAD
Runs whereInstalls on your computerCloud or install on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyNoNoNoNoNoNo
Add with + in ClaudeNoNoNoNoYesNo
Basic checks3/35/54/44/44/44/4
LicenseMITMITAGPL-3.0Apache-2.0MITMIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

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.

Very Important

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.

MCP WhatsApp Web (TypeScript)

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:

  • Search and read your personal WhatsApp messages (including media)
  • Search your contacts
  • Send messages to individuals or groups
  • Send and receive media files (images, videos, documents, audio)

Features

  • TypeScript Implementation: Fully typed codebase for better developer experience and code reliability
  • Selectable WhatsApp Backend: Uses whatsapp-web.js by default, with an optional Baileys backend that runs without a browser
  • MCP Server: Implements the Model Context Protocol for seamless integration with AI assistants
  • Media Support: Send and receive images, videos, documents, and audio messages
  • Webhooks (Baileys): signed notifications for new messages and for incoming calls, including who is calling
  • Multiple Transport Options: Supports stdio and Streamable HTTP transports — even both at once from a single process (start with stdio and set MCP_HTTP_PORT to additionally expose http://127.0.0.1: /mcp, or run HTTP-only with --http)
  • Flexible Authentication: QR code (as an MCP image tool), pairing code (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-authenticate

Architecture

This MCP server consists of:

  1. TypeScript MCP Server: Implements the Model Context Protocol to provide standardized tools for AI assistants to interact with WhatsApp
  2. WhatsApp Backend: A shared service interface selects web.js/Puppeteer or Baileys/WebSocket, handles authentication, and manages message sending/receiving
  3. Tool Implementations: Provides various tools for contacts, chats, messages, media, and authentication

Prerequisites

  • Node.js >= 22.0.0 (Node 22 or 24 recommended for the Baileys SQLite dependency)
  • npm or yarn
  • For the default webjs backend: Google Chrome or Microsoft Edge (auto-detected; needed for video/GIF codec support; other operations can use Puppeteer's bundled Chromium)
  • For 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.

Installation

npx
   npx mcp-whatsapp-web
Manual Installation
  1. Clone this repository
   git clone https://github.com/mario-andreschak/mcp-whatsapp-web.git

cd mcp-whatsapp-web

  1. Install dependencies
   npm install
  1. Build the project
   npm run build
  1. Configure environment variables (optional)

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).

Choosing a backend

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

Optional: where the sign-in lives. Leave it out to use the standard place.

#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.

Baileys sessions and history
  • Credentials, Signal keys, contacts, chats and messages persist in 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.
  • Normal shutdown and lost connections keep the sign-in. Only a clear "this device was removed" from WhatsApp, or the 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.
  • Contact and history tools query the local synchronized store. Initial full-history sync is requested and can take time on large accounts. 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.
  • Treat returned message IDs as opaque and use IDs from the active backend. Legacy @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.
  • Text, media, downloads, voice notes and the existing authentication tools use the same MCP interface. Voice-note inputs must be local files or base64; FFmpeg converts them to mono Opus/Ogg before sending. If conversion fails, the tool reports an error without sending a different message type.

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.

Keeping the link

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:

SystemBaileysweb.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
  • If you set BAILEYS_SESSION_DIR (or WHATSAPP_SESSION_DIR for web.js), that folder is always used.
  • Older versions kept the sign-in in a 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.
  • At start the log says which folder is used and whether it holds a sign-in. 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:

  • The device was removed under Settings > Linked devices on the phone, or with the logout tool.
  • The phone was offline for a long time (WhatsApp ends linked devices after about 14 days without the phone).
  • WhatsApp itself ends the link, for examp

Only the beginning is shown; read the rest in the repo