wacli.me alpha

Your WhatsApp,
as an MCP server.

Link your account once and get an endpoint any MCP client can talk to — Claude, ChatGPT, your editor, your own agent. Ask for a summary of a thread, search two years of history, draft the reply. The gateway is open source: host it yourself, or let us host it for you.

MCP https://wacli.me/mcp

Streamable HTTP transport · bearer token per account · read-only until you say otherwise.

See what it can do Read the source

How it works

Link your account

Scan one QR code, the way you link WhatsApp Web. It is a linked device, not a takeover — unlink it from your phone at any time.

Get your endpoint

You receive a URL and a bearer token. The token maps to your own isolated message store; nobody else's tools can reach it.

Point a client at it

Paste both into any MCP client. Chats, search and history show up as tools within seconds.

Connecting

# Claude Code
claude mcp add --transport http whatsapp https://wacli.me/mcp \
  --header "Authorization: Bearer <your-token>"

# any client that speaks MCP over HTTP
{
  "whatsapp": {
    "type": "http",
    "url": "https://wacli.me/mcp",
    "headers": { "Authorization": "Bearer <your-token>" }
  }
}

Then just talk to your assistant: “What did the plumber say about the appointment?”

Tools

Thirteen read-only tools, four behind a write switch that stays off until you ask for it.

search_messagesFull-text search across your synced history.
list_messagesMessages of one chat, with time and sender filters.
get_message_contextWhat was said around a message — the answer to “answering what?”
list_chats Chats by recent activity, filterable by name or unread.
list_groupsGroups, their subjects, participants and admins.
get_mediaFetch one message's image, on demand, never in bulk.
list_callsWho called, when, answered or missed.
history_coverageHow far back your history actually reaches.
send_messageSend text — also to a number you have never written to.
check_numbers_on_whatsappIs that number on WhatsApp at all?
Full tool reference — all 17

Pricing

Free while the alpha runs — no payment flow, no card, no bill. Self-hosting is free without limits, permanently. A paid tier for several accounts in one workspace is planned; it is not priced yet, and pricing comes with 30 days' notice.

See the plans

The project

Open

Built on open source

The heavy lifting is done by wacli — an independent MIT-licensed WhatsApp CLI with 2,745 stars and 343 forks on GitHub, actively developed since December 2025. This service is a hosted gateway in front of it, run by different people; the gateway is MIT too and publishes with the public beta.

Public

Changes in the open

Every release and every incident is dated in the changelog. What comes next, and what will never be built, is on the roadmap.

Written down

Decisions, not slogans

Why sending is off, how accounts are isolated, why a tool server beats a chatbot — the reasoning is in the build notes.

Why you can check us instead of trusting us

Open source. The gateway is MIT-licensed and builds on the open-source wacli CLI. Read every line that touches your messages.

Self-hostable. Same code, your hardware, no account here. Hosting is a convenience, never a lock-in.

Read-only by default. Sending is a separate switch, off until you flip it.

No third parties. Your messages are not sent to any analytics, ad or model provider by us — only to the client you connect.

Read the docs Questions people ask Current status