WhatsApp MCP server
io.github.mcp-dir/whatsapp-mcpmcp-dirstreamable-httpv0.1.0Scanned
Connect a personal/Business WhatsApp account via QR pairing (multi-device, like WhatsApp Web). Send
47 tools: 3 can delete or cancel things, 7 do something that can't be undone, 22 change things and 15 only read.
- Reads private data · 7
- Reads text others write · 8
- Can send data out · 9
- 6 findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here can delete or cancel things and 7 do something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the WhatsApp MCP server can do
The WhatsApp MCP server is published by the GitHub account mcp-dir. It has 47 tools. It can delete or cancel things (3 tools: whatsapp_group_participants_remove, whatsapp_message_delete and whatsapp_chat_archive), do things that cannot be undone, such as sending, paying or publishing (whatsapp_send_text, whatsapp_send_media, whatsapp_poll_create, whatsapp_poll_vote and 3 more) and create or change data (22 tools: whatsapp_sync, whatsapp_messages_write, whatsapp_group_participants_add, whatsapp_group_participants_promote and 18 more). 15 tools only read.
7 tools read private data (whatsapp_chats, whatsapp_messages, whatsapp_contacts_list and 4 more); 8 tools bring in text other people can write (whatsapp_chats, whatsapp_messages, whatsapp_chat_metadata and 5 more); 9 tools can send data out of your system (whatsapp_send_text, whatsapp_send_media, whatsapp_messages_write and 6 more). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 6 findings (annotation-conflict and credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 8, 2026, version 0.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
47 tools
Deletes or cancels 3Claude Code: deny
whatsapp_chat_archiveChange a chat's state.1 finding
Why it is in this group
- The name "whatsapp_chat_archive" says "archive": a word for removing or ending something.
- The server marks it not destructive (destructiveHint: false), but an annotation never lowers a class.
Findings
- Warn
The server marks "whatsapp_chat_archive" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "whatsapp_chat_archive" says "archive": a word for removing or ending something.
Description, as the server wrote it Change a chat's state. action: archive/unarchive, pin/unpin, mute/unmute. Requires chat_jid. [Flattened action: archive]
Annotations the server declares
- title: whatsapp_chat_archive
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
whatsapp_group_participants_removeManage participants of a WhatsApp group (the connected account must be a group admin).1 finding
Why it is in this group
- The name "whatsapp_group_participants_remove" says "remove": a word for removing or ending something.
- The server marks it not destructive (destructiveHint: false), but an annotation never lowers a class.
Findings
- Warn
The server marks "whatsapp_group_participants_remove" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "whatsapp_group_participants_remove" says "remove": a word for removing or ending something.
Description, as the server wrote it Manage participants of a WhatsApp group (the connected account must be a group admin). action: 'remove' kicks members, 'promote' makes them admin, 'demote' removes admin, 'add' invites. Pass 1–50 phone numbers (+E164) or JIDs in `users`. [Flattened action: remove]
Annotations the server declares
- title: whatsapp_group_participants_remove
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
whatsapp_message_deleteManage a message you can act on.1 finding
Why it is in this group
- The name "whatsapp_message_delete" says "delete": a word for removing or ending something.
- The input addresses people (input.to): what it sends cannot be taken back.
- The server marks it not destructive (destructiveHint: false), but an annotation never lowers a class.
Findings
- Warn
The server marks "whatsapp_message_delete" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "whatsapp_message_delete" says "delete": a word for removing or ending something.
Description, as the server wrote it Manage a message you can act on. Actions: - delete: { chat_jid, message_id, for_everyone? (default true) } — delete for everyone (your msg) or just for you - forward: { chat_jid, message_id, to } — forward a stored message to another chat - edit: { chat_jid, message_id, text } — edit one of your recent text messages [Flattened action: delete] Bulk support: accepts message_ids for batched execution.
Annotations the server declares
- title: whatsapp_message_delete
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Can't be undone 7Claude Code: ask
whatsapp_group_manage_invite_linkGroup lifecycle/admin (the connected account must be a group admin for most actions).Can send data outNo findings
Why it is in this group
- The name "whatsapp_group_manage_invite_link" says "invite": a word for sending, and what is sent cannot be taken back.
What it can reach
- outboundThe name "whatsapp_group_manage_invite_link" says "invite": it sends or publishes something to other people.
Description, as the server wrote it Group lifecycle/admin (the connected account must be a group admin for most actions). Actions: - create: { name, participants[] } - leave: { group_jid } - update: { group_jid, name?, description? } - invite_link: { group_jid, link_action: 'get'|'revoke' } - join: { invite } (invite code or full invite link) - requests: { group_jid, req_action: 'list'|'approve'|'reject', users? } [Flattened action: invite_link]
Annotations the server declares
- title: whatsapp_group_manage_invite_link
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
whatsapp_message_editManage a message you can act on.Can send data outNo findings
Why it is in this group
- The name "whatsapp_message_edit" says "edit": a word for a change.
- The input addresses people (input.to): what it sends cannot be taken back.
What it can reach
- outboundThe name "whatsapp_message_edit" says "edit" and "message": it writes something other people read.
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Description, as the server wrote it Manage a message you can act on. Actions: - delete: { chat_jid, message_id, for_everyone? (default true) } — delete for everyone (your msg) or just for you - forward: { chat_jid, message_id, to } — forward a stored message to another chat - edit: { chat_jid, message_id, text } — edit one of your recent text messages [Flattened action: edit] Bulk support: accepts message_ids for batched execution.
Annotations the server declares
- title: whatsapp_message_edit
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
whatsapp_message_forwardManage a message you can act on.Can send data outNo findings
Why it is in this group
- The input addresses people (input.to): what it sends cannot be taken back.
What it can reach
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Description, as the server wrote it Manage a message you can act on. Actions: - delete: { chat_jid, message_id, for_everyone? (default true) } — delete for everyone (your msg) or just for you - forward: { chat_jid, message_id, to } — forward a stored message to another chat - edit: { chat_jid, message_id, text } — edit one of your recent text messages [Flattened action: forward] Bulk support: accepts message_ids for batched execution.
Annotations the server declares
- title: whatsapp_message_forward
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
whatsapp_poll_createSend a poll or vote on one.Can send data outNo findings
Why it is in this group
- The name "whatsapp_poll_create" says "create": a word for a change.
- The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
- The input addresses people (input.to): what it sends cannot be taken back.
What it can reach
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Description, as the server wrote it Send a poll or vote on one. Actions: - create: { to, name, options[] (2–12), selectable_count? } - vote: { chat_jid, message_id, options[] (the option texts to select) } [Flattened action: create] Bulk support: accepts message_ids for batched execution.
Annotations the server declares
- title: whatsapp_poll_create
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
whatsapp_poll_voteSend a poll or vote on one.Can send data outNo findings
Why it is in this group
- The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
- The input addresses people (input.to): what it sends cannot be taken back.
What it can reach
- outboundThe description's first verb is "send": it sends or publishes something to other people.
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Description, as the server wrote it Send a poll or vote on one. Actions: - create: { to, name, options[] (2–12), selectable_count? } - vote: { chat_jid, message_id, options[] (the option texts to select) } [Flattened action: vote] Bulk support: accepts message_ids for batched execution.
Annotations the server declares
- title: whatsapp_poll_vote
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
whatsapp_send_mediaSend a WhatsApp message (text or media).Can send data outNo findings
Why it is in this group
- The name "whatsapp_send_media" says "send": a word for sending, and what is sent cannot be taken back.
- The input addresses people (input.to): what it sends cannot be taken back.
What it can reach
- outboundThe name "whatsapp_send_media" says "send": it sends or publishes something to other people.
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Description, as the server wrote it Send a WhatsApp message (text or media). Actions: - text: { to, text, reply_to? } - media: { to, type ('image'|'video'|'audio'|'document'|'sticker'), media_url | media_base64, caption?, filename?, mimetype? } `to` accepts either a JID ('5511999999999@s.whatsapp.net', '<id>@g.us') or a plain phone (digits, country code included). For groups always use the '<id>@g.us' JID — get it from whatsapp_groups. Result: `sent:true` + `delivery:"accepted_by_server"` means WhatsApp's server accepted the message (it has an id). It is NOT a read/delivery receipt from the recipients' phones. If the message did not go out, the call fails with the reason. [Flattened action: media]
Annotations the server declares
- title: whatsapp_send_media
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
whatsapp_send_textSend a WhatsApp message (text or media).Can send data outNo findings
Why it is in this group
- The name "whatsapp_send_text" says "send": a word for sending, and what is sent cannot be taken back.
- The input addresses people (input.to): what it sends cannot be taken back.
What it can reach
- outboundThe name "whatsapp_send_text" says "send": it sends or publishes something to other people.
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Description, as the server wrote it Send a WhatsApp message (text or media). Actions: - text: { to, text, reply_to? } - media: { to, type ('image'|'video'|'audio'|'document'|'sticker'), media_url | media_base64, caption?, filename?, mimetype? } `to` accepts either a JID ('5511999999999@s.whatsapp.net', '<id>@g.us') or a plain phone (digits, country code included). For groups always use the '<id>@g.us' JID — get it from whatsapp_groups. Result: `sent:true` + `delivery:"accepted_by_server"` means WhatsApp's server accepted the message (it has an id). It is NOT a read/delivery receipt from the recipients' phones. If the message did not go out, the call fails with the reason. [Flattened action: text]
Annotations the server declares
- title: whatsapp_send_text
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Changes things 22Claude Code: ask
authenticateMCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it MCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes, or with no args to get the link.
Annotations the server declares
- title: Authenticate
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
marketplaceThe official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them.Reads text others write1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The description mentions "credential".
What this check looks forMatched text
description: "...ating the tool list. If the MCP needs a credential/login, invoke returns a connect link; i..."
Description, as the server wrote it The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/<slug> link that opens without login.
Annotations the server declares
- title: Marketplace
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
report_bugReport a bug, missing feature, or send feedback.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.
Annotations the server declares
- title: Report Bug
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
whatsapp_chat_muteChange a chat's state.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Change a chat's state. action: archive/unarchive, pin/unpin, mute/unmute. Requires chat_jid. [Flattened action: mute]
Annotations the server declares
- title: whatsapp_chat_mute
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
whatsapp_chat_pinChange a chat's state.No findings
Why it is in this group
- The name "whatsapp_chat_pin" says "pin": a word for a change.
Description, as the server wrote it Change a chat's state. action: archive/unarchive, pin/unpin, mute/unmute. Requires chat_jid. [Flattened action: pin]
Annotations the server declares
- title: whatsapp_chat_pin
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
whatsapp_chat_unarchiveChange a chat's state.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Change a chat's state. action: archive/unarchive, pin/unpin, mute/unmute. Requires chat_jid. [Flattened action: unarchive]
Annotations the server declares
- title: whatsapp_chat_unarchive
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
whatsapp_chat_unmuteChange a chat's state.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Change a chat's state. action: archive/unarchive, pin/unpin, mute/unmute. Requires chat_jid. [Flattened action: unmute]
Annotations the server declares
- title: whatsapp_chat_unmute
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
whatsapp_chat_unpinChange a chat's state.No findings
Why it is in this group
- The name "whatsapp_chat_unpin" says "unpin": a word for a change.
Description, as the server wrote it Change a chat's state. action: archive/unarchive, pin/unpin, mute/unmute. Requires chat_jid. [Flattened action: unpin]
Annotations the server declares
- title: whatsapp_chat_unpin
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
whatsapp_config_setChange an editable-after-connect setting on a connected number WITHOUT re-pairing.No findings
Why it is in this group
- The name "whatsapp_config_set" says "set": a word for a change.
Description, as the server wrote it Change an editable-after-connect setting on a connected number WITHOUT re-pairing. Today the only field is `proxy_url` — the SOCKS5/HTTPS proxy WhatsApp connects through (recommended to avoid IP bans). Owner/admin or the connection owner. - `account`: which number (id/wa_jid, phone, or label; omit if only one is connected). - `values`: e.g. { "proxy_url": "socks5://user:pass@host:port" }. An empty string CLEARS the field (e.g. { "proxy_url": "" } connects with no proxy); omit the key to keep the current value. The new value applies on the next (re)connection; the live session cache is invalidated so the next tool call uses it.
Annotations the server declares
- title: whatsapp_config_set
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
whatsapp_group_manage_createGroup lifecycle/admin (the connected account must be a group admin for most actions).No findings
Why it is in this group
- The name "whatsapp_group_manage_create" says "create": a word for a change.
Description, as the server wrote it Group lifecycle/admin (the connected account must be a group admin for most actions). Actions: - create: { name, participants[] } - leave: { group_jid } - update: { group_jid, name?, description? } - invite_link: { group_jid, link_action: 'get'|'revoke' } - join: { invite } (invite code or full invite link) - requests: { group_jid, req_action: 'list'|'approve'|'reject', users? } [Flattened action: create]
Annotations the server declares
- title: whatsapp_group_manage_create
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
whatsapp_group_manage_joinGroup lifecycle/admin (the connected account must be a group admin for most actions).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Group lifecycle/admin (the connected account must be a group admin for most actions). Actions: - create: { name, participants[] } - leave: { group_jid } - update: { group_jid, name?, description? } - invite_link: { group_jid, link_action: 'get'|'revoke' } - join: { invite } (invite code or full invite link) - requests: { group_jid, req_action: 'list'|'approve'|'reject', users? } [Flattened action: join]
Annotations the server declares
- title: whatsapp_group_manage_join
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
whatsapp_group_manage_leaveGroup lifecycle/admin (the connected account must be a group admin for most actions).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Group lifecycle/admin (the connected account must be a group admin for most actions). Actions: - create: { name, participants[] } - leave: { group_jid } - update: { group_jid, name?, description? } - invite_link: { group_jid, link_action: 'get'|'revoke' } - join: { invite } (invite code or full invite link) - requests: { group_jid, req_action: 'list'|'approve'|'reject', users? } [Flattened action: leave]
Annotations the server declares
- title: whatsapp_group_manage_leave
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
whatsapp_group_manage_requestsGroup lifecycle/admin (the connected account must be a group admin for most actions).No findings
Why it is in this group
- The name "whatsapp_group_manage_requests" says "request": a word for a change.
Description, as the server wrote it Group lifecycle/admin (the connected account must be a group admin for most actions). Actions: - create: { name, participants[] } - leave: { group_jid } - update: { group_jid, name?, description? } - invite_link: { group_jid, link_action: 'get'|'revoke' } - join: { invite } (invite code or full invite link) - requests: { group_jid, req_action: 'list'|'approve'|'reject', users? } [Flattened action: requests]
Annotations the server declares
- title: whatsapp_group_manage_requests
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
whatsapp_group_manage_updateGroup lifecycle/admin (the connected account must be a group admin for most actions).No findings
Why it is in this group
- The name "whatsapp_group_manage_update" says "update": a word for a change.
Description, as the server wrote it Group lifecycle/admin (the connected account must be a group admin for most actions). Actions: - create: { name, participants[] } - leave: { group_jid } - update: { group_jid, name?, description? } - invite_link: { group_jid, link_action: 'get'|'revoke' } - join: { invite } (invite code or full invite link) - requests: { group_jid, req_action: 'list'|'approve'|'reject', users? } [Flattened action: update]
Annotations the server declares
- title: whatsapp_group_manage_update
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
whatsapp_group_participants_addManage participants of a WhatsApp group (the connected account must be a group admin).No findings
Why it is in this group
- The name "whatsapp_group_participants_add" says "add": a word for a change.
Description, as the server wrote it Manage participants of a WhatsApp group (the connected account must be a group admin). action: 'remove' kicks members, 'promote' makes them admin, 'demote' removes admin, 'add' invites. Pass 1–50 phone numbers (+E164) or JIDs in `users`. [Flattened action: add]
Annotations the server declares
- title: whatsapp_group_participants_add
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
whatsapp_group_participants_demoteManage participants of a WhatsApp group (the connected account must be a group admin).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Manage participants of a WhatsApp group (the connected account must be a group admin). action: 'remove' kicks members, 'promote' makes them admin, 'demote' removes admin, 'add' invites. Pass 1–50 phone numbers (+E164) or JIDs in `users`. [Flattened action: demote]
Annotations the server declares
- title: whatsapp_group_participants_demote
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
whatsapp_group_participants_promoteManage participants of a WhatsApp group (the connected account must be a group admin).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Manage participants of a WhatsApp group (the connected account must be a group admin). action: 'remove' kicks members, 'promote' makes them admin, 'demote' removes admin, 'add' invites. Pass 1–50 phone numbers (+E164) or JIDs in `users`. [Flattened action: promote]
Annotations the server declares
- title: whatsapp_group_participants_promote
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
whatsapp_history_backfillRequest OLDER messages for a chat from your phone (on-demand history sync), extending what whatsapp_messages can read.No findings
Why it is in this group
- The description's first verb is "request": a word for a change.
Description, as the server wrote it Request OLDER messages for a chat from your phone (on-demand history sync), extending what whatsapp_messages can read. Returns { status, messages_added }: - "done"/"partial": it pulled messages_added new messages — read them via whatsapp_messages (paginate with `before`). "partial" means WhatsApp stopped early; wait and retry for more. - "cooldown": you requested this chat <60s ago (retry_after_s tells you when). WhatsApp THROTTLES back-to-back requests — DO NOT retry in a loop; wait, then try once. - "timeout": the phone didn't deliver in time (offline or throttled) — already-synced history is still readable; retry later. BEST-EFFORT (gated by WhatsApp): one call usually pulls a batch (~50–70 msgs); pulling much deeper repeatedly often won't work. Connects live, may take up to ~1 minute. The initial sync already loaded deep history for most chats — check whatsapp_history_coverage first; only backfill when a chat's oldest_ts isn't far enough back.
Annotations the server declares
- title: whatsapp_history_backfill
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
whatsapp_messages_writeMark messages as read in a chat.Can send data outNo findings
Why it is in this group
- The name "whatsapp_messages_write" says "write": a word for a change.
What it can reach
- outboundThe name "whatsapp_messages_write" says "write" and "message": it writes something other people read.
Description, as the server wrote it Mark messages as read in a chat. Requires chat_jid. Optional message_id (marks up to this message; omit to mark all unread). Bulk support: accepts message_ids for batched execution.
Annotations the server declares
- title: whatsapp_messages_write
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
whatsapp_reactReact to a message with an emoji (or remove your reaction by passing an empty emoji).No findings
Why it is in this group
- The name "whatsapp_react" says "react": a word for a change.
Description, as the server wrote it React to a message with an emoji (or remove your reaction by passing an empty emoji). Requires chat_jid + message_id. Bulk support: accepts message_ids for batched execution.
Annotations the server declares
- title: whatsapp_react
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
whatsapp_syncRefresh this account's local data from WhatsApp — pulls recent messages and refreshes the groups/contacts lists into the local store.1 finding
Why it is in this group
- The name "whatsapp_sync" says "sync": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "whatsapp_sync" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "whatsapp_sync" says "sync": a word for a change.
Description, as the server wrote it Refresh this account's local data from WhatsApp — pulls recent messages and refreshes the groups/contacts lists into the local store. Call it BEFORE reading (chats/groups/messages/contacts/search) when results look stale or empty (e.g. right after connecting, or an account that hasn't synced recently). Connects live, so it may take ~20–60s. Returns { messages_stored }.
Annotations the server declares
- title: whatsapp_sync
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
whatsapp_webhook_setSet (or remove) this WhatsApp install's outbound webhook.Can send data outNo findings
Why it is in this group
- The name "whatsapp_webhook_set" says "set": a word for a change.
What it can reach
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Set (or remove) this WhatsApp install's outbound webhook. Owner/admin only. - To set: pass `url` (https only, not localhost). `events` is the list of subscribed events ("permissions") — e.g. ["whatsapp.message"], or ["whatsapp.*"] for every WhatsApp event, or [] / omit for ALL events. See available_events from whatsapp_webhook_get. `include_result` (default true) controls whether the tool result is included in tool.call payloads. `secret` is optional (reserved). - Subscribing to any whatsapp.* event makes the daemon hold a live connection per number and forward inbound messages to your URL. - To remove the webhook: pass `remove: true` (or an empty url).
Annotations the server declares
- title: whatsapp_webhook_set
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Only reads 15Show 15 read-only tools
connectReturns connection status and URLs.1 finding
Why it is in this group
- The description's first verb is "return": a word for reading.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...nticated:true and empty pending[]. When credentials are missing, returns connect_url for th..."
Description, as the server wrote it Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.
Annotations the server declares
- title: Connection Status
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
show_versionShow the current MCP platform and adapter versions.No findings
Why it is in this group
- The name "show_version" says "show": a word for reading.
Description, as the server wrote it Show the current MCP platform and adapter versions.
Annotations the server declares
- title: Show Version
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
toolkit_infoReturns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.No findings
Why it is in this group
- The description's first verb is "return": a word for reading.
Description, as the server wrote it Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.
Annotations the server declares
- title: Toolkit Info
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
whatsapp_chat_metadataGet metadata for a single chat (subject/name, archived/pinned/muted state, unread count, timestamps).Reads private dataReads text others writeNo findings
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- private-dataThe name "whatsapp_chat_metadata" says "chat": it reads messages.
- private-dataThe description's first sentence says "get" and "chat": it reads messages.
- untrusted-inputThe name "whatsapp_chat_metadata" says "chat": it reads messages, which other people can write.
- untrusted-inputThe description's first sentence says "get" and "chat": it reads messages, which other people can write.
Description, as the server wrote it Get metadata for a single chat (subject/name, archived/pinned/muted state, unread count, timestamps). Requires chat_jid.
Annotations the server declares
- title: whatsapp_chat_metadata
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
whatsapp_chatsList WhatsApp chats (individual + group).Reads private dataReads text others writeNo findings
Why it is in this group
- The description's first verb is "list": a word for reading.
What it can reach
- private-dataThe name "whatsapp_chats" says "chat": it reads messages.
- private-dataThe description's first sentence says "list" and "chat": it reads messages.
- untrusted-inputThe name "whatsapp_chats" says "chat": it reads messages, which other people can write.
- untrusted-inputThe description's first sentence says "list" and "chat": it reads messages, which other people can write.
Description, as the server wrote it List WhatsApp chats (individual + group). Sorted by most recent activity.
Annotations the server declares
- title: whatsapp_chats
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
whatsapp_config_getShow this install's editable-after-connect settings per connected number — currently the proxy (proxy_url): whether it's set and a masked preview (the raw value is never returned).Reads text others writeNo findings
Why it is in this group
- The name "whatsapp_config_get" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "show" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it Show this install's editable-after-connect settings per connected number — currently the proxy (proxy_url): whether it's set and a masked preview (the raw value is never returned). Owner/admin or the connection owner.
Annotations the server declares
- title: whatsapp_config_get
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
whatsapp_contacts_getRead WhatsApp contacts.Reads private dataNo findings
Why it is in this group
- The name "whatsapp_contacts_get" says "get": a word for reading.
What it can reach
- private-dataThe name "whatsapp_contacts_get" says "get" and "contact": it reads contacts.
- private-dataThe description's first sentence says "read" and "contact": it reads contacts.
Description, as the server wrote it Read WhatsApp contacts. Actions: - list: search across contacts (query optional — substring on name/phone). Default limit 50. - get: full contact info by JID. [Flattened action: get]
Annotations the server declares
- title: whatsapp_contacts_get
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
whatsapp_contacts_listRead WhatsApp contacts.Reads private dataNo findings
Why it is in this group
- The name "whatsapp_contacts_list" says "list": a word for reading.
What it can reach
- private-dataThe name "whatsapp_contacts_list" says "list" and "contact": it reads contacts.
- private-dataThe description's first sentence says "read" and "contact": it reads contacts.
Description, as the server wrote it Read WhatsApp contacts. Actions: - list: search across contacts (query optional — substring on name/phone). Default limit 50. - get: full contact info by JID. [Flattened action: list]
Annotations the server declares
- title: whatsapp_contacts_list
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
whatsapp_group_membersList the members of a WhatsApp group (live).No findings
Why it is in this group
- The description's first verb is "list": a word for reading.
Description, as the server wrote it List the members of a WhatsApp group (live). Returns each participant's JID, phone, and admin/super-admin flag. Requires group_jid (…@g.us, from whatsapp_groups).
Annotations the server declares
- title: whatsapp_group_members
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
whatsapp_groupsList WhatsApp groups the account belongs to — subject, jid, participants count, owner.No findings
Why it is in this group
- The description's first verb is "list": a word for reading.
Description, as the server wrote it List WhatsApp groups the account belongs to — subject, jid, participants count, owner.
Annotations the server declares
- title: whatsapp_groups
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
whatsapp_history_coverageShow how far back the LOCAL message archive reaches per chat (oldest_ts, newest_ts, message_count, status).Reads private dataReads text others writeNo findings
Why it is in this group
- The description's first verb is "show": a word for reading.
What it can reach
- private-dataThe description's first sentence says "show" and "message": it reads messages.
- untrusted-inputThe description's first sentence says "show" and "message": it reads messages, which other people can write.
Description, as the server wrote it Show how far back the LOCAL message archive reaches per chat (oldest_ts, newest_ts, message_count, status). Use it to find pagination boundaries for whatsapp_messages and to decide whether to pull more with whatsapp_history_backfill. Optional query (filter by name/JID), kind, limit, or a single chat_jid.
Annotations the server declares
- title: whatsapp_history_coverage
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
whatsapp_list_accountsList WhatsApp accounts paired to this install — wa_jid, phone, label, proxy on/off, status.No findings
Why it is in this group
- The name "whatsapp_list_accounts" says "list": a word for reading.
Description, as the server wrote it List WhatsApp accounts paired to this install — wa_jid, phone, label, proxy on/off, status.
Annotations the server declares
- title: whatsapp_list_accounts
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
whatsapp_messagesList messages in a chat from LOCAL history.Reads private dataReads text others writeNo findings
Why it is in this group
- The description's first verb is "list": a word for reading.
What it can reach
- private-dataThe name "whatsapp_messages" says "message": it reads messages.
- private-dataThe description's first sentence says "list" and "message": it reads messages.
- untrusted-inputThe name "whatsapp_messages" says "message": it reads messages, which other people can write.
- untrusted-inputThe description's first sentence says "list" and "message": it reads messages, which other people can write.
Description, as the server wrote it List messages in a chat from LOCAL history. Requires chat_jid (from whatsapp_chats). Paginate backwards by passing the oldest message's timestamp as `before` (ISO 8601); `after` pages forward; `order` sorts. NOTE: only messages already synced locally are returned — to see how far back the archive goes use whatsapp_history_coverage, and to pull OLDER messages from your phone use whatsapp_history_backfill.
Annotations the server declares
- title: whatsapp_messages
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
whatsapp_searchFull-text search across all stored messages (SQLite FTS5).Reads private dataReads text others writeNo findings
Why it is in this group
- The name "whatsapp_search" says "search": a word for reading.
What it can reach
- private-dataThe description's first sentence says "message": it reads messages.
- untrusted-inputThe description's first sentence says "message": it reads messages, which other people can write.
Description, as the server wrote it Full-text search across all stored messages (SQLite FTS5). Optional chat_jid to scope. Returns matches with context.
Annotations the server declares
- title: whatsapp_search
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
whatsapp_webhook_getShow this WhatsApp install's outbound webhook: the current URL, the subscribed events (empty = all), include_result, and the catalog of subscribable events (available_events — e.g.Reads text others writeNo findings
Why it is in this group
- The name "whatsapp_webhook_get" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "show" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it Show this WhatsApp install's outbound webhook: the current URL, the subscribed events (empty = all), include_result, and the catalog of subscribable events (available_events — e.g. whatsapp.message, whatsapp.reaction, and the whatsapp.* wildcard). Owner/admin only.
Annotations the server declares
- title: whatsapp_webhook_get
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
504 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 7 private-data tools breaks every one.
- Reads private data7
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write8
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out9
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__whatsapp__whatsapp_chat_metadata",
"mcp__whatsapp__whatsapp_chats",
"mcp__whatsapp__whatsapp_contacts_get",
"mcp__whatsapp__whatsapp_contacts_list",
"mcp__whatsapp__whatsapp_history_coverage",
"mcp__whatsapp__whatsapp_messages",
"mcp__whatsapp__whatsapp_search"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:40 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 32
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 32 tools that change things (3 destructive, 7 irreversible, 22 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.mcp.ai/p_whatsapp: tools/list returned 47 tools to an anonymous client, including whatsapp_group_participants_remove (destructive), whatsapp_message_delete (destructive), whatsapp_chat_archive (destructive), whatsapp_send_text (irreversible), whatsapp_send_media (irreversible) and 27 more
Findings
Matches of fixed checks, with the text they matched.
- Warnwhatsapp_sync
The server marks "whatsapp_sync" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "whatsapp_sync" says "sync": a word for a change.
The server marks "whatsapp_group_participants_remove" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "whatsapp_group_participants_remove" says "remove": a word for removing or ending something.
The server marks "whatsapp_message_delete" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "whatsapp_message_delete" says "delete": a word for removing or ending something.
The server marks "whatsapp_chat_archive" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "whatsapp_chat_archive" says "archive": a word for removing or ending something.
- Infoconnect
The description mentions "credentials".
What this check looks forMatched text
description: "...nticated:true and empty pending[]. When credentials are missing, returns connect_url for th..."
- Infomarketplace
The description mentions "credential".
What this check looks forMatched text
description: "...ating the tool list. If the MCP needs a credential/login, invoke returns a connect link; i..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools2 changed.~2 changedView diff
- Changed:whatsapp_send_mediaCan't be undonedescription
- Changed:whatsapp_send_textCan't be undonedescription
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http whatsapp https://api.mcp.ai/p_whatsappclaude mcp add --transport http whatsapp https://api.mcp.ai/p_whatsappRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__whatsapp__whatsapp_list_accounts",
"mcp__whatsapp__whatsapp_chats",
"mcp__whatsapp__whatsapp_messages",
"mcp__whatsapp__whatsapp_contacts_list",
"mcp__whatsapp__whatsapp_contacts_get",
"mcp__whatsapp__whatsapp_groups",
"mcp__whatsapp__whatsapp_group_members",
"mcp__whatsapp__whatsapp_chat_metadata",
"mcp__whatsapp__whatsapp_search",
"mcp__whatsapp__whatsapp_history_coverage",
"mcp__whatsapp__whatsapp_webhook_get",
"mcp__whatsapp__whatsapp_config_get",
"mcp__whatsapp__show_version",
"mcp__whatsapp__connect",
"mcp__whatsapp__toolkit_info"
],
"ask": [
"mcp__whatsapp__whatsapp_sync",
"mcp__whatsapp__whatsapp_send_text",
"mcp__whatsapp__whatsapp_send_media",
"mcp__whatsapp__whatsapp_messages_write",
"mcp__whatsapp__whatsapp_group_participants_add",
"mcp__whatsapp__whatsapp_group_participants_promote",
"mcp__whatsapp__whatsapp_group_participants_demote",
"mcp__whatsapp__whatsapp_react",
"mcp__whatsapp__whatsapp_poll_create",
"mcp__whatsapp__whatsapp_poll_vote",
"mcp__whatsapp__whatsapp_message_forward",
"mcp__whatsapp__whatsapp_message_edit",
"mcp__whatsapp__whatsapp_chat_unarchive",
"mcp__whatsapp__whatsapp_chat_pin",
"mcp__whatsapp__whatsapp_chat_unpin",
"mcp__whatsapp__whatsapp_chat_mute",
"mcp__whatsapp__whatsapp_chat_unmute",
"mcp__whatsapp__whatsapp_group_manage_create",
"mcp__whatsapp__whatsapp_group_manage_leave",
"mcp__whatsapp__whatsapp_group_manage_update",
"mcp__whatsapp__whatsapp_group_manage_invite_link",
"mcp__whatsapp__whatsapp_group_manage_join",
"mcp__whatsapp__whatsapp_group_manage_requests",
"mcp__whatsapp__whatsapp_history_backfill",
"mcp__whatsapp__whatsapp_webhook_set",
"mcp__whatsapp__whatsapp_config_set",
"mcp__whatsapp__report_bug",
"mcp__whatsapp__marketplace",
"mcp__whatsapp__authenticate"
],
"deny": [
"mcp__whatsapp__whatsapp_group_participants_remove",
"mcp__whatsapp__whatsapp_message_delete",
"mcp__whatsapp__whatsapp_chat_archive"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as whatsapp. Review it before you use it.
Capability tags behind 19 rules
- mcp__whatsapp__whatsapp_send_text outbound
- mcp__whatsapp__whatsapp_send_media outbound
- mcp__whatsapp__whatsapp_chats private-data, untrusted-input
- mcp__whatsapp__whatsapp_messages private-data, untrusted-input
- mcp__whatsapp__whatsapp_messages_write outbound
- mcp__whatsapp__whatsapp_contacts_list private-data
- mcp__whatsapp__whatsapp_contacts_get private-data
- mcp__whatsapp__whatsapp_poll_create outbound
- mcp__whatsapp__whatsapp_poll_vote outbound
- mcp__whatsapp__whatsapp_message_forward outbound
- mcp__whatsapp__whatsapp_message_edit outbound
- mcp__whatsapp__whatsapp_chat_metadata private-data, untrusted-input
- mcp__whatsapp__whatsapp_group_manage_invite_link outbound
- mcp__whatsapp__whatsapp_search private-data, untrusted-input
- mcp__whatsapp__whatsapp_history_coverage private-data, untrusted-input
- mcp__whatsapp__whatsapp_webhook_get untrusted-input
- mcp__whatsapp__whatsapp_webhook_set outbound
- mcp__whatsapp__whatsapp_config_get untrusted-input
- mcp__whatsapp__marketplace untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.mcp-dir/whatsapp-mcp/verify?hash=71b73bd2cabbade474d36e76e480e60cfb17a70c3e6c4e5104e08786f97a1194" | jq -e '.changed == false'Pinned hash 71b73bd2cabb, from Nov 8, 2026, 10:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.mcp-dir/whatsapp-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.mcp-dir/whatsapp-mcp)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:40 UTC.
WhatsApp MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the WhatsApp MCP server safe?
- No scan can promise that. What its definitions show: 47 tools, 32 of which can change, send or delete something, and 6 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the WhatsApp MCP server delete data?
- Yes. 3 tools can delete, cancel or revoke something: whatsapp_group_participants_remove, whatsapp_message_delete and whatsapp_chat_archive.
Can the WhatsApp MCP server do things that cannot be undone?
- Yes. 7 tools can send, pay, publish or merge: whatsapp_send_text, whatsapp_send_media, whatsapp_poll_create, whatsapp_poll_vote, whatsapp_message_forward, whatsapp_message_edit and 1 more.
What tools does the WhatsApp MCP server have?
- 47 tools: 3 destructive, 7 irreversible, 22 write, 15 read. whatsapp_group_participants_remove, whatsapp_message_delete, whatsapp_chat_archive, whatsapp_send_text, whatsapp_send_media, whatsapp_poll_create, whatsapp_poll_vote, whatsapp_message_forward and 39 more.
Does the WhatsApp MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the WhatsApp MCP server send data to outside services?
- 9 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): whatsapp_send_text, whatsapp_send_media, whatsapp_messages_write, whatsapp_poll_create, whatsapp_poll_vote, whatsapp_message_forward and 3 more.
Has the WhatsApp MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 8, 2026. Every change is on this page and in its Atom feed.