Whatsapp

me.wacliPublished by wacli.meOfficial publisherv0.2.1Updated Oct 25, 2026

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

VerifiedStreamable HTTPWeb executableKnowledge & MemoryCommunication & Collaboration

Overview

AI-generated overview

A hosted MCP gateway that links your own WhatsApp account so any MCP client can read, search and optionally send messages.

What you can do
Read messages from a linked WhatsApp account's synced store and search across them, with reads run in read-only mode so tool calls cannot change the store. Send messages only when the account owner has explicitly enabled write access for that tenant. Connect over Streamable HTTP at the MCP endpoint using a bearer token, with OAuth 2.1 discovery so clients can fetch their own credentials. Link an account once by scanning a QR code like WhatsApp Web, then use it from any MCP client without running anything locally.
When to use it
Useful when you want an assistant to look through your own WhatsApp history or draft and send replies from an MCP client, without running a local bridge. Suited to personal or small-team use where one linked account per token is acceptable.
Requirements
A remote endpoint at wacli.me over Streamable HTTP with OAuth authentication required. A WhatsApp account to link by scanning a QR code, and a bearer token issued at the connect page. Self-hosting needs Node.js, the bundled wacli binary, and a sync daemon to backfill history.
Before you install
The QR link is a linked device: whoever holds the store directory or tenant token can read that account's messages, so treat both as credentials. Sending is a write action and is only registered when allowSend is enabled; leave it off unless the owner asked for it. The service is a public alpha on a single host. When self-hosting, bind to loopback and use a tunnel rather than exposing the port.

Installation

In SourceWeft

  1. Open Whatsapp in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/me.wacli%2Fwhatsapp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "whatsapp": {
      "type": "http",
      "url": "https://wacli.me/mcp"
    }
  }
}

README

wacli.me

Hosted MCP gateway in front of the wacli WhatsApp CLI.

The idea: someone links their WhatsApp account once (QR, like WhatsApp Web) and gets a URL plus a bearer token. Any MCP client can then read, search — and optionally send — without running anything locally.

Status: public alpha. Single host, single process. Live at https://wacli.me.

MIT licensed. Self-hosting is a first-class path — see "Running" below.

Layout

server/      Node MCP server (Streamable HTTP) + static file servingsite/        website sources (pages + layout + assets)web/         generated site, built from site/ by scripts/build.mjs — never editconfig/      tenants.json (gitignored) — token -> store mappingbin/wacli    pinned wacli binary, isolated from any system installstores/      one wacli store directory per tenant (gitignored)scripts/     start/stop/tunnel helpers

Endpoints

PathPurpose
/landing page
/mcpMCP over Streamable HTTP, Authorization: Bearer …
/healthzliveness + tenant count
/connectself-service linking: live QR, issues a token
/.well-known/oauth-*OAuth 2.1 discovery — clients fetch their own credentials

Tenants

config/tenants.json:

json
{  "tenants": [    { "id": "demo", "token": "<32 random bytes, hex>", "store": "/Users/<user>/wacli-me/stores/demo", "allowSend": false }  ]}

The file is re-read every 5 seconds — adding a tenant needs no restart. A token maps to exactly one store directory; tools are constructed per request against that store, so two tenants cannot see each other's data. allowSend is what registers the send_message tool at all; leave it false unless the account owner explicitly asked for write access.

Generate a token with openssl rand -hex 32.

Running

bash
npm install --prefix servernode scripts/build.mjs                        # site/ -> web/PORT=8787 HOST=127.0.0.1 node server/server.mjs

Environment:

VariableDefaultMeaning
PORT8787listen port
HOST127.0.0.1bind address — keep loopback, expose via tunnel
WACLI_BIN./bin/wacliwacli binary
WACLI_ME_TENANTS./config/tenants.jsontenant file

Linking an account

bash
bin/wacli --store stores/<tenant> auth        # prints a QR, scan it on the phonebin/wacli --store stores/<tenant> sync        # backfill history (long-running; run as a daemon)

Without a sync daemon the store only holds what was fetched during the last run.

Security notes

  • Bind to loopback and publish through a tunnel; never expose the port directly.
  • Every MCP request needs a valid bearer token; tokens are compared in constant time.
  • Reads run wacli with --read-only, so a compromised tool call cannot mutate the store.
  • The QR link is a linked device. Whoever holds the store can read that account's messages — treat store directories and tenant tokens as credentials.

License

MIT, see LICENSE. site/assets/qrcode.min.js is Kazuhiko Arase's qrcode-generator, vendored unchanged (MIT). wacli itself is a separate MIT project — this repository only drives it.

Linking an account uses an unofficial WhatsApp client. That is against WhatsApp's terms of service, and Meta may block a number for it. Run it on accounts you own, and tell your users the same.

Source: README.md at commit 0bcd107

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v0.2.1LatestSep 19, 2026
  2. v0.2.0Sep 18, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts