mcpbeat Sign in

Whatsapp MCP Server

answering

Whatsapp is answering right now. Last checked 9 min ago.

WhatsApp (Web + Business API), SMS, contacts, and call records via 2Chat's MCP server.

Uptime history 91 days of history · worst day 97%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
468 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Whatsapp every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add whatsapp --transport http https://mcp.2chat.io/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mcp.2chat.io/mcp
~/.codex/config.toml
[mcp_servers.whatsapp]
url = "https://mcp.2chat.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "whatsapp": {
      "url": "https://mcp.2chat.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "whatsapp": {
      "type": "http",
      "url": "https://mcp.2chat.io/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://mcp.2chat.io/mcp streamable-http sign-in 375 ms 9 min ago

Alternatives to Whatsapp

same job, measured the same way
WhatsApp MCP Server
by nakulben

Manage WhatsApp Business templates and send messages via Meta Cloud API

107 installs/wk local only
WhatsApp Web MCP Server
by mario-andreschak

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

76 installs/wk local only
MCP Z API
by codespar

MCP server for Z-API — WhatsApp messaging, contacts, media

60 installs/wk local only
ManyContacts - WhatsApp Business MCP
by manycontacts

WhatsApp Business MCP: send messages, manage contacts, campaigns, and AI agents.

90 installs/wk local only
CatchMyCall
by catchmycall

Place calls, send WhatsApp messages, and read call records, contacts, leads and campaigns

answering
AirysChat MCP Server
by airys

Operate AirysChat — conversations, CRM, AI Agents, Meta Business Agent, and WhatsApp campaigns.

425 installs/wk answering
ManyContacts - WhatsApp Business CRM
by manycontacts

WhatsApp Business CRM: send messages, manage contacts, campaigns, and AI agents.

local only
MCP Evolution API
by codespar

MCP server for Evolution API — WhatsApp messaging, instances, contacts

137 installs/wk local only

Whatsapp — questions

Answers built from our own checks of this server.

Why is there no tool list for Whatsapp?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Whatsapp working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 468 ms. The bar chart above shows every period we have measured.
How do I connect Whatsapp?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Whatsapp?
No API key is involved. Whatsapp answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Whatsapp?
It answers our handshake in 468 ms on average, which is faster than 26% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.