mcpbeat Sign in
C

Whatsapp MCP Server

by corapilot Your server? Claim it
answering

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

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

Uptime history 3 hours of history
3 hours agonow
100.0%
Uptime 24h
8 of 8 checks
Tools
hidden behind auth
169 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 15 min ago.

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

Alternatives to Whatsapp

same job, measured the same way
M
Whatsapp
by wacli

Your own WhatsApp as an MCP server: read, search and send from any MCP client.

answering
Telegram MCP
by jgalea

Telegram MCP server: read, send, and search messages and manage chats via your account.

90 installs/wk local only
Whatsapp
by gaviwhatsapp

Send WhatsApp messages from Cursor, Claude Code, and Codex via MCP.

23 installs/wk local only
WhatsApp Connect
by idle-sync

Read, search, and send personal WhatsApp messages from any MCP client, behind a send-confirm gate.

local only
Dialogbrain
by saloprj

Unified inbox MCP for WhatsApp, Telegram, Email, voice — read/send messages, search, AI agents.

answering
Slack MCP Server
by stevenvo

Read Slack conversations, threads, user info, and search messages from your MCP client.

52 installs/wk local only
Kontato
by kontato

Give your AI agents a real WhatsApp number to send and receive messages.

9 tools answering
WhatsApp MCP by TimelinesAI
by initechsoftware

Drive your real WhatsApp inbox from Claude — send, reply, label, assign, and triage via TimelinesAI.

answering

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 8 of 8 checks got a reply (100.0%), average response time 169 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 169 ms on average, which is faster than 73% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.