← Index

WhatsApp Web MCP Server

io.github.mario-andreschak/mcp-whatsapp-webv1.1.0Chat & Messaging

MCP server for WhatsApp via whatsapp-web.js: send/receive messages, media, chats, groups, contacts

The current version, v1.1.0, was published to the official MCP registry on 2026-07-05. It is distributed as mcp-whatsapp-web on npm, filed under Chat & Messaging by this index, and declares 13 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.

In-path gate · all MCP tools

Using WhatsApp Web MCP Server in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).

Install the mcpindex gate (one command)

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

uv tool install mcpindex-gate && mcpindex-config-wire
Trust verdict · v1 advisory · method
REVIEWstatus: PARTIALfresh until 2026-08-27 10:49 UTC
screened 2026-07-21tier: scannedgranularity: description-levelsource: registry

Semantic screen found no manipulation pattern in the description. Conformance probe not yet run.

mcpindex.integrity.descriptionpassINFO

evidenceDeclared capabilities, no hidden instructionsvia static_description

Limits of this verdict
  • - Semantic screen only - the deterministic conformance probe has not run on this server
  • - Confidence is reported but not yet calibrated (v1)
  • - Screen reads the tool description, not the live behavior
  • - advisory
  • - registry description only no input schema
  • - screen model 8b
  • - Still current: the description we screened is unchanged, re-checked against the registry

Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.

Own this server? Screen its description →

That verdict was true at screening time (snapshot 2026-08-20).

Contracts can change after screening, with no version bump. The gate pins WhatsApp Web MCP Server’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

See your first HOLD in 2 minutes →

Related: how to trust an MCP server · screen before install · silent contract drift

Cite this record

People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.

Markdown
[Independent trust record for WhatsApp Web MCP Server](https://mcpindex.ai/server/io-github-mario-andreschak-mcp-whatsapp-web) - screening verdict, registry provenance, and contract drift monitoring.
HTML
<a href="https://mcpindex.ai/server/io-github-mario-andreschak-mcp-whatsapp-web">Independent trust record for WhatsApp Web MCP Server</a> - screening verdict, registry provenance, and contract drift monitoring.
Embed this badge

A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.

Markdown
[![mcpindex](https://mcpindex.ai/api/v1/badge/io-github-mario-andreschak-mcp-whatsapp-web)](https://mcpindex.ai/server/io-github-mario-andreschak-mcp-whatsapp-web)
HTML
<a href="https://mcpindex.ai/server/io-github-mario-andreschak-mcp-whatsapp-web"><img src="https://mcpindex.ai/api/v1/badge/io-github-mario-andreschak-mcp-whatsapp-web" alt="mcpindex verdict" height="20" /></a>
Environment variables
LOG_LEVEL

Log level for the log file (logs/mcp-whatsapp.log)

LOG_STDERR_LEVEL

Log level for stderr (visible in most MCP client logs)

WHATSAPP_HEADLESS

Set to false to show the browser window instead of running headless (debugging aid)

BROWSER_EXECUTABLE_PATH

Browser executable. Chrome and Edge are auto-detected in their standard install locations; set this only to use a specific browser. A real Chrome/Edge is required for sending videos and GIFs.

WHATSAPP_SESSION_DIR

Where the WhatsApp session (browser profile) is stored (default: <working directory>/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

Pin the WhatsApp Web version. Only set this if a WhatsApp-side update breaks the client.

HEALTH_CHECK_INTERVAL_MS

Connection health check interval in milliseconds (<=0 disables)

TOOL_READY_TIMEOUT_MS

How long tool calls wait for the WhatsApp client to become ready before erroring

MCP_HTTP_PORT

When set, additionally exposes the MCP endpoint at http://127.0.0.1:<port>/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)

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

MCP quality score · maturity, not trust · methodology
freshness
24
completeness
25
installability
25
documentation
15
stability
10
Alternatives in Chat & Messaging