Whatsapp MCP Server

by corapilot Your server? Claim it

answering

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

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

Uptime history 47 days of history · worst day 99%

47 days agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

193 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.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add whatsapp --transport http https://corapilot.com/mcp

Settings → Connectors → Add custom connector, then paste this address

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

{
  "servers": {
    "whatsapp": {
      "type": "http",
      "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

URL	Transport	State	Latency	Checked
https://corapilot.com/mcp	streamable-http	sign-in	270 ms	3 min ago

Alternatives to Whatsapp

same job, measured the same way

WaBot

by astranexo-wabot

Your own WhatsApp in Claude and ChatGPT: read chats, draft replies, send messages you approve.

answering

Uxen

by rrrfirstchat

Your Telegram, WhatsApp, Instagram, mail and calendar in Claude or ChatGPT. Never sends messages.

answering

MajlisDesk: WhatsApp shared inbox

by majlisdesk

Read and answer your team's WhatsApp and email inbox from Claude or ChatGPT. OAuth sign-in.

answering

WireCat WhatsApp

by wirecat

Your WhatsApp account for agents: read, search and send messages. Sign in with the wa CLI first.

5 078 installs/wk local only

whatsapi.sh

by whatsapi

Send WhatsApp messages from your own numbers, read and answer chats, and send sign-in codes.

answering

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.

135 installs/wk local only

by gaviwhatsapp

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

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 92 of 92 checks got a reply (100.0%), average response time 193 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 193 ms on average, which is faster than 75% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.