REMOTE · API.MCP.AI · SCANNED OCT 5
Connect a personal/Business WhatsApp account via QR pairing (multi-device, like WhatsApp Web). Send
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 5853 tokens (~124/item across 47 items; 47 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 6 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 48 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the WhatsApp MCP server?
WhatsApp is a hosted endpoint at https://api.mcp.ai/p_whatsapp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.mcp.ai
claude mcp add --transport http mcp-dir-whatsapp-mcp 'https://api.mcp.ai/p_whatsapp'
{
"mcpServers": {
"mcp-dir-whatsapp-mcp": {
"url": "https://api.mcp.ai/p_whatsapp"
}
}
} {
"servers": {
"mcp-dir-whatsapp-mcp": {
"type": "http",
"url": "https://api.mcp.ai/p_whatsapp"
}
}
} [mcp_servers.mcp-dir-whatsapp-mcp] url = "https://api.mcp.ai/p_whatsapp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mcp-dir-whatsapp-mcp": {
"type": "remote",
"url": "https://api.mcp.ai/p_whatsapp",
"enabled": true
}
}
} openclaw mcp add mcp-dir-whatsapp-mcp --url 'https://api.mcp.ai/p_whatsapp' --transport streamable-http
mcp_servers:
mcp-dir-whatsapp-mcp:
url: "https://api.mcp.ai/p_whatsapp" {
"McpServers": {
"mcp-dir-whatsapp-mcp": {
"Transport": "http",
"Url": "https://api.mcp.ai/p_whatsapp"
}
}
} assistant mcp add mcp-dir-whatsapp-mcp -t streamable-http -u 'https://api.mcp.ai/p_whatsapp'
{
"mcpServers": {
"mcp-dir-whatsapp-mcp": {
"type": "http",
"url": "https://api.mcp.ai/p_whatsapp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.356 → 0.9.358 functional
- 3 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.353 → 0.9.356 functional
- 2 Oct 26 0
- Stability: 0.97 → pass security
- 1 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.351 → 0.9.353 functional
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 −3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Oct 2026 · Probed https://api.mcp.ai/p_whatsapp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.ai | CN=WE1,O=Google Trust Services,C=US | 28 Sept 2026 | 27 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 1bf4d405299e078a0e62ff16cded599b |
| SANs: mcp.ai, *.mcp.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.mcp.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| mcp.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.mcp.ai/p_whatsapp | Verified | 200 | |
| http (plaintext) | http://api.mcp.ai/p_whatsapp | Inconclusive | 406 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
authenticate ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | – | – |
No output schema declared.
No examples provided.
connect ~42
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
marketplace ~532
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | – |
| arguments | string | – | – |
| cancel_comment | string | – | – |
| cancel_reason | string | – | – |
| conversation | string | – | – |
| immediate | boolean | – | – |
| limit | number | – | – |
| mcp_id | string | – | – |
| message | string | – | – |
| prompt_body | string | – | – |
| prompt_category | string | – | – |
| prompt_description | string | – | – |
| prompt_slug | string | – | – |
| prompt_targets | array | – | – |
| prompt_title | string | – | – |
| prompt_tool | string | – | – |
| prompt_vars | string | – | – |
| query | string | – | – |
| report_context | string | – | – |
| request_details | string | – | – |
| request_name | string | – | – |
| tier_slug | string | – | – |
| tool_id | string | – | – |
No output schema declared.
No examples provided.
report_bug ~50
Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | – |
| conversation | string | – | – |
| message | string | yes | – |
No output schema declared.
No examples provided.
show_version ~17
Show the current MCP platform and adapter versions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
toolkit_info ~37
Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
whatsapp_chat_archive ~65
Change a chat's state. action: archive/unarchive, pin/unpin, mute/unmute. Requires chat_jid. [Flattened action: archive]
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| chat_jid | string | yes | – |
| duration_secs | number | – | – |
No output schema declared.
No examples provided.
whatsapp_chat_metadata ~52
Get metadata for a single chat (subject/name, archived/pinned/muted state, unread count, timestamps). Requires chat_jid.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| chat_jid | string | yes | – |
No output schema declared.
No examples provided.
whatsapp_chat_mute ~66
Change a chat's state. action: archive/unarchive, pin/unpin, mute/unmute. Requires chat_jid. [Flattened action: mute]
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| chat_jid | string | yes | – |
| duration_secs | number | – | – |
No output schema declared.
No examples provided.
whatsapp_chat_pin ~65
Change a chat's state. action: archive/unarchive, pin/unpin, mute/unmute. Requires chat_jid. [Flattened action: pin]
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| chat_jid | string | yes | – |
| duration_secs | number | – | – |
No output schema declared.
No examples provided.
whatsapp_chat_unarchive ~67
Change a chat's state. action: archive/unarchive, pin/unpin, mute/unmute. Requires chat_jid. [Flattened action: unarchive]
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| chat_jid | string | yes | – |
| duration_secs | number | – | – |
No output schema declared.
No examples provided.
whatsapp_chat_unmute ~67
Change a chat's state. action: archive/unarchive, pin/unpin, mute/unmute. Requires chat_jid. [Flattened action: unmute]
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| chat_jid | string | yes | – |
| duration_secs | number | – | – |
No output schema declared.
No examples provided.
whatsapp_chat_unpin ~67
Change a chat's state. action: archive/unarchive, pin/unpin, mute/unmute. Requires chat_jid. [Flattened action: unpin]
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| chat_jid | string | yes | – |
| duration_secs | number | – | – |
No output schema declared.
No examples provided.
whatsapp_chats ~45
List WhatsApp chats (individual + group). Sorted by most recent activity.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| archived | boolean | – | – |
| limit | number | – | – |
No output schema declared.
No examples provided.
whatsapp_config_get ~50
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
whatsapp_config_set ~184
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.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| values | object | yes | – |
No output schema declared.
No examples provided.
whatsapp_contacts_get ~82
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]
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| jid | string | – | – |
| limit | number | – | – |
| query | string | – | – |
No output schema declared.
No examples provided.
whatsapp_contacts_list ~82
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]
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| jid | string | – | – |
| limit | number | – | – |
| query | string | – | – |
No output schema declared.
No examples provided.
whatsapp_group_manage_create ~195
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]
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| description | string | – | – |
| group_jid | string | – | – |
| invite | string | – | – |
| link_action | string | – | – |
| name | string | – | – |
| participants | array | – | – |
| req_action | string | – | – |
| users | array | – | – |
No output schema declared.
No examples provided.
whatsapp_group_manage_invite_link ~198
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]
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| description | string | – | – |
| group_jid | string | – | – |
| invite | string | – | – |
| link_action | string | – | – |
| name | string | – | – |
| participants | array | – | – |
| req_action | string | – | – |
| users | array | – | – |
No output schema declared.
No examples provided.
whatsapp_group_manage_join ~195
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]
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| description | string | – | – |
| group_jid | string | – | – |
| invite | string | – | – |
| link_action | string | – | – |
| name | string | – | – |
| participants | array | – | – |
| req_action | string | – | – |
| users | array | – | – |
No output schema declared.
No examples provided.
whatsapp_group_manage_leave ~195
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]
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| description | string | – | – |
| group_jid | string | – | – |
| invite | string | – | – |
| link_action | string | – | – |
| name | string | – | – |
| participants | array | – | – |
| req_action | string | – | – |
| users | array | – | – |
No output schema declared.
No examples provided.
whatsapp_group_manage_requests ~195
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]
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| description | string | – | – |
| group_jid | string | – | – |
| invite | string | – | – |
| link_action | string | – | – |
| name | string | – | – |
| participants | array | – | – |
| req_action | string | – | – |
| users | array | – | – |
No output schema declared.
No examples provided.
whatsapp_group_manage_update ~195
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]
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| description | string | – | – |
| group_jid | string | – | – |
| invite | string | – | – |
| link_action | string | – | – |
| name | string | – | – |
| participants | array | – | – |
| req_action | string | – | – |
| users | array | – | – |
No output schema declared.
No examples provided.
whatsapp_group_members ~66
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).
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| group_jid | string | yes | – |
No output schema declared.
No examples provided.
whatsapp_group_participants_add ~104
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]
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| group_jid | string | yes | – |
| users | array | yes | – |
No output schema declared.
No examples provided.
whatsapp_group_participants_demote ~106
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]
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| group_jid | string | yes | – |
| users | array | yes | – |
No output schema declared.
No examples provided.
whatsapp_group_participants_promote ~105
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]
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| group_jid | string | yes | – |
| users | array | yes | – |
No output schema declared.
No examples provided.
whatsapp_group_participants_remove ~104
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]
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| group_jid | string | yes | – |
| users | array | yes | – |
No output schema declared.
No examples provided.
whatsapp_groups ~33
List WhatsApp groups the account belongs to — subject, jid, participants count, owner.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
No output schema declared.
No examples provided.
whatsapp_history_backfill ~260
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.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| chat_jid | string | yes | – |
| count | number | – | – |
| requests | number | – | – |
No output schema declared.
No examples provided.
whatsapp_history_coverage ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| chat_jid | string | – | – |
| kind | string | – | – |
| limit | number | – | – |
| query | string | – | – |
No output schema declared.
No examples provided.
whatsapp_list_accounts ~39
List WhatsApp accounts paired to this install — wa_jid, phone, label, proxy on/off, status.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
No output schema declared.
No examples provided.
whatsapp_message_delete ~171
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.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| chat_jid | string | yes | – |
| for_everyone | boolean | – | – |
| message_id | string | yes | – |
| message_ids | array | – | – |
| text | string | – | – |
| to | string | – | – |
No output schema declared.
No examples provided.
whatsapp_message_edit ~171
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.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| chat_jid | string | yes | – |
| for_everyone | boolean | – | – |
| message_id | string | yes | – |
| message_ids | array | – | – |
| text | string | – | – |
| to | string | – | – |
No output schema declared.
No examples provided.
whatsapp_message_forward ~171
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.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| chat_jid | string | yes | – |
| for_everyone | boolean | – | – |
| message_id | string | yes | – |
| message_ids | array | – | – |
| text | string | – | – |
| to | string | – | – |
No output schema declared.
No examples provided.
whatsapp_messages ~148
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.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| after | string | – | – |
| before | string | – | – |
| chat_jid | string | yes | – |
| limit | number | – | – |
| order | string | – | – |
| since | string | – | – |
No output schema declared.
No examples provided.
whatsapp_messages_write ~81
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.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| chat_jid | string | yes | – |
| message_id | string | – | – |
| message_ids | array | – | – |
No output schema declared.
No examples provided.
whatsapp_poll_create ~139
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.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| chat_jid | string | – | – |
| message_id | string | – | – |
| message_ids | array | – | – |
| name | string | – | – |
| options | array | yes | – |
| selectable_count | number | – | – |
| to | string | – | – |
No output schema declared.
No examples provided.
whatsapp_poll_vote ~139
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.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| chat_jid | string | – | – |
| message_id | string | – | – |
| message_ids | array | – | – |
| name | string | – | – |
| options | array | yes | – |
| selectable_count | number | – | – |
| to | string | – | – |
No output schema declared.
No examples provided.
whatsapp_react ~85
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.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| chat_jid | string | yes | – |
| emoji | string | – | – |
| message_id | string | yes | – |
| message_ids | array | – | – |
No output schema declared.
No examples provided.
whatsapp_search ~63
Full-text search across all stored messages (SQLite FTS5). Optional chat_jid to scope. Returns matches with context.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| chat_jid | string | – | – |
| limit | number | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
whatsapp_send_media ~213
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. [Flattened action: media]
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| caption | string | – | – |
| filename | string | – | – |
| media_base64 | string | – | – |
| media_url | string | – | – |
| mimetype | string | – | – |
| reply_to | string | – | – |
| text | string | – | – |
| to | string | yes | – |
| type | string | – | – |
No output schema declared.
No examples provided.
whatsapp_send_text ~213
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. [Flattened action: text]
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| caption | string | – | – |
| filename | string | – | – |
| media_base64 | string | – | – |
| media_url | string | – | – |
| mimetype | string | – | – |
| reply_to | string | – | – |
| text | string | – | – |
| to | string | yes | – |
| type | string | – | – |
No output schema declared.
No examples provided.
whatsapp_sync ~97
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 }.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
No output schema declared.
No examples provided.
whatsapp_webhook_get ~65
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
whatsapp_webhook_set ~201
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).
| Name | Type | Req | Description |
|---|---|---|---|
| events | array | – | – |
| include_result | boolean | – | – |
| remove | boolean | – | – |
| secret | string | – | – |
| url | string | – | – |
No output schema declared.
No examples provided.
What is the WhatsApp MCP server?
WhatsApp is an MCP server listed in the public MCP registry as io.github.mcp-dir/whatsapp-mcp. Connect a personal/Business WhatsApp account via QR pairing (multi-device, like WhatsApp Web). Send. This page covers its hosted endpoint (https://api.mcp.ai/p_whatsapp).
Is the WhatsApp MCP server safe to use?
WhatsApp scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the WhatsApp MCP server expose?
WhatsApp exposes 47 tools: whatsapp_list_accounts, whatsapp_sync, whatsapp_send_text, whatsapp_send_media, whatsapp_chats, and 42 more. Their descriptions and schemas cost roughly 5,729 tokens of context every time the server is loaded.
Does the WhatsApp MCP server require authentication?
No. We connected to WhatsApp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the WhatsApp MCP server still maintained?
WhatsApp is still listed as active in the MCP registry. We last reached this channel on 5 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.