AgentHubAgentHub

WhatsApp Web MCP Setup & Guide

MCP ServerMCP RegistryOfficial

io.github.mario-andreschak/mcp-whatsapp-web · v1.2.0

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

Copy the install config on this page first, then verify docs and permissions upstream.

Overview

WhatsApp MCP via web.js or browserless Baileys: messages, media, chats, groups and contacts WhatsApp Web MCP Server is a MCP Server listed from MCP Registry. Transports: stdio. This page includes an overview, setup tutorial, install commands, and use cases for Trae, Tongyi Lingma, Cursor, Claude Code, and VS Code.

Use cases

AgentHub Verified AvailabilityTested & Ready

Automated pipeline validated install commands, protocol & client compatibility

Verified At2026-10-04
Install Snippets TestedCLI & JSON config syntax verified
Protocol Handshake ReadyComplies with JSON-RPC 2.0 specifications
Origin Registry ActiveSourced from official-mcp-registry
Verified ClientsClaude Code、Claude Desktop、Cursor 等
Security Tier: A+ 级 · 官方认证推荐 (A+)·Maintained by official/verified teams, audited for standard MCP protocol compliance.

Copy by platform

Choose your platform

  1. Open or create .cursor/mcp.json in your project root
  2. Click Copy config and paste; merge only this mcpServers entry if others exist
  3. Replace <placeholders> in env with real secrets (see Environment variables below)
  4. Save, then Cmd+Shift+P → Reload Window

Pre-fill Environment Variables (Optional)

Privacy Guarantee: Keys are replaced 100% locally in your browser memory and are NEVER uploaded or stored on any server.
Click to copy snippet
{
  "mcpServers": {
    "mcp-whatsapp-web": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-whatsapp-web"
      ]
    }
  }
}

Setup tutorial

  1. Open the WhatsApp Web MCP Server page and confirm this MCP Server (source: MCP Registry).
  2. Copy the Cursor, Claude Code, or VS Code snippet.
  3. Merge it into mcpServers and replace env placeholders with real secrets.
  4. Reload the window, then call the MCP tools from your agent chat.

Install commands

Install commands and setup steps are in the HTML so search engines and no-JS browsers can read them without running client JavaScript.

Claude Code (local)

  1. Install Claude Code CLI
  2. Copy the command below, replace <placeholders> with real env values, then run in terminal
  3. See Environment variables below if listed
claude mcp add mcp-whatsapp-web -- npx -y mcp-whatsapp-web

Cursor — .cursor/mcp.json (local)

  1. Open or create .cursor/mcp.json in your project root
  2. Click Copy config and paste; merge only this mcpServers entry if others exist
  3. Replace <placeholders> in env with real secrets (see Environment variables below)
  4. Save, then Cmd+Shift+P → Reload Window
{
  "mcpServers": {
    "mcp-whatsapp-web": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-whatsapp-web"
      ]
    }
  }
}

VS Code — .vscode/mcp.json (local)

  1. Install GitHub Copilot in VS Code with MCP support
  2. Open or create .vscode/mcp.json in your project root
  3. Click Copy config and paste; merge only this mcpServers entry if others exist
  4. Replace <placeholders> in env with real secrets
  5. Save and Developer: Reload Window
{
  "mcpServers": {
    "mcp-whatsapp-web": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-whatsapp-web"
      ]
    }
  }
}

Claude Desktop — claude_desktop_config.json (local)

  1. Open Claude Desktop claude_desktop_config.json (see remote guide for paths)
  2. Click Copy config and merge under mcpServers
  3. Replace <placeholders> in env with real secrets
  4. Fully quit and restart Claude Desktop
{
  "mcpServers": {
    "mcp-whatsapp-web": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-whatsapp-web"
      ]
    }
  }
}

Trae — .trae/mcp.json (local)

  1. Trae → Settings → MCP, or edit .trae/mcp.json / global mcp.json
  2. Click Copy config and merge mcpServers
  3. Replace <placeholders> in env with real secrets
  4. Save and reload Trae
{
  "mcpServers": {
    "mcp-whatsapp-web": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-whatsapp-web"
      ]
    }
  }
}

Cherry Studio — MCP settings (local)

  1. Cherry Studio → Settings → MCP Servers → Add (STDIO)
  2. Or import JSON: click Copy config and merge mcpServers
  3. Replace <placeholders> in env; ensure Node.js / uv (npx, uvx) are installed
  4. Enable the server and check tools load
{
  "mcpServers": {
    "mcp-whatsapp-web": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-whatsapp-web"
      ]
    }
  }
}

Tongyi Lingma — MCP config (local)

  1. Lingma Settings → MCP → + → STDIO or config file
  2. Click Copy config and merge mcpServers
  3. Replace <placeholders> in env; need Node.js 18+ (npx) or uv (uvx)
  4. Confirm connected before using tools in agent chat
{
  "mcpServers": {
    "mcp-whatsapp-web": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-whatsapp-web"
      ]
    }
  }
}

Windsurf — mcp_config.json (local)

  1. Edit ~/.codeium/windsurf/mcp_config.json
  2. Click Copy config and merge mcpServers (stdio same as Cursor)
  3. Replace <placeholders> in env, save, refresh Cascade
{
  "mcpServers": {
    "mcp-whatsapp-web": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-whatsapp-web"
      ]
    }
  }
}

Cline — MCP Servers (local)

  1. Cline panel → Settings → MCP Servers
  2. Click Copy config and merge
  3. Replace <placeholders> in env, then save
{
  "mcpServers": {
    "mcp-whatsapp-web": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-whatsapp-web"
      ]
    }
  }
}

WorkBuddy — .workbuddy/mcp.json (local)

  1. Edit ~/.workbuddy/mcp.json (user) or project .workbuddy/mcp.json
  2. Or Plugins → MCP Servers → Configure MCP and paste the JSON below
  3. Replace <placeholders> in env; on Windows prefer absolute paths for command/scripts
  4. Save, restart WorkBuddy, confirm connector status is green
{
  "mcpServers": {
    "mcp-whatsapp-web": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-whatsapp-web"
      ]
    }
  }
}

Troubleshooting & Common ErrorsFAQ

Common connection errors and verified fixes for WhatsApp Web MCP Server

Getting 'connection closed' or exit code 1 in Cursor / Claude Code for WhatsApp Web MCP Server?

Usually caused by missing runtime paths or IDE environment inheritance. Fix steps: 1. Verify Node.js 18+ (npx) or Python 3.10+ (uvx) is installed; 2. Run 'which npx' or 'which uvx' in terminal, and replace 'command' with absolute path; 3. Reload or restart the client window after modifying config.

Fix Snippet
# Check binary path in terminal:
which npx
node -v
Getting 'spawn npx ENOENT' or 'command not found'?

The editor background process does not inherit your full terminal PATH. Solution: Globally install the package, or set the absolute binary path (e.g. C:\Program Files\nodejs\npx.cmd on Windows, or /usr/local/bin/npx on macOS).

Missing required environment variable or authentication failure?

WhatsApp Web MCP Server requires environment variables (WHATSAPP_BACKEND、BAILEYS_SESSION_DIR、LOG_LEVEL、LOG_STDERR_LEVEL、WHATSAPP_HEADLESS、WHATSAPP_NO_SANDBOX、BROWSER_EXECUTABLE_PATH、WHATSAPP_SESSION_DIR、WHATSAPP_PAIRING_PHONE_NUMBER、FFMPEG_PATH、WA_WEB_VERSION、HEALTH_CHECK_INTERVAL_MS、TOOL_READY_TIMEOUT_MS、MCP_HTTP_PORT、MCP_HTTP_HOST、MCP_OAUTH). Ensure you have added valid keys under the 'env' object in your config file without trailing whitespace.

Fix Snippet
// .cursor/mcp.json 或 claude_desktop_config.json
{
  "env": {
    "API_KEY": "your_actual_key_here"
  }
}

Tool Mock Playground

Sandbox

WhatsApp Web MCP Server Tool Interface Simulation · Preview tool schema & outputs without local runtime

Sandbox Ready
fn: mcp_whatsapp_webExecute the core tool interface of WhatsApp Web MCP Server
Request ArgumentsJSON Schema
{
  "target": "WhatsApp Web MCP Server",
  "action": "execute",
  "options": {
    "mode": "standard",
    "timeoutMs": 5000
  }
}
💡Parameters generated dynamically by Agent runtime
Agent Tool Output

Click 'Run Mock' above

to preview the raw response returned to the LLM

Env: AgentHub Virtual SandboxJSON-RPC 2.0

Decision Guide: Why & When to Use

Assess suitability before installing to save trial-and-error time

Best Suited For
  • PR review
  • Changelog generation
  • Cross-repo issue search
When NOT to Use
  • Replacing human security audit
  • Unauthorized repo access
Recommended Workflow Pairing:View Scenario →

WhatsApp Web MCP Server + Scenario Prompt → Complete Agent Automation

MCP hands-on: install to visible results

Follow the full lab (expected UI/output + contrast checks). After installing this item, verify with the tutorial prompts.

Open tutorial →

Related resources

Often paired with

Planning with files

v3.23.0

SkillClawHub44.6k

io.clawhub.othmanadi/planning-with-files

Persistent file-based planning for multi-step AI-agent work. Keeps task_plan.md, findings.md, and progress.md on disk; lifecycle hooks inject selected project planning context. Automatic recovery reads project planning files only. Explicit session-catchup.py --metadata reads same-project local agent session records and emits aggregate counts only; --replay may emit bounded nonce-framed excerpts. Optional gated mode can request continuation only when the host supports it and never runs commands declared in Markdown. The skill has no network upload path. Use for research or work needing 5+ tool calls.

source

ClawCall

v2.0.1

SkillClawHub53.1k

io.clawhub.clawcall-dev/clawcall-dev

Use when the user wants an AI agent to place a US phone call, call a business, handle hold or phone menus, confirm/reschedule/cancel/book/follow up/check an order, reach a real person, leave voicemail, connect the user into a live call, configure ClawCall voice/personality/profile or inbound reserved-number answering, poll received inbound calls, or link a ClawCall API key. Not for SMS, email, or international calls.

source

中文公文写作

v2.0.25

SkillClawHub9.1k

io.clawhub.gongyu0918-debug/chinese-official-writing

用于中文公文、事务性材料和新闻稿件的起草、改写、压缩、润色、审校、文种核对、去口语化、降 AI 味及 Word 格式处理,适用于机关、企事业单位、学校和新闻机构。涵盖申请、请示、报告、通知、通告、意见、决定、决议、议案、公报、命令、函、复函、批复、说明、方案、纪要、公告、公示、通报、制度、规定、办法、细则、操作规程、工作要点、总结、调研、讲话、致辞、主持词、述职、可研、审查材料、技术需求、新闻消息、编者按、新闻评论,以及采购、整改、反馈和 AI 算力等场景。

source

Keep exploring AgentHub

Most people compare similar tools or check scenario guides before installing—start here.

Listing badge: put AgentHub on your site

Copy either snippet into your project homepage, docs, or GitHub README. The badge is a hotlinked SVG — nothing to host — and it links back to this page so visitors can find the install steps.

PreviewListed on AgentHub: WhatsApp Web MCP Server
HTML
<a href="https://myagenthub.cn/p/io.github.mario-andreschak/mcp-whatsapp-web" title="Listed on AgentHub: WhatsApp Web MCP Server" target="_blank" rel="noopener">
  <img src="https://myagenthub.cn/badge/io.github.mario-andreschak/mcp-whatsapp-web?lang=en" alt="Listed on AgentHub: WhatsApp Web MCP Server" height="20" style="border:0"/>
</a>
Markdown (GitHub README)
[![Listed on AgentHub: WhatsApp Web MCP Server](https://myagenthub.cn/badge/io.github.mario-andreschak/mcp-whatsapp-web?lang=en)](https://myagenthub.cn/p/io.github.mario-andreschak/mcp-whatsapp-web)

Badges are generated on the fly from /badge/<package-id>, so name and listing changes propagate automatically. Keep the link target unchanged — it is what counts as the referral.

Unified Manifest

{
  "id": "io.github.mario-andreschak/mcp-whatsapp-web",
  "type": "mcp-server",
  "version": "1.2.0",
  "displayName": "WhatsApp Web MCP Server",
  "description": "WhatsApp MCP via web.js or browserless Baileys: messages, media, chats, groups and contacts",
  "repository": {
    "url": "https://github.com/mario-andreschak/mcp-whatsapp-web",
    "source": "github"
  },
  "homepage": "https://github.com/mario-andreschak/mcp-whatsapp-web",
  "distribution": {
    "packages": [
      {
        "registryType": "npm",
        "identifier": "mcp-whatsapp-web",
        "version": "1.2.0",
        "runtimeHint": "npx",
        "transport": "stdio",
        "environmentVariables": [
          {
            "name": "WHATSAPP_BACKEND",
            "description": "WhatsApp backend: webjs uses a persistent browser profile; baileys connects without a browser and requires separate pairing"
          },
          {
            "name": "BAILEYS_SESSION_DIR",
            "description": "Baileys credentials and synchronized history directory (default: <working directory>/baileys-sessions). Use a private absolute path, owned by one server process."
          },
          {
            "name": "LOG_LEVEL",
            "description": "Log level for the log file (logs/mcp-whatsapp.log)"
          },
          {
            "name": "LOG_STDERR_LEVEL",
            "description": "Log level for stderr (visible in most MCP client logs)"
          },
          {
            "name": "WHATSAPP_HEADLESS",
            "description": "webjs only: set to false to show the browser window instead of running headless"
          },
          {
            "name": "WHATSAPP_NO_SANDBOX",
            "description": "webjs only: explicitly disable the browser sandbox for containers that require it. The sandbox is enabled by default."
          },
          {
            "name": "BROWSER_EXECUTABLE_PATH",
            "description": "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."
          },
          {
            "name": "WHATSAPP_SESSION_DIR",
            "description": "webjs only: persistent browser profile directory (default: <working directory>/whatsapp-sessions)"
          },
          {
            "name": "WHATSAPP_PAIRING_PHONE_NUMBER",
            "description": "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"
          },
          {
            "name": "FFMPEG_PATH",
            "description": "Path to an ffmpeg binary (only needed to override the ffmpeg installed automatically via the ffmpeg-static npm package)"
          },
          {
            "name": "WA_WEB_VERSION",
            "description": "webjs only: pin the WhatsApp Web version if a WhatsApp-side update breaks the client."
          },
          {
            "name": "HEALTH_CHECK_INTERVAL_MS",
            "description": "webjs only: connection health check interval in milliseconds (<=0 disables)"
          },
          {
            "name": "TOOL_READY_TIMEOUT_MS",
            "description": "How long tool calls wait for the WhatsApp client to become ready before erroring"
          },
          {
            "name": "MCP_HTTP_PORT",
            "description": "When set, additionally exposes the MCP endpoint at http://127.0.0.1:<port>/mcp (Streamable HTTP) from the same process"
          },
          {
            "name": "MCP_HTTP_HOST",
            "description": "Bind address for the HTTP endpoint (do not expose publicly; the endpoint controls your personal WhatsApp account)"
          },
          {
            "name": "MCP_OAUTH",
            "description": "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"
          }
        ]
      }
    ],
    "remotes": []
  },
  "dependencies": [],
  "installTargets": [
    "claude-code",
    "claude-desktop",
    "cursor",
    "vscode",
    "trae",
    "cherry-studio",
    "lingma",
    "windsurf",
    "cline",
    "workbuddy"
  ],
  "keywords": [],
  "provenance": {
    "origin": "official-mcp-registry",
    "originalId": "io.github.mario-andreschak/mcp-whatsapp-web",
    "originalUrl": "https://registry.modelcontextprotocol.io/v0.1/servers/io.github.mario-andreschak%2Fmcp-whatsapp-web/versions/latest",
    "isOfficial": true,
    "status": "active"
  }
}
WhatsApp Web MCP Setup & Guide - AgentHub