Open source · macOS · MCP
WhatsApp, controlled by your AI assistant.
An MCP server that lets Claude, Cursor, or any MCP client search contacts, send messages, and read chats in the native WhatsApp desktop app on macOS. No Meta Business API. No browser automation. One npm install.
macOS 13+ · WhatsApp desktop app · Accessibility permission
What you get
Native macOS, no Web API
Drives the official WhatsApp Catalyst app through accessibility APIs and CGEvent input. No Meta Business API keys, no Selenium, no QR-code scraping.
11 MCP tools, stdio transport
Search contacts, open chats, read messages, send text, navigate the app. Plug into Claude Desktop, Claude Code, Cursor, Windsurf, or any MCP-compatible client.
Single npm install
One public npm command. Postinstall compiles the Swift binary; the MCP server registers via stdio in your client config. No Docker, no daemons.
Local and private
Runs entirely on your Mac. Messages stay in WhatsApp; nothing routes through third-party infrastructure. No WhatsApp password, QR code, or Meta credential is requested.
How it works
01
Install the npm package
One global npm install. The public command is on the install page, and the postinstall script compiles the Swift binary in release mode.
02
Grant Accessibility permission
System Settings, Privacy & Security, Accessibility, enable the host app (Claude Desktop, Terminal, Fazm, etc.).
03
Register the MCP server
Drop a single JSON block into your MCP client's config and restart it. The snippets for Claude Code, Claude Desktop, Cursor, VS Code, and Windsurf are published on the install page.
04
Talk to WhatsApp from your AI
"Send Mom my flight info" — your assistant searches contacts, opens the chat, and drafts the message in WhatsApp.
Common questions
- Is this affiliated with WhatsApp or Meta?
- No. WhatsApp MCP for macOS is an independent open-source project. It is not affiliated with, endorsed by, or sponsored by WhatsApp LLC or Meta Platforms.
- Will this ask for my WhatsApp password or QR code?
- No. The MCP server never asks for your WhatsApp password, QR code, Meta credentials, payment details, or session files. It only drives the official WhatsApp desktop app already signed in on your Mac.
- Does this use the WhatsApp Business API?
- No. It drives the native macOS WhatsApp desktop app through accessibility APIs. There are no Meta API keys, no webhook setup, no opt-in template approval. The tradeoff: it's a personal-account automation tool, not a high-volume broadcast pipeline.
- Is this open source?
- Yes. Full source is on GitHub at github.com/m13v/whatsapp-mcp-macos. The MCP server is written in Swift; the npm package compiles it during postinstall.
- What about WhatsApp Web?
- WhatsApp Web automation breaks on every layout update and requires reverse-engineering the encrypted protocol. This project sidesteps both by driving the official Catalyst app's accessibility tree, which is stable across WhatsApp releases.
- Will my account get banned?
- Risk is materially lower than browser-automation approaches because there is no protocol-level traffic to fingerprint — the OS treats this like a human clicking and typing. That said, automation always carries some risk; don't blast hundreds of unsolicited messages.
Give your AI a real messaging tool.
One install. One config block. Your assistant talks to WhatsApp like you do.