draw.io
Create draw.io diagrams in chat from Mermaid or XML, shown live and interactive. 10,000+ shapes.
WhatsApp for your agent: chats, messages, media, contacts and groups behind MCP tools.
Pick the AI app you use, then copy the settings.
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Wazap for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "wazap": { "command": "npx", "args": [ "-y", "wazap-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Wazap tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
SettingsDeveloperEdit Config
{
"mcpServers": {
"wazap": {
"command": "npx",
"args": [
"-y",
"wazap-mcp"
]
}
}
}Use Wazap and tell me what you can do for me, then show me one thing✓ If Claude says it is using Wazap or shows a Wazap tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
WAZAP_READ_ONLY Refuse every write. The write tools are not registered at all. · default falseWAZAP_DATA_DIR Where wazap keeps credentials, history and media. Defaults to ~/.wazap.Descriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Wazap yet
Wazap runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Wazap
B · Others in Chat & email that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Wazap for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user wazap -- npx -y wazap-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Wazap tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user wazap -- npx -y wazap-mcpYou should see Wazap listed as connected
Use Wazap and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Wazap or shows a Wazap tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
WAZAP_READ_ONLY Refuse every write. The write tools are not registered at all. · default falseWAZAP_DATA_DIR Where wazap keeps credentials, history and media. Defaults to ~/.wazap.Descriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Wazap for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "wazap": { "command": "npx", "args": [ "-y", "wazap-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Wazap tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Use Wazap and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Wazap or shows a Wazap tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
WAZAP_READ_ONLY Refuse every write. The write tools are not registered at all. · default falseWAZAP_DATA_DIR Where wazap keeps credentials, history and media. Defaults to ~/.wazap.Descriptions are as written by the maker.
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Wazap for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "wazap": { "type": "stdio", "command": "npx", "args": [ "-y", "wazap-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Wazap tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Use Wazap and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Wazap or shows a Wazap tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
WAZAP_READ_ONLY Refuse every write. The write tools are not registered at all. · default falseWAZAP_DATA_DIR Where wazap keeps credentials, history and media. Defaults to ~/.wazap.Descriptions are as written by the maker.
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
JSON settings are under “For developers” below
Claude Code
claude mcp add --scope user wazap -- npx -y wazap-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"wazap": {
"command": "npx",
"args": [
"-y",
"wazap-mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"wazap": {
"command": "npx",
"args": [
"-y",
"wazap-mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"wazap": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"wazap-mcp"
]
}
}
}WAZAP_READ_ONLY envWAZAP_DATA_DIR envDescriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 15, 2026
The registry name was verified with the GitHub account razvangirgiz, which owns the repo
Code last changed yesterday
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
No entries on OSV.dev for wazap-mcp@1.7.4
Checks only this package version, not every dependency · checked Nov 15, 2026
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed yesterday, and the latest version (1.7.4) reached the registry 4 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: draw.io, Vexa, emailmd, Kite Discord Bot Builder, e2a — email for AI agents
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Create draw.io diagrams in chat from Mermaid or XML, shown live and interactive. 10,000+ shapes.
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
Build and fix Discord bots from a chat. Kite hosts them 24/7, with no code to deploy.
Authenticated email gateway for AI agents — per-agent inboxes, HITL approval, SPF/DKIM verified.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
╭───────────────╮
│ ▄██▀ │ ██╗ ██╗ █████╗ ███████╗ █████╗ ██████╗ │ ▄██▀ │ ██║ ██║██╔══██╗╚══███╔╝██╔══██╗██╔══██╗ │ ▄███████▀ │ ██║ █╗ ██║███████║ ███╔╝ ███████║██████╔╝ │ ▄██▀ │ ██║███╗██║██╔══██║ ███╔╝ ██╔══██║██╔═══╝ │ ▄█▀ │ ╚███╔███╔╝██║ ██║███████╗██║ ██║██║ ╰─╮╭────────────╯ ╚══╝╚══╝ ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚═╝ ╰╯ WhatsApp for your AI agent.
wazap is an MCP server for your own WhatsApp account. It links as a device, the way WhatsApp Web does, keeps what it sees on your machine, and gives any MCP client — Claude, ChatGPT, Gemini, Cursor, Codex — 23 tools over your chats, messages, media, contacts and groups.
You stop opening WhatsApp to find things and ask instead:
No browser, no business account, no third-party service. There is no wazap cloud: it runs where you run it.
You need Node.js 22.16+ on the 22 line, or 24+, and a phone with WhatsApp.
npx wazap-mcp setup
setup links your account, finds the MCP clients installed on this machine (Claude Code, Claude Desktop, Cursor, Codex, Gemini CLI), writes their config, installs the five skills where the client reads them, and tells you what to restart. Then ask your assistant: *"what did I miss on WhatsApp today?"*
Rather let your agent do it? Paste this into it:
Set up WhatsApp for me: run
npx wazap-mcp setup --agentand follow what it prints.
npx wazap-mcp on its own, in a terminal, starts nothing: it prints where you stand and the next command. When something is off, npx wazap-mcp status is the first thing to run; it prints a fix next to anything broken.
| Client | Fastest path |
|---|---|
| Claude Code | /plugin marketplace add razvangirgiz/wazap, then /plugin install wazap@wazap |
| Claude Desktop | download wazap- .mcpb from Releases and double-click it |
| Cursor | the badge below, then npx wazap-mcp skills install cursor |
| Codex CLI | npx wazap-mcp connect codex, then npx wazap-mcp skills install codex |
| Gemini CLI | npx wazap-mcp connect gemini |
| claude.ai, ChatGPT, other hosted agents | a URL they sign in to with OAuth: see Remote access |
| Anything else | command npx -y wazap-mcp, transport stdio |
The hand-written entry, for any client that takes the usual JSON:
{
"mcpServers": { "whatsapp": { "command": "npx", "args": ["-y", "wazap-mcp"] } } }
Every step setup takes, each file connect writes, and upgrading are in docs/install.md.
Linking is a one-time step. setup does it for you; on its own it is:
npx wazap-mcp login # QR code: Settings → Linked devices → Link a device
npx wazap-mcp login --phone +15550100 # pairing code instead, no camera needed
With --phone, wazap prints an 8-character code. On the phone, go to WhatsApp → Settings → Linked devices → Link a device → Link with phone number instead and type it in. The pairing code works over SSH and on a headless server, where a QR is impractical.
An assistant can link the account itself, too: the link_account tool returns the same code, so a Claude Desktop user never needs a terminal.
Several WhatsApp accounts can live in one wazap (wazap account add , then wazap login --account ); see docs/accounts.md.
What every argument means, and every error code, is in docs/tools.md. The assistant gets all of it by calling learn.
| Tool | Kind | What it does |
|---|---|---|
learn | read | The guide to every tool, id format, workflow and error code. Call it first. |
get_status | read | Connection, sync, linked accounts, how fresh the history is, webhook delivery, versions. |
link_account | read | Link an account from the assistant; returns the 8-character code to type into the phone. |
list_chats | read | Conversations newest-first: all, unread, groups, individual or archived. |
read_messages | read | One chat, paging back into the phone's history; chat_id: "status" reads the stories. |
catch_up | read | "What did I miss?" across every account, in one call and within a token budget. |
search | read | Messages by meaning and by words at once, narrowed by chat, sender or date. |
get_message | read | One message in full: its quote, reactions and who left them, poll votes, delivery and read receipts. |
find_contact | read | Who "mama", a nickname, a group name or a number means, before anything is drafted. |
list_contacts | read | The phone's address book a page at a time: saved name, number, when you last talked. |
get_group_info | read | Participants, admins, group settings, the invite link for an admin. |
get_media | read | A voice note as its transcript, a photo as an image, any file saved to disk; served from the copy kept on arrival first. |
wait_for_messages | read | Block up to 55 s until a message arrives, with a cursor so nothing is missed between calls. |
remember | local | A note, tags or details about a person, kept on this machine. Nothing changes on WhatsApp. |
send_message | write | Draft a message, media, poll, location or forward — and send nothing. send_at drafts it for a later time. |
confirm_send | write | Send that draft, once, after the user has seen the preview and said yes; a draft for later is scheduled. |
edit_message | write | Edit your own message, within WhatsApp's 15-minute window. |
react_to_message | write | Add or remove an emoji reaction. |
delete_message | write | Delete for everyone (your own message, or anyone's in a group you admin), or only on this account. |
manage_chat | write | Preview archive, pin, mute, star, clear, delete, block and undo actions; confirm the preview to apply once. mark_read remains direct. |
manage_group | write | Create, join, rename, add, remove, promote, invite links, join requests, settings, leave. |
scheduled_messages | write | List the scheduled messages (sent, missed, failed too) or cancel one before it goes. |
reminder | local | "Remind me if Ana has not answered in 2 days": set, list or cancel; posted to your webhook when due. |
Scheduled messages and reminders. send_message with send_at ("tomorrow at 9" as 2026-10-12T09:00 in Europe/Bucharest) drafts a message for later; the user's yes to that preview, time included, schedules it, and every send check runs again when it goes. One wazap could not send within 15 minutes of its time is reported as missed, never sent late. reminder keeps "remind me if Ana has not answered in 2 days" and posts it to your webhook when due. Both survive restarts; see Scheduling a message and Reminders.
Two features are off by default and can run entirely on your machine: voice transcription with whisper.cpp (docs/voice.md) and semantic recall, so search matches meaning and not only words (docs/recall.md). Turn them on with wazap config transcribe local and wazap config recall local.
Tools say what is possible; the five Agent Skills in skills/ say how to do the job well.
| Skill | What the agent does |
|---|---|
whatsapp-inbox | Triage: needs you / FYI / noise, plus replies you forgot. Read-only. |
whatsapp-recall | Find an address, an invoice, a photo, a thing someone said. Read-only. |
whatsapp-groups | Catch up on a busy group: decisions, dates, what is asked of you. Read-only. |
whatsapp-send | Find who you mean, draft in the chat's own tone, show it, send on a yes. |
wazap-setup | Diagnose, link or repair the connection. |
setup installs them for Claude Code, Codex and Cursor (npx wazap-mcp skills install does it by hand). Every other client gets the same five as MCP prompts from the server, with nothing to install.
stdio is the default: the client starts npx -y wazap-mcp and talks to it over stdin/stdout. Nothing listens on the network.
HTTP (Streamable HTTP) is for a server that outlives the client, or one another machine reaches:
npx wazap-mcp serve --http # http://127.0.0.1:8766/mcp, health at /healthz
--host/--port (or WAZAP_HOST/WAZAP_PORT) move it. wazap refuses to bind anything but loopback without WAZAP_READ_TOKEN. Clients authenticate with a static bearer token (WAZAP_READ_TOKEN, plus WAZAP_WRITE_TOKEN for the write tools) or with OAuth 2.1, which wazap serves itself. Details in docs/self-host.md.
Two commands keep wazap running and reachable from hosted agents:
npx wazap-mcp service install # a launchd agent (macOS) or systemd user unit (Linux)
npx wazap-mcp expose # a public https URL through Tailscale Funnel or Cloudflare Tunnel
expose prints the URL and a consent password. Give the agent only the URL; it registers itself, and the consent page asks you for the password and whether that agent may only read or also send. See Keep it running.
The service recovers by itself: a dropped link is retried with backoff, a watchdog replaces a socket that went dead across a sleep or stopped answering, and when reconnecting keeps failing wazap exits so launchd or systemd starts it fresh. The linked session is never deleted for any of that; only WhatsApp unlinking the device needs a new link. Set WAZAP_WEBHOOK_EVENTS to include alert to be told when the link has been down for 5 minutes, when it is back, and when it needs linking again (Link alerts); get_status shows the same under link.
On a server of your own, the session never leaves it. With Docker (images for amd64 and arm64 at ghcr.io/razvangirgiz/wazap):
mkdir wazap && cd wazap
curl -fsSLO https://raw.githubusercontent.com/razvangirgiz/wazap/main/docker-compose.yml printf 'WAZAP_READ_TOKEN=%s\nWAZAP_WRITE_TOKEN=%s\n' $(openssl rand -hex 32) $(openssl rand -hex 32) > .env docker compose run --rm wazap login --phone +15550100 # once; the session lands in the volume docker compose up -d curl -s http://127.0.0.1:8766/healthz
The container publishes port 8766 on loopback only; put TLS in front (deploy/Caddyfile is two lines). A systemd unit is in deploy/wazap.service. Both setups, reverse-proxy trust and the OAuth server are in docs/self-host.md. Calling wazap from your own product, and receiving signed webhooks for incoming messages, is in docs/api-and-webhooks.md.
Every setting is optional. They are environment variables, read from the process or from `~/