ClaudeMap

WhatsApp MCP

A read-only WhatsApp MCP server: your agent can search and read your own chats and send nothing — free hosted beta or self-host on Cloudflare

MCP Serverswhatsappmcpread-onlyprivacyopen source

whatsapp-mcp is a read-only MCP server over your own WhatsApp message history: link your phone once the way you'd link WhatsApp Web, and from then on any MCP client can search and read your chats — it cannot send anything. Messages are stored encrypted and the code is open source (MIT). Two ways to run it: the hosted beta at whatsapp.finereli.com (free, limited seats — sign in with Google, scan the QR, add the /mcp endpoint to your agent; encrypted at rest, but the operator runs the login service and the README says plainly they could in principle derive your key); or your own copy on Cloudflare Workers (Workers Paid for large history imports, about $5/month; Node 20+; create a KV namespace, set an OWNER_PASSWORD secret, npm run deploy). Sync semantics: read tools top up from WhatsApp when the stored copy is over ten minutes old; there is no background pull because the data key only exists while someone is signed in — an account unused for weeks may need a relink and full resync. 404 stars as of writing.

What it does

  • Read-only by construction: any MCP client can search and read your WhatsApp history; nothing can be sent
  • Hosted free beta at whatsapp.finereli.com — Google sign-in, QR link like WhatsApp Web, add the /mcp endpoint to your agent
  • Self-host on Cloudflare Workers: KV for sign-in tokens, an OWNER_PASSWORD that locks your messages, deploy with npm run deploy
  • Encrypted at rest with a per-account data key derived from a secret only the login service holds — the README states the honest limit that its operator could derive every key
  • Sync on read: every read tool tops up from WhatsApp when the stored copy is over ten minutes old; no background pull, since the key only exists while someone is signed in

When to use it

People who want their agent to answer questions from their own chats — what did I promise someone, when did we agree on X, find that address someone sent — without granting any send capability or pasting chats into prompts.

Getting started

# hosted (free beta): add https://whatsapp.finereli.com/mcp to your MCP client, then scan the QR with your phone

# or self-host (Cloudflare Workers; Workers Paid plan needed for large history imports, ~$5/mo; Node 20+):
git clone https://github.com/finereli/whatsapp-mcp && cd whatsapp-mcp
npm install
npx wrangler kv namespace create OAUTH_KV      # paste the id into wrangler.jsonc
npx wrangler secret put OWNER_PASSWORD         # 12+ chars; this is what locks your messages
npm run deploy

# then open your workers.dev URL: sign in with the password, scan the QR (Settings, Linked Devices),
# and point your MCP client at https://your-url/mcp

Things to know

Read-only, but chat history is sensitive: on the hosted beta the operator runs the login service and says plainly they could derive your key — run your own copy if that is not acceptable (the README's own framing). Large history imports need the Workers Paid plan; on the free plan the first import is fragile by the author's own account. An account unused for weeks may have lost messages WhatsApp was holding for the linked device — relink and resync. 404 stars as of writing (2026-11-06). MIT.

Repository

finereli/whatsapp-mcp

Charted

Related on the map

  • Blitz Strike

    MCP Server

    A penetration-testing methodology delivered as one MCP server: BLITZ maps the attack surface, EAGLE-EYE traces source-to-sink, STRIKE live-verifies every finding before it is reported.

    • mcp-server
    • security
    • pentest
    • methodology
  • Ripwire

    MCP Server

    Red Hat's "ripgrep for AI context" — a C++23 zero-dependency CLI that also speaks MCP.

    • mcp
    • code-context
    • cli
    • red-hat
  • Deja Vu

    MCP Server

    One shared session memory for 25+ coding agents — Claude Code, Codex, and Cursor finally remember the same project.

    • mcp
    • memory
    • cross-agent
    • context