Skip to main content
Glama

Server Details

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

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
mcp-dir/whatsapp-mcp
GitHub Stars
0
Server Listing
WhatsApp MCP
ChatGPT
–
Claude
–

TDQS

C2.7/5.0

Scored across 47 tools

Disambiguation2/5

Multiple tools share byte-identical descriptions (six whatsapp_chat_* state tools all read 'Change a chat's state. action: archive/unarchive, pin/unpin, mute/unmute'; six whatsapp_group_manage_* tools and four whatsapp_group_participants_* also have identical text), so the description does nothing to steer an agent to the right tool. The individual tool names are distinct enough to salvage some selection, but the flattened action surface means each tool advertises actions that belong to its siblings. Boundaries are heavily obscured by the shared descriptions.

Naming Consistency3/5

The whatsapp_* tools follow a readable snake_case domain_action pattern (whatsapp_chat_archive, whatsapp_group_manage_create), which is consistent within its family. However, six platform tools (authenticate, connect, marketplace, report_bug, show_version, toolkit_info) have no prefix and use generic verbs, breaking the pattern. The flattened action-vs-name suffixing (e.g. whatsapp_send_text vs whatsapp_send_media duplicating one description) adds minor irregularity.

Tool Count2/5

47 tools is far beyond a healthy scope; many are near-duplicates created by exploding multi-action tools into one tool per action (six chat-state tools, six group-manage tools). The domain could plausibly be served with a fraction of these if consolidated. The result is a bloated surface that dilutes selection.

Completeness4/5

The surface is genuinely comprehensive: messages (send, edit, delete, forward, react, read), chats (list, metadata, archive/pin/mute), groups (create, join, leave, participants, invite, requests), contacts, full-text search, history coverage/backfill, polls, webhooks, config, and multi-account listing. Only modest gaps remain (e.g. status/broadcast, explicit get-single-message). Coverage is not a weakness here.

Available Tools

47 tools
authenticateA
Idempotent
Inspect

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: "" } after the user pastes, or with no args to get the link.

Inputs: token.

connectA
Read-onlyIdempotent
Inspect

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.

Inputs: no named parameters.

marketplaceAInspect

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/ link that opens without login.

Inputs: limit, query, action, mcp_id, +19 more.

report_bugA
Idempotent
Inspect

Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.

Inputs: message (required), context, conversation.

show_versionA
Read-onlyIdempotent
Inspect

Show the current MCP platform and adapter versions.

Inputs: no named parameters.

toolkit_infoA
Read-onlyIdempotent
Inspect

Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.

Inputs: no named parameters.

whatsapp_chat_archiveCInspect

Change a chat's state. action: archive/unarchive, pin/unpin, mute/unmute. Requires chat_jid.

[Flattened action: archive]

Inputs: chat_jid (required), account, duration_secs.

whatsapp_chat_metadataA
Read-onlyIdempotent
Inspect

Get metadata for a single chat (subject/name, archived/pinned/muted state, unread count, timestamps). Requires chat_jid.

Inputs: chat_jid (required), account.

whatsapp_chat_muteDInspect

Change a chat's state. action: archive/unarchive, pin/unpin, mute/unmute. Requires chat_jid.

[Flattened action: mute]

Inputs: chat_jid (required), account, duration_secs.

whatsapp_chat_pinDInspect

Change a chat's state. action: archive/unarchive, pin/unpin, mute/unmute. Requires chat_jid.

[Flattened action: pin]

Inputs: chat_jid (required), account, duration_secs.

whatsapp_chatsB
Read-onlyIdempotent
Inspect

List WhatsApp chats (individual + group). Sorted by most recent activity.

Inputs: limit, account, archived.

whatsapp_chat_unarchiveBInspect

Change a chat's state. action: archive/unarchive, pin/unpin, mute/unmute. Requires chat_jid.

[Flattened action: unarchive]

Inputs: chat_jid (required), account, duration_secs.

whatsapp_chat_unmuteCInspect

Change a chat's state. action: archive/unarchive, pin/unpin, mute/unmute. Requires chat_jid.

[Flattened action: unmute]

Inputs: chat_jid (required), account, duration_secs.

whatsapp_chat_unpinCInspect

Change a chat's state. action: archive/unarchive, pin/unpin, mute/unmute. Requires chat_jid.

[Flattened action: unpin]

Inputs: chat_jid (required), account, duration_secs.

whatsapp_config_getA
Read-onlyIdempotent
Inspect

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.

Inputs: no named parameters.

whatsapp_config_setAInspect

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.

Inputs: values (required), account.

whatsapp_contacts_getB
Read-onlyIdempotent
Inspect

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]

Inputs: jid, limit, query, account.

whatsapp_contacts_listA
Read-onlyIdempotent
Inspect

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]

Inputs: jid, limit, query, account.

whatsapp_group_manage_createCInspect

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]

Inputs: name, users, invite, account, +5 more.

whatsapp_group_manage_joinCInspect

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]

Inputs: name, users, invite, account, +5 more.

whatsapp_group_manage_leaveCInspect

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]

Inputs: name, users, invite, account, +5 more.

whatsapp_group_manage_requestsDInspect

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]

Inputs: name, users, invite, account, +5 more.

whatsapp_group_manage_updateCInspect

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]

Inputs: name, users, invite, account, +5 more.

whatsapp_group_membersA
Read-onlyIdempotent
Inspect

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).

Inputs: group_jid (required), account.

whatsapp_group_participants_addBInspect

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]

Inputs: users (required), group_jid (required), account.

whatsapp_group_participants_demoteBInspect

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]

Inputs: users (required), group_jid (required), account.

whatsapp_group_participants_promoteAInspect

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]

Inputs: users (required), group_jid (required), account.

whatsapp_group_participants_removeDInspect

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]

Inputs: users (required), group_jid (required), account.

whatsapp_groupsA
Read-onlyIdempotent
Inspect

List WhatsApp groups the account belongs to — subject, jid, participants count, owner.

Inputs: account.

whatsapp_history_backfillAInspect

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.

Inputs: chat_jid (required), count, account, requests.

whatsapp_history_coverageA
Read-onlyIdempotent
Inspect

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.

Inputs: kind, limit, query, account, +1 more.

whatsapp_list_accountsA
Read-onlyIdempotent
Inspect

List WhatsApp accounts paired to this install — wa_jid, phone, label, proxy on/off, status.

Inputs: account.

whatsapp_message_deleteCInspect

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.

Inputs: chat_jid (required), message_id (required), to, text, +3 more.

whatsapp_message_editDInspect

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.

Inputs: chat_jid (required), message_id (required), to, text, +3 more.

whatsapp_message_forwardCInspect

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.

Inputs: chat_jid (required), message_id (required), to, text, +3 more.

whatsapp_messagesA
Read-onlyIdempotent
Inspect

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.

Inputs: chat_jid (required), after, limit, order, +3 more.

whatsapp_messages_writeAInspect

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.

Inputs: chat_jid (required), account, message_id, message_ids.

whatsapp_poll_createCInspect

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.

Inputs: options (required), to, name, account, +4 more.

whatsapp_poll_voteCInspect

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.

Inputs: options (required), to, name, account, +4 more.

whatsapp_reactAInspect

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.

Inputs: chat_jid (required), message_id (required), emoji, account, +1 more.

whatsapp_send_mediaAInspect

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', '@g.us') or a plain phone (digits, country code included). For groups always use the '@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]

Inputs: to (required), text, type, account, +6 more.

whatsapp_send_textAInspect

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', '@g.us') or a plain phone (digits, country code included). For groups always use the '@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]

Inputs: to (required), text, type, account, +6 more.

whatsapp_syncA
Read-onlyIdempotent
Inspect

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 }.

Inputs: account.

whatsapp_webhook_getA
Read-onlyIdempotent
Inspect

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.

Inputs: no named parameters.

whatsapp_webhook_setAInspect

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).

Inputs: url, events, remove, secret, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to pair with a personal or business WhatsApp account via terminal QR code, then send text messages, forward media from URLs, verify phone numbers, and check connection status.
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects your own WhatsApp account to AI clients so they can summarize and search chats, identify unanswered messages, manage media, and draft or send messages, polls, and scheduled messages.
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables linking a WhatsApp number via QR code and then sending, reading, listing chats, and checking status through MCP tools, with per-account API key authentication.
      -
    • A
      license
      B
      quality
      D
      maintenance
      Enables AI agents to control WhatsApp, including sending messages and media, reading chats, managing groups and communities, with QR/pairing auth and session persistence.
      14
      22 npm
      2
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.