mcpbeat Sign in

Whatsapp MCP Server

answering

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

WhatsApp assistants, messaging, broadcasts, and analytics for your iZap account, over OAuth.

Uptime history 52 days of history · worst day 92%
52 days agonow
95.6%
Uptime 24h
87 of 91 checks
Tools
hidden behind auth
1139 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Whatsapp does not always answer

Over the last week it answered 98.3% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

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 11 min ago.

run in your terminal
claude mcp add whatsapp --transport http https://api.izap.ai/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "whatsapp": {
      "url": "https://api.izap.ai/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.whatsapp]
url = "https://api.izap.ai/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "whatsapp": {
      "url": "https://api.izap.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "whatsapp": {
      "url": "https://api.izap.ai/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://api.izap.ai/mcp streamable-http sign-in 1142 ms 11 min ago

Alternatives to Whatsapp

same job, measured the same way
Whatsapp
by corapilot

Let Claude or ChatGPT search, read and send your WhatsApp messages over MCP. OAuth sign-in.

answering
Leporis WhatsApp
by admin-rstechie

Send and read WhatsApp messages on your Leporis account from AI coding agents, via your own API key.

answering
DripRaven WhatsApp campaigns
by dripraven

Run WhatsApp Business campaigns from any AI assistant: contacts, segments, and broadcasts.

answering
Atmita
by atmita

Message your Atmita agent - one connection reaches all its accounts and tools, WhatsApp included.

answering
WhatsApp Messaging API
by jevil25

Send WhatsApp messages from Claude. No Meta Business approval or WhatsApp Business account.

36 installs/wk local only
MCP Evolution API
by codespar

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

24 installs/wk local only
MCP Z API
by codespar

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

19 installs/wk local only
Wazap
by razvangirgiz

WhatsApp for your agent: chats, messages, media, contacts and groups behind MCP tools.

1 131 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: 95.6% 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 87 of 91 checks got a reply (95.6%), average response time 1139 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 with the file path 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 1139 ms on average, which is faster than 8% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.