MCP Whatsapp Web MCP Server

MCP Whatsapp Web MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. TypeScript MCP server for WhatsApp using whatsapp-web.js.

What you get

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.

• TypeScript Implementation — Fully typed codebase for better developer experience and code reliability
• WhatsApp Web Integration — Uses whatsapp-web.js for direct connection to WhatsApp Web
• MCP Server — Implements the Model Context Protocol for seamless integration with AI assistants
• Media Support — Send and receive images, videos, documents, and audio messages
• 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)

What the assistant can call

Once MCP Whatsapp Web is connected, these are the calls the assistant has available:

• Authentication — The Authentication tool exposed by this server
• Contacts — The Contacts tool exposed by this server
• Chats — The Chats tool exposed by this server
• Messages — The Messages tool exposed by this server
• Media — The Media tool exposed by this server
• Scripts — The Scripts tool exposed by this server

Configuration and credentials

You will need 2 environment variables: FFMPEG_PATH, BROWSER_EXECUTABLE_PATH. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js >= 20.0.0 - npm or yarn - Google Chrome or Microsoft Edge (auto-detected; only needed for sending videos/GIFs — everything else works with the Chromium that puppeteer downloads automatically) 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.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Choosing this one

Among the team communication options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCP Whatsapp Web's toolset — Authentication, Contacts, Chats and 3 more — is a fair guide to whether it matches your workflow. It is maintained by mario-andreschak; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp whatsapp web mcp server does with a few real requests.