# WhatsApp

> Connect a personal/Business WhatsApp account via QR pairing (multi-device, like WhatsApp Web). Send 

- name: io.github.mcp-dir/whatsapp-mcp
- version: 0.1.0
- connection class: R0 (autonomous)
- trust: 91/100
- quality: 85/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.github.mcp-dir%2Fwhatsapp-mcp
- tools: https://api.protogrid.dev/v1/servers/io.github.mcp-dir%2Fwhatsapp-mcp/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "whatsapp-mcp": {
      "type": "http",
      "url": "https://api.mcp.ai/p_whatsapp"
    }
  }
}
```


## Trust

- hygiene: 100
- liveness: 100
- freshness: 85
- provenance: 80
- drivers: +repository +namespace-matches-repo +reachable +uptime-100% ~updated-60d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 85/100 (good)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 86 (weight 30)

- pass `tools.descriptions`: every tool has a description
- warn `tools.description_length`: 1 tools have descriptions over 1,024 characters, which crowds the context
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 47 of 47 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- warn `tools.token_cost`: about 8,629 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: no tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 47, about 8,629 tokens to load them all
- tool set hash: 6adcafe69034a6e538caf30036cf9517
- badge: [![protogrid quality](https://protogrid.dev/badge/io.github.mcp-dir/whatsapp-mcp.svg)](https://protogrid.dev/servers/io.github.mcp-dir/whatsapp-mcp)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://api.mcp.ai/p_whatsapp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (47)

- `authenticate`: 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.
- `connect`: 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.
- `marketplace`: 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.
- `report_bug`: Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.
- `show_version`: Show the current MCP platform and adapter versions.
- `toolkit_info`: Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.
- `whatsapp_chat_archive`: Change a chat's state. action: archive/unarchive, pin/unpin, mute/unmute. Requires chat_jid.

[Flattened action: archive]
- `whatsapp_chat_metadata`: Get metadata for a single chat (subject/name, archived/pinned/muted state, unread count, timestamps). Requires chat_jid.
- `whatsapp_chat_mute`: Change a chat's state. action: archive/unarchive, pin/unpin, mute/unmute. Requires chat_jid.

[Flattened action: mute]
- `whatsapp_chat_pin`: Change a chat's state. action: archive/unarchive, pin/unpin, mute/unmute. Requires chat_jid.

[Flattened action: pin]
- `whatsapp_chats`: List WhatsApp chats (individual + group). Sorted by most recent activity.
- `whatsapp_chat_unarchive`: Change a chat's state. action: archive/unarchive, pin/unpin, mute/unmute. Requires chat_jid.

[Flattened action: unarchive]
- `whatsapp_chat_unmute`: Change a chat's state. action: archive/unarchive, pin/unpin, mute/unmute. Requires chat_jid.

[Flattened action: unmute]
- `whatsapp_chat_unpin`: Change a chat's state. action: archive/unarchive, pin/unpin, mute/unmute. Requires chat_jid.

[Flattened action: unpin]
- `whatsapp_config_get`: 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.
- `whatsapp_config_set`: 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.
- `whatsapp_contacts_get`: 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]
- `whatsapp_contacts_list`: 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]
- `whatsapp_group_manage_create`: 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]
- `whatsapp_group_manage_invite_link`: 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]
- `whatsapp_group_manage_join`: 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]
- `whatsapp_group_manage_leave`: 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]
- `whatsapp_group_manage_requests`: 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]
- `whatsapp_group_manage_update`: 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]
- `whatsapp_group_members`: 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).
- `whatsapp_group_participants_add`: 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]
- `whatsapp_group_participants_demote`: 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]
- `whatsapp_group_participants_promote`: 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]
- `whatsapp_group_participants_remove`: 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]
- `whatsapp_groups`: List WhatsApp groups the account belongs to — subject, jid, participants count, owner.
- `whatsapp_history_backfill`: 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.
- `whatsapp_history_coverage`: 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.
- `whatsapp_list_accounts`: List WhatsApp accounts paired to this install — wa_jid, phone, label, proxy on/off, status.
- `whatsapp_message_delete`: 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.
- `whatsapp_message_edit`: 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.
- `whatsapp_message_forward`: 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.
- `whatsapp_messages`: 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.
- `whatsapp_messages_write`: 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.
- `whatsapp_poll_create`: 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.
- `whatsapp_poll_vote`: 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.
- `whatsapp_react`: 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.
- `whatsapp_search`: Full-text search across all stored messages (SQLite FTS5). Optional chat_jid to scope. Returns matches with context.
- `whatsapp_send_media`: 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]
- `whatsapp_send_text`: 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]
- `whatsapp_sync`: 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 }.
- `whatsapp_webhook_get`: 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.
- `whatsapp_webhook_set`: 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).