Awesome MCP Servers by AI Anytime

Directory / Marketing, content & social

Wassenger

Send WhatsApp messages and approved templates, and manage chats, contacts, campaigns and a shared team inbox through the official WhatsApp Business API; needs a Wassenger API key. Endpoint: https://api.wassenger.com/mcp · Docs

Live  Answered an MCP handshake without credentials and listed 60 tools.

Category
Marketing, content & social
Transport
http
Source
https://github.com/wassengerhq/whatsapp-mcp
Endpoint
https://api.wassenger.com/mcp
MCP Registry
com.wassenger/whatsapp
Reports itself as
WhatsApp MCP 1.0.0
Protocol
2025-06-18
Tools
60
Context cost
about 41,541 tokens for the tool definitions (estimated at four characters per token)
Tool definitions last changed
no change seen since first check
Handshake time
164 ms
Repository
6 stars · last push 2026-11-13 · MIT
Last checked
2026-11-22 11:27:53 UTC
Listed since
2026-11-18

Health and compatibility

Endpoint reachableVerifiedResponded in 164 ms
MCP handshake (initialize)VerifiedCompleted without credentials
Tool discovery (tools/list)Verified60 tools listed
AuthenticationVerifiedNone needed to connect
Protocol versionVerified2025-06-18
TransportVerifiedStreamable HTTP
Capabilities declaredVerifiedcompletions, logging, prompts, tools

Last checked . Verified means the check saw it happen; it says nothing about whether the server is safe.

Recent history

5 daily checks so far; median response 157 ms. Green answered, violet asked for auth, red did not answer.

Set up in your client

Claude Code

Run this in a terminal:

claude mcp add --transport http wassenger https://api.wassenger.com/mcp

Claude Desktop

Open Settings → Connectors → Add custom connector and paste this URL:

https://api.wassenger.com/mcp

Or bridge it through mcp-remote in claude_desktop_config.json (needs Node.js):

{
  "mcpServers": {
    "wassenger": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.wassenger.com/mcp"
      ]
    }
  }
}

Cursor

Add to Cursor

Or add it to ~/.cursor/mcp.json (or .cursor/mcp.json in a project):

{
  "mcpServers": {
    "wassenger": {
      "url": "https://api.wassenger.com/mcp"
    }
  }
}

VS Code

Add to VS Code

Or add it to .vscode/mcp.json:

{
  "servers": {
    "wassenger": {
      "type": "http",
      "url": "https://api.wassenger.com/mcp"
    }
  }
}

Or from a terminal:

code --add-mcp '{"name": "wassenger", "type": "http", "url": "https://api.wassenger.com/mcp"}'

Windsurf

Add it to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "wassenger": {
      "serverUrl": "https://api.wassenger.com/mcp"
    }
  }
}

Other clients

Most clients accept this shape. The endpoint is:

https://api.wassenger.com/mcp
{
  "mcpServers": {
    "wassenger": {
      "type": "http",
      "url": "https://api.wassenger.com/mcp"
    }
  }
}

If it does not connect

Tools 60

Names, descriptions and input schemas exactly as the server returned them on 2026-11-22. This is the server author's own text. Nothing is run from this page. Labels such as read-only are declared by the server and are not verified. Raw JSON

analyze_whatsapp_chat_messagesWhatsApp chat message analysis tool. Supports delivery-status lookups and chat export. The 'device' parameter …

WhatsApp chat message analysis tool. Supports delivery-status lookups and chat export. The 'device' parameter accepts a device ID (24-hex), phone number (E.164), or alias — auto-selected if the account has a single device; otherwise the tool errors with the list of available devices so you can ask the user. Available actions: - delivery_status: Check delivery and read receipts for specific outbound messages (≤30 days old) - export: Export chat messages in JSON, CSV, or TXT format

ParameterTypeDescription
actionstringrequiredAction to perform for WhatsApp message analysis operations One of: delivery_status, export
chatstringoptionalWhatsApp chat ID (required for export)
devicestringoptionalTarget WhatsApp device — accepts device ID (24-hex), phone number in E.164 format, or device alias. Optional: if the account has a single device, it is auto-selected; otherwise specify which one.
fromDatestringoptionalExport period start date
toDateanyoptionalExport period end date
messageIdsstring[]optionalMessage IDs to check status for (required for delivery_status, max 20)
formatstringoptionalExport format One of: json, csv, txt
includeMediabooleanoptionalInclude media file information in export
includeMetadatabooleanoptionalInclude full message metadata in export
maxMessagesnumberoptionalMaximum messages to export (paginated under the hood)

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "analyze_whatsapp_chat_messages",
    "arguments": {
      "action": "delivery_status"
    }
  }
}
analyze_whatsapp_chatsReports and exports of the chats of a WhatsApp number. Available actions: - statistics: the team's figures …

Reports and exports of the chats of a WhatsApp number. Available actions: - statistics: the team's figures for a period (7 days by default, up to 92): new, resolved and reopened chats, messages received and sent, internal notes, average time to the first reply, to each reply, to resolve and to handle a chat, what was in the inbox at the end of the period, the most used labels and a day-by-day breakdown. Add compareFromDate and compareToDate to compare with an earlier period and get the change in percent. Days are cut at midnight in the account timezone, so for whole days pass local midnights with their offset. Times are in seconds. There is no breakdown per agent or per hour. - export: Export chats in JSON, CSV or TXT, filtered by status and date, paging through as many chats as requested Use this tool for: weekly reports, response time reviews, backups, and feeding chat lists into another system.

ParameterTypeDescription
actionstringrequiredChat analysis action to perform One of: statistics, export
devicestringrequiredWhatsApp device ID connected to Wassenger (24 character hexadecimal string)
formatstringoptionalExport format One of: json, csv, txt
limitnumberoptionalMaximum number of WhatsApp chats to export (max 1000, fetched in pages of 500)
statusstring[]optionalExport only: filter by chat status
fromDatestringoptionalStart of the period, e.g. 2026-09-11T00:00:00+02:00. Statistics: defaults to 7 days before toDate. Export: only chats whose last message is after this date
toDatestringoptionalEnd of the period. Statistics: defaults to now. Export: only chats whose last message is before this date
compareFromDatestringoptionalStatistics only: start of an earlier period to compare with. Requires compareToDate
compareToDatestringoptionalStatistics only: end of the earlier period to compare with
verbositystringoptionalResponse detail level for the json format One of: summary, standard, full
fieldsstring[]optionalExplicit dot-path allowlist for the json format. Overrides verbosity when set.

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "analyze_whatsapp_chats",
    "arguments": {
      "action": "statistics",
      "device": "..."
    }
  }
}
create_whatsapp_templatecan modifyexternal accessCreate a WhatsApp message template and submit it to WhatsApp for review (WhatsApp Business API numbers only). …

Create a WhatsApp message template and submit it to WhatsApp for review (WhatsApp Business API numbers only). It works in steps. Call it with whatever the user has given so far: if anything is missing or breaks a WhatsApp rule, it returns needsInput with the exact questions to ask, and nothing is created. When everything is valid it returns a preview and a confirmToken, still without creating anything. Show the preview; only after the user approves, call it again with the same fields plus the confirmToken. Supports text, image, video, document and location headers, body variables ({{1}} or {{first_name}}) with sample values, a footer, quick reply, URL, phone number and copy code buttons, and authentication (one-time code) templates.

ParameterTypeDescription
devicestringoptionalWhatsApp Business API device ID (24 hex characters) that will own the template. Use get_whatsapp_devices to find it.
namestringoptionalTemplate name: lowercase letters, numbers and underscores, e.g. order_ready
languagestringoptionalWhatsApp language code of the template text, e.g. en_US, es, pt_BR
categorystringoptionalMARKETING (promotions and offers), UTILITY (order, account or appointment updates) or AUTHENTICATION (one-time codes) One of: MARKETING, UTILITY, AUTHENTICATION
headerobjectoptionalOptional header shown above the body
bodystringoptionalMessage body, up to 1024 characters. Mark per-message values with {{1}}, {{2}} or named variables like {{first_name}}; never at the very start or end, and never next to each other. Not used for AUTHENTICATION templates.
bodyExamplesobjectoptionalOne realistic sample value per body variable, keyed by the variable: {"1": "Maria"} or {"first_name": "Maria"}. Ask the user for them; never invent them.
footerstringoptionalOptional footer, up to 60 characters, without variables
buttonsobject[]optionalOptional buttons: up to 10 in total, at most 2 URL, 1 PHONE_NUMBER and 1 COPY_CODE, with quick replies grouped together
authenticationobjectoptionalOptions for AUTHENTICATION templates only
confirmTokenstringoptionalToken returned with the preview. Pass it only after the user approved that exact preview.

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "create_whatsapp_template",
    "arguments": {}
  }
}
delete_whatsapp_fileDelete an uploaded WhatsApp file permanently. This action cannot be undone and will remove the file from …

Delete an uploaded WhatsApp file permanently. This action cannot be undone and will remove the file from storage. The file will no longer be available for sending in messages.

ParameterTypeDescription
fileIdstringrequiredFile ID (24 character hexadecimal string)

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "delete_whatsapp_file",
    "arguments": {
      "fileId": "..."
    }
  }
}
delete_whatsapp_templatecan modifydestructiveexternal accessDelete one WhatsApp message template, in one language, from a WhatsApp Business API number. It works in two …

Delete one WhatsApp message template, in one language, from a WhatsApp Business API number. It works in two steps: called without a confirmToken it only reports which template would be deleted and returns a token, writing nothing; the deletion happens on a second call carrying that token, after the user approved it. It never deletes more than the template it reported, and it asks which language when the name exists in several.

ParameterTypeDescription
devicestringoptionalWhatsApp Business API device ID (24 hex characters) that owns the template
namestringoptionalName of the template to delete
languagestringoptionalLanguage code of the template to delete, e.g. es or en_US. Required when the name exists in several languages.
confirmTokenstringoptionalToken returned with the confirmation. Pass it only after the user approved deleting that exact template.

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "delete_whatsapp_template",
    "arguments": {}
  }
}
delete_whatsapp_web_form_submissionscan modifydestructiveexternal accessDelete web form submissions, or cancel a booking: delete (one), delete_many (up to 100 ids), forget_contact …

Delete web form submissions, or cancel a booking: delete (one), delete_many (up to 100 ids), forget_contact (every submission of one contact, the contact fields the forms wrote, and the contact's WhatsApp Forms responses, for an erasure request), or cancel_booking (the appointment a submission booked: the time is offered again, the answers stay; with message, the customer is told in the chat). The first call reports what would be erased or cancelled and a confirmToken; call again with the token once the user approved. Only the account owner's key or an admin can delete; a booking can also be cancelled by the agent who sent its link. For WhatsApp Forms (Meta WhatsApp Flows, native in-chat forms on WhatsApp Business API numbers) use send_whatsapp_flow and list_whatsapp_flows instead.

ParameterTypeDescription
actionstringrequiredWhat to do One of: delete, delete_many, forget_contact, cancel_booking
submissionIdstringoptionaldelete, cancel_booking: the submission
messagestringoptionalcancel_booking: what to tell the customer in the chat; leave out to cancel without telling them
idsstring[]optionaldelete_many: the submissions
contactstringoptionalforget_contact: chat ID or phone of the contact
devicestring[]optionalforget_contact: only on these numbers
formIdstringoptionalforget_contact: only this web form
allFormsbooleanoptionalforget_contact: across every web form
confirmTokenstringoptionalToken from the preview, sent back once the user approved the change

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "delete_whatsapp_web_form_submissions",
    "arguments": {
      "action": "delete"
    }
  }
}
download_whatsapp_chat_fileDownload the content of a received file from a WhatsApp chat. Returns the file content in the specified …

Download the content of a received file from a WhatsApp chat. Returns the file content in the specified format: URL only (default) or base64 encoded content.

ParameterTypeDescription
devicestringrequiredWhatsApp device ID connected to Wassenger (24 character hexadecimal string)
fileIdstringrequiredFile ID (24 character hexadecimal string)
outputFormatstringoptionalDownload format: url (download URL only) or base64 (encoded file content) One of: url, base64

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "download_whatsapp_chat_file",
    "arguments": {
      "device": "...",
      "fileId": "..."
    }
  }
}
download_whatsapp_fileDownload the content of an uploaded WhatsApp file. Returns the file content in the specified format: URL only …

Download the content of an uploaded WhatsApp file. Returns the file content in the specified format: URL only (default) or base64 encoded content.

ParameterTypeDescription
fileIdstringrequiredFile ID (24 character hexadecimal string)
outputFormatstringoptionalDownload format: url (download URL only) or base64 (encoded file content) One of: url, base64

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "download_whatsapp_file",
    "arguments": {
      "fileId": "..."
    }
  }
}
export_whatsapp_chatsExport WhatsApp chats list in various formats for backup, analysis, or reporting purposes. Same as …

Export WhatsApp chats list in various formats for backup, analysis, or reporting purposes. Same as analyze_whatsapp_chats with action "export".

ParameterTypeDescription
devicestringrequiredWhatsApp device ID connected to Wassenger (24 character hexadecimal string)
formatstringoptionalExport format One of: json, csv, txt
limitnumberoptionalMaximum number of WhatsApp chats to export (max 1000, fetched in pages of 500)
statusstring[]optionalExport only: filter by chat status
fromDatestringoptionalStart of the period, e.g. 2026-09-11T00:00:00+02:00. Statistics: defaults to 7 days before toDate. Export: only chats whose last message is after this date
toDatestringoptionalEnd of the period. Statistics: defaults to now. Export: only chats whose last message is before this date
compareFromDatestringoptionalStatistics only: start of an earlier period to compare with. Requires compareToDate
compareToDatestringoptionalStatistics only: end of the earlier period to compare with
verbositystringoptionalResponse detail level for the json format One of: summary, standard, full
fieldsstring[]optionalExplicit dot-path allowlist for the json format. Overrides verbosity when set.

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "export_whatsapp_chats",
    "arguments": {
      "device": "..."
    }
  }
}
get_whatsapp_archived_chatsRetrieve archived WhatsApp chats. Useful for accessing historical conversations and managing chat …

Retrieve archived WhatsApp chats. Useful for accessing historical conversations and managing chat organization. Same as get_whatsapp_chats with action "archived".

ParameterTypeDescription
devicestringrequiredWhatsApp device ID connected to Wassenger (24 character hexadecimal string)
limitnumberoptionalNumber of WhatsApp chats per call (max 100)
pagenumberoptionalResults page, starting at 0
sortstringoptionalResult order. Defaults to the API order (most recent activity first) One of: date:asc, date:desc, lastMessage:asc, lastMessage:desc, inbound:asc
fromDatestringoptionalStart date (for by_date_range and archived actions)
toDateanyoptionalEnd date (for by_date_range and archived actions)

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "get_whatsapp_archived_chats",
    "arguments": {
      "device": "..."
    }
  }
}
get_whatsapp_assigned_chatsRetrieve WhatsApp chats assigned to specific agents or departments. Essential for agent workload management …

Retrieve WhatsApp chats assigned to specific agents or departments. Essential for agent workload management and performance tracking. Same as get_whatsapp_chats with action "assigned".

ParameterTypeDescription
devicestringrequiredWhatsApp device ID connected to Wassenger (24 character hexadecimal string)
agentIdstringoptionalFilter by assigned agent ID (for assigned action)
departmentIdstringoptionalFilter by assigned department ID (for assigned action)
limitnumberoptionalNumber of WhatsApp chats per call (max 100)
pagenumberoptionalResults page, starting at 0
sortstringoptionalResult order. Defaults to the API order (most recent activity first) One of: date:asc, date:desc, lastMessage:asc, lastMessage:desc, inbound:asc

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "get_whatsapp_assigned_chats",
    "arguments": {
      "device": "..."
    }
  }
}
get_whatsapp_chat_by_idRetrieve detailed information about a specific chat using its WhatsApp ID. Includes complete metadata, …

Retrieve detailed information about a specific chat using its WhatsApp ID. Includes complete metadata, assignment info, and activity details. Same as get_whatsapp_chats with action "by_id".

ParameterTypeDescription
devicestringrequiredWhatsApp device ID connected to Wassenger (24 character hexadecimal string)
verbositystringoptionalResponse detail level: summary = curated high-signal fields (default, token-lean); standard = broader set; full = complete chat objects (escape hatch). One of: summary, standard, full
fieldsstring[]optionalExplicit dot-path allowlist, e.g. ['id','name','contact.phone','unreadCount']. Overrides verbosity when set.
chatstringrequiredWhatsApp chat ID (e.g., 1234567890@c.us for phone numbers, 123456789000000000@g.us for groups, 123456789000000@newsletter for WhatsApp channels)

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "get_whatsapp_chat_by_id",
    "arguments": {
      "device": "...",
      "chat": "..."
    }
  }
}
get_whatsapp_chat_file_detailsGet detailed information about a specific received file from a WhatsApp chat by ID. Returns complete file …

Get detailed information about a specific received file from a WhatsApp chat by ID. Returns complete file metadata including sender information, chat context, media details, and download URLs.

ParameterTypeDescription
devicestringrequiredWhatsApp device ID connected to Wassenger (24 character hexadecimal string)
fileIdstringrequiredFile ID (24 character hexadecimal string)

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "get_whatsapp_chat_file_details",
    "arguments": {
      "device": "...",
      "fileId": "..."
    }
  }
}
get_whatsapp_chat_messagesRetrieve WhatsApp chat messages (both inbound and outbound) for a specific device. Backed by the …

Retrieve WhatsApp chat messages (both inbound and outbound) for a specific device. Backed by the device-scoped Chat Messages endpoint, which requires a Platform subscription on the target device. Available actions: - recent: Latest messages in a chat (newest first by default) - search: Text search across messages (within a chat or device-wide) - date_range: Messages in a specific time window - by_sender: Messages sent from a specific phone number or WID - by_type: Messages filtered by type (text, image, video, audio, document, location, contact, etc.) - by_id: Fetch a specific message by its WhatsApp message ID - thread: Get conversation context around a specific message (N before + target + N after) - media: Messages containing media files The 'device' parameter accepts a device ID (24-hex), phone number in E.164 format, or device alias (e.g., "Sales 2") — pass exactly what the user named in their request. If the account has a single device, omit it and it will be auto-selected. If the account has multiple devices and the user didn't name one, the tool returns an error listing available devices — ask the user which one they mean.

ParameterTypeDescription
actionstringrequiredAction to perform for WhatsApp message retrieval operations One of: recent, search, date_range, by_sender, by_type, by_id, thread, media
chatstringoptionalWhatsApp chat ID. Required for all actions except by_id and search (which accepts device-wide search when chat is omitted)
devicestringoptionalTarget WhatsApp device — accepts device ID (24-hex), phone number in E.164 format, or device alias. Optional: if the account has a single device, it is auto-selected; otherwise specify which one.
messageIdstringoptionalSpecific message ID (required for by_id and thread actions)
limitnumberoptionalMaximum messages to retrieve per request (REST API caps at 50)
includeMediabooleanoptionalReserved for compatibility — media is always included when present
sortOrderstringoptionalSort order by date (default: desc) One of: asc, desc
querystringoptionalText to search for (required for search action)
fromDatestringoptionalLower bound of the date range (maps to REST `after`)
toDateanyoptionalUpper bound of the date range (maps to REST `before`)
senderstringoptionalPhone number or WID of message sender (required for by_sender action)
messageTypesstring[]optionalTypes of messages to retrieve (required for by_type action)
contextBeforenumberoptionalMessages before target message (thread action)
contextAfternumberoptionalMessages after target message (thread action)
mediaTypesstring[]optionalFilter by specific media types (media action)
includeReactionsbooleanoptionalReserved for compatibility — reactions are returned inline by the REST API when available
includeQuotesbooleanoptionalWhen true, request quoted message details from the API (off by default to keep responses lean)
includeFileDetailsbooleanoptionalReturn full media file metadata (media action)
verbositystringoptionalResponse detail level: summary = curated high-signal fields (default, token-lean); standard = broader set; full = complete message objects (escape hatch). One of: summary, standard, full
fieldsstring[]optionalExplicit dot-path allowlist, e.g. ['id','date','flow','body']. Overrides verbosity when set.

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "get_whatsapp_chat_messages",
    "arguments": {
      "action": "recent"
    }
  }
}
get_whatsapp_chat_statisticsFigures of the team for a period: chat and message volumes, response and resolution times, and what was in …

Figures of the team for a period: chat and message volumes, response and resolution times, and what was in the inbox at the end of the period, optionally compared with an earlier period. Same as analyze_whatsapp_chats with action "statistics".

ParameterTypeDescription
devicestringrequiredWhatsApp device ID connected to Wassenger (24 character hexadecimal string)
compareFromDatestringoptionalStatistics only: start of an earlier period to compare with. Requires compareToDate
compareToDatestringoptionalStatistics only: end of the earlier period to compare with
fromDatestringoptionalStart of the period, e.g. 2026-09-11T00:00:00+02:00. Defaults to 7 days before toDate
toDatestringoptionalEnd of the period. Defaults to now

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "get_whatsapp_chat_statistics",
    "arguments": {
      "device": "..."
    }
  }
}
get_whatsapp_chatsComprehensive WhatsApp chat retrieval tool supporting all chat operations through a unified action-based …

Comprehensive WhatsApp chat retrieval tool supporting all chat operations through a unified action-based interface. Perfect for accessing chat lists, searching conversations, filtering by various criteria, and managing chat data. Supports all WhatsApp chat retrieval operations with consistent formatting. Available actions: - recent: Most recent chats - unread: Chats with unread messages - by_status: Filter by chat status (pending, active, resolved, archived...) - assigned: Chats assigned to an agent or department, or to anyone - unassigned: Chats nobody is handling yet - by_contact_type: Filter by chat type (chat, group, community, channel) - by_id: One chat by its WhatsApp ID - search: Free text search over phone, name, contact, company, metadata and private notes - archived: Archived chats - by_date_range: Chats by last message, first message or last inbound message date Every action accepts labels, labelsExclude, status and contactTypes as extra filters. To find leads that went quiet, use by_date_range with activityType "lastInbound" and a toDate: those are the chats where the customer has not written since then.

ParameterTypeDescription
actionstringoptionalChat retrieval action to perform One of: recent, unread, by_status, assigned, unassigned, by_contact_type, by_id, search …
devicestringrequiredWhatsApp device ID connected to Wassenger (24 character hexadecimal string)
limitnumberoptionalNumber of WhatsApp chats per call (max 100)
pagenumberoptionalResults page, starting at 0
sortstringoptionalResult order. Defaults to the API order (most recent activity first) One of: date:asc, date:desc, lastMessage:asc, lastMessage:desc, inbound:asc
chatIdstringoptionalSpecific chat ID (required for by_id action)
statusstring[]optionalFilter by chat status (required for by_status action, optional elsewhere)
contactTypesstring[]optionalFilter by chat type (required for by_contact_type action, optional elsewhere)
agentIdstringoptionalFilter by assigned agent ID (for assigned action)
departmentIdstringoptionalFilter by assigned department ID (for assigned action)
querystringoptionalFree text to search for (required for search action)
labelsstring[]optionalOnly chats carrying at least one of these labels. Use ["*"] for any label. Cannot be combined with labelsExclude
labelsExcludeany[]optionalExclude chats carrying any of these labels. Use ["*"] to exclude every labelled chat
fromDatestringoptionalStart date (for by_date_range and archived actions)
toDateanyoptionalEnd date (for by_date_range and archived actions)
activityTypestringoptionalWhich date the range applies to: last message of any side, first message ever, or last message received from the customer One of: lastMessage, firstMessage, lastInbound
verbositystringoptionalResponse detail level: summary = curated high-signal fields (default, token-lean); standard = broader set; full = complete chat objects (escape hatch). One of: summary, standard, full
fieldsstring[]optionalExplicit dot-path allowlist, e.g. ['id','name','contact.phone','unreadCount']. Overrides verbosity when set.

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "get_whatsapp_chats",
    "arguments": {
      "device": "..."
    }
  }
}
get_whatsapp_chats_by_contact_typeFilter WhatsApp chats by contact type (individual users, groups, communities, channels). Useful for analyzing …

Filter WhatsApp chats by contact type (individual users, groups, communities, channels). Useful for analyzing different communication patterns. Same as get_whatsapp_chats with action "by_contact_type".

ParameterTypeDescription
devicestringrequiredWhatsApp device ID connected to Wassenger (24 character hexadecimal string)
contactTypesstring[]optionalFilter by chat type (required for by_contact_type action, optional elsewhere)
limitnumberoptionalNumber of WhatsApp chats per call (max 100)
pagenumberoptionalResults page, starting at 0
sortstringoptionalResult order. Defaults to the API order (most recent activity first) One of: date:asc, date:desc, lastMessage:asc, lastMessage:desc, inbound:asc

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "get_whatsapp_chats_by_contact_type",
    "arguments": {
      "device": "..."
    }
  }
}
get_whatsapp_chats_by_date_rangeRetrieve WhatsApp chats that were active within a specific date range. Perfect for analyzing conversation …

Retrieve WhatsApp chats that were active within a specific date range. Perfect for analyzing conversation patterns and generating reports. Same as get_whatsapp_chats with action "by_date_range".

ParameterTypeDescription
devicestringrequiredWhatsApp device ID connected to Wassenger (24 character hexadecimal string)
fromDatestringoptionalStart date (for by_date_range and archived actions)
toDateanyoptionalEnd date (for by_date_range and archived actions)
activityTypestringoptionalWhich date the range applies to: last message of any side, first message ever, or last message received from the customer One of: lastMessage, firstMessage, lastInbound
limitnumberoptionalNumber of WhatsApp chats per call (max 100)
pagenumberoptionalResults page, starting at 0
sortstringoptionalResult order. Defaults to the API order (most recent activity first) One of: date:asc, date:desc, lastMessage:asc, lastMessage:desc, inbound:asc

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "get_whatsapp_chats_by_date_range",
    "arguments": {
      "device": "..."
    }
  }
}
get_whatsapp_chats_by_statusSearch and filter WhatsApp chats by their platform status (active, pending, resolved, etc.). Useful for …

Search and filter WhatsApp chats by their platform status (active, pending, resolved, etc.). Useful for workflow management and chat organization. Same as get_whatsapp_chats with action "by_status".

ParameterTypeDescription
devicestringrequiredWhatsApp device ID connected to Wassenger (24 character hexadecimal string)
statusstring[]optionalFilter by chat status (required for by_status action, optional elsewhere)
limitnumberoptionalNumber of WhatsApp chats per call (max 100)
pagenumberoptionalResults page, starting at 0
sortstringoptionalResult order. Defaults to the API order (most recent activity first) One of: date:asc, date:desc, lastMessage:asc, lastMessage:desc, inbound:asc

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "get_whatsapp_chats_by_status",
    "arguments": {
      "device": "..."
    }
  }
}
get_whatsapp_device_detailsRetrieve comprehensive detailed information about a specific WhatsApp device using its ID. Returns complete …

Retrieve comprehensive detailed information about a specific WhatsApp device using its ID. Returns complete device configuration, session status, metrics, and actionable insights. For WhatsApp Cloud API numbers it includes the health Meta reports: quality rating, messaging limit, payment problems, restrictions and the issues Meta lists with their fix. Use it to find out why messages are not going out.

ParameterTypeDescription
deviceIdstringrequiredWhatsApp device ID (24 character hexadecimal string)
includeSettingsbooleanoptionalInclude device settings and configuration
includeSessionLogsbooleanoptionalInclude recent session logs
includeMetricsbooleanoptionalInclude device metrics and statistics

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "get_whatsapp_device_details",
    "arguments": {
      "deviceId": "..."
    }
  }
}
get_whatsapp_devicesComprehensive tool to retrieve WhatsApp devices with flexible filtering options. Supports all device query …

Comprehensive tool to retrieve WhatsApp devices with flexible filtering options. Supports all device query scenarios: get all devices, filter by status/session status, search by terms, get only active/online devices, etc.

ParameterTypeDescription
statusstring[]optionalFilter by device operational statuses
sessionStatusstring[]optionalFilter by session connectivity statuses
searchstringoptionalSearch term: phone number, alias, or device ID
exactMatchbooleanoptionalWhether to use exact match for search (only applies when search is provided)
onlineOnlybooleanoptionalOnly include devices that are currently online
activeOnlybooleanoptionalOnly include active/operational devices (authorized, verified, operative)
minUptimenumberoptionalMinimum session uptime in seconds (for online devices)
limitnumberoptionalMaximum number of devices to retrieve
pagenumberoptionalPage number for pagination (0-based)
includeMetricsbooleanoptionalInclude device metrics (chat counts, contacts, etc.)
includeSettingsbooleanoptionalInclude device settings and configuration
includeSessionDetailsbooleanoptionalInclude detailed session information
includeSessionLogsbooleanoptionalInclude recent session logs

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "get_whatsapp_devices",
    "arguments": {}
  }
}
get_whatsapp_file_detailsGet detailed information about a specific uploaded WhatsApp file by ID. Returns complete file metadata …

Get detailed information about a specific uploaded WhatsApp file by ID. Returns complete file metadata including size, type, format, status, expiration, tags, and download URLs.

ParameterTypeDescription
fileIdstringrequiredFile ID (24 character hexadecimal string)

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "get_whatsapp_file_details",
    "arguments": {
      "fileId": "..."
    }
  }
}
get_whatsapp_unread_chatsRetrieve WhatsApp chats with unread messages. Essential for managing pending conversations and customer …

Retrieve WhatsApp chats with unread messages. Essential for managing pending conversations and customer support. Same as get_whatsapp_chats with action "unread".

ParameterTypeDescription
devicestringrequiredWhatsApp device ID connected to Wassenger (24 character hexadecimal string)
limitnumberoptionalNumber of WhatsApp chats per call (max 100)
pagenumberoptionalResults page, starting at 0
sortstringoptionalResult order. Defaults to the API order (most recent activity first) One of: date:asc, date:desc, lastMessage:asc, lastMessage:desc, inbound:asc
labelsstring[]optionalOnly chats carrying at least one of these labels. Use ["*"] for any label. Cannot be combined with labelsExclude

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "get_whatsapp_unread_chats",
    "arguments": {
      "device": "..."
    }
  }
}
health_checkComprehensive health check of the MCP server and connected WhatsApp devices.

Comprehensive health check of the MCP server and connected WhatsApp devices.

Takes no parameters.

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "health_check",
    "arguments": {}
  }
}
list_whatsapp_flow_responsesread-onlyexternal accessList what customers answered in a WhatsApp Form (Meta WhatsApp Flow), newest first: who answered, each …

List what customers answered in a WhatsApp Form (Meta WhatsApp Flow), newest first: who answered, each question's label and value, and when. Takes the form's id from list_whatsapp_flows (not its flowId). Only keys of the account owner or an admin can read answers.

ParameterTypeDescription
form_idstringrequiredThe form id ("id" from list_whatsapp_flows, 24 hex characters)
fromstringoptionalFirst day, YYYY-MM-DD (UTC)
tostringoptionalLast day, YYYY-MM-DD (UTC)
campaignstringoptionalOnly answers to this campaign
deviceanyoptionalOnly answers received on this number
pageintegeroptionalPage, from 0
sizeintegeroptionalAnswers per page (default 25, max 100)

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "list_whatsapp_flow_responses",
    "arguments": {
      "form_id": "..."
    }
  }
}
list_whatsapp_flowsread-onlyexternal accessList WhatsApp Flows available for a device (WABA). Returns flow id, name, status, categories and entry …

List WhatsApp Flows available for a device (WABA). Returns flow id, name, status, categories and entry screen. Use this to find a flow to send.

ParameterTypeDescription
devicestringrequiredTarget WhatsApp device ID (24 character hex string)
statusstringoptionalFilter by flow status One of: DRAFT, PUBLISHED, DEPRECATED, THROTTLED, BLOCKED

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "list_whatsapp_flows",
    "arguments": {
      "device": "..."
    }
  }
}
list_whatsapp_templatesread-onlyexternal accessRetrieve WhatsApp templates for a specific device (approved ones by default). Each template includes its …

Retrieve WhatsApp templates for a specific device (approved ones by default). Each template includes its components and the variables that must be filled in to send it. This is required for sending template-based messages.

ParameterTypeDescription
devicestringrequiredTarget WhatsApp device ID (24 character hex string)
statusstringoptionalFilter templates by status (defaults to APPROVED) One of: APPROVED, REJECTED, PENDING, DELETED
sizenumberoptionalMaximum number of templates to retrieve

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "list_whatsapp_templates",
    "arguments": {
      "device": "..."
    }
  }
}
manage_whatsapp_campaign_contactsUniversal WhatsApp campaign contacts management tool that handles all campaign recipient operations through …

Universal WhatsApp campaign contacts management tool that handles all campaign recipient operations through action-based parameters. Supports add, remove, and search operations for campaign recipients: phone numbers and groups. Essential for WhatsApp campaign recipient management. add keeps the recipients already on the campaign. On a campaign that sends a template (WhatsApp Cloud API numbers), give every variable its component exactly as on manage_whatsapp_campaigns create: body, header, header_location, button_url_N or button_copy_code_N, with N the buttonIndex that list_whatsapp_templates reports. Such a campaign only reaches phone numbers, not groups. On a campaign from a number linked by QR, each variable key fills the {{ key }} placeholder of the campaign message.

ParameterTypeDescription
campaignIdstringrequiredWhatsApp campaign ID
actionstringrequiredAction to perform on campaign contacts One of: search, add, remove
searchstringoptionalSearch contacts by phone number, name, or group ID (for search action)
targetstring[]optionalFilter by contact target: phone number or group WhatsApp ID (for search action)
kindstring[]optionalFilter by contact type (for search action)
statusstring[]optionalFilter by delivery status (for search action)
pagenumberoptionalResults page number (for search action)
sizenumberoptionalResults page size (for search action)
contactsobject[]optionalContacts to add to campaign (for add action)
phonesany[]optionalPhone numbers to remove (for remove action)
groupsany[]optionalGroup IDs to remove (for remove action)
channelsany[]optionalChannel IDs to remove (for remove action)
widsstring[]optionalWhatsApp message IDs to remove (for remove action)

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "manage_whatsapp_campaign_contacts",
    "arguments": {
      "campaignId": "...",
      "action": "search"
    }
  }
}
manage_whatsapp_campaignsUniversal WhatsApp campaign management tool that handles all campaign operations through action-based …

Universal WhatsApp campaign management tool that handles all campaign operations through action-based parameters. Supports search, create, update, start, stop, and delete operations for WhatsApp bulk messaging campaigns. Perfect for comprehensive WhatsApp marketing automation. What a campaign sends depends on the number. Its connector, reported by get_whatsapp_devices and health_check, says which kind it is: cloud for WhatsApp Cloud API, web for a number linked by QR. - WhatsApp Cloud API (WABA) numbers: a pre-approved template is required, and it only reaches phone numbers, never groups. Pass template { name, language } and give each recipient the values its variables need. Read the template first with list_whatsapp_templates: every variable it reports has a location (header, body or buttons) and, for buttons, a buttonIndex starting at 0. Send each value with its component, and for a button variable use button_url_N or button_copy_code_N with that index. - Numbers linked by QR: a message, optionally with a file. Personalize it with placeholders: {{ name }} is the recipient's name, {{ phone }} their number, and each key in a recipient's variables fills {{ key }}. For example message "Hi {{ name }}, your order {{ order }} has shipped" with variables [{ key: "order", value: "A-1043" }]. Write keys and placeholders in lowercase. A placeholder a recipient has no value for disappears from their message; {{ order | on its way }} prints the text after the bar instead. To send it: …

ParameterTypeDescription
devicestringoptionalWhatsApp device ID (required for create action)
actionstringrequiredAction to perform on WhatsApp campaigns One of: search, get, create, update, start, stop, delete, estimate_cost
beforestringoptionalFilter campaigns created before this date (for search action)
afterstringoptionalFilter campaigns created after this date (for search action)
statusstring[]optionalFilter campaigns by status (for search action)
ownerstring[]optionalFilter by owner user IDs (for search action)
phonestring[]optionalFilter campaigns by recipient phone numbers (for search action)
groupstring[]optionalFilter campaigns by group IDs (for search action)
pagenumberoptionalResults page number (for search action)
sizenumberoptionalResults page size (for search action, max 100)
campaignIdstringoptionalWhatsApp campaign ID (required for get, update, start, stop, delete actions)
namestringoptionalCampaign name (required for create action)
messagestringoptionalCampaign message, for numbers linked by QR. On a WhatsApp Cloud API number use template instead. Personalize it with {{ name }}, {{ phone }} and {{ key }} for each key in the recipients' variables
templateobjectoptionalPre-approved template to send. Required on WhatsApp Cloud API numbers, and not accepted on numbers linked by QR
formstring | object | nulloptionalA published web form (see manage_whatsapp_web_forms) sent to every recipient, each with a link of their own minted when their message goes out. On numbers linked by QR the link replaces {{form.url}} in message, or is added at its end. On WhatsApp Cloud API …
filestringoptionalUploaded file ID. On a template campaign this is the header media, and only for a template whose header is an image, video or document: on a template without a media header the API sends a header the template does not have and Meta rejects it. Upload the file …
settingsobjectoptionalCampaign delivery settings (for create/update actions)
contactsobject[]optionalCampaign recipients, for the create action only. Max 2000 per request, and the total a campaign can hold depends on the plan (100 on trial, 500 to 2000 otherwise). To add or remove recipients later use manage_whatsapp_campaign_contacts
unsubscribeobjectoptionalUnsubscribe settings (for create/update actions)
activatebooleanoptionalStart the campaign right after creating it. Needs settings.date and at least one recipient; without them the campaign is created and left as a draft
confirmPaymentIssuebooleanoptionalOnly after telling the user that Meta reports a payment problem on the number, or that it needs reconnecting: true to activate or start the campaign anyway, because they say it is already fixed or reconnected, or want to send regardless
costsobject[]optionalFor estimate_cost: one line per country of the recipients, with the template category and the number of messages. Up to 100 lines

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "manage_whatsapp_campaigns",
    "arguments": {
      "action": "search"
    }
  }
}
manage_whatsapp_channel_messagesComprehensive WhatsApp channel message management tool for retrieving and managing channel content. Perfect …

Comprehensive WhatsApp channel message management tool for retrieving and managing channel content. Perfect for monitoring channel activity and accessing channel message history. Available actions: - get: Get recent messages from a specific channel with filtering options

ParameterTypeDescription
devicestringrequiredWhatsApp device ID connected to Wassenger (24 character hexadecimal string)
actionstringrequiredAction to perform on WhatsApp channel messages One of: get
channelIdstringrequiredWhatsApp channel ID to get messages from
limitnumberoptionalNumber of recent messages to retrieve (max 100)
includeMediabooleanoptionalInclude media message details
includeDeletedbooleanoptionalInclude deleted messages in results
pagenumberoptionalPage number for pagination (0-based)
sortOrderstringoptionalSort order by timestamp One of: asc, desc
fromDatestringoptionalGet messages from this date onwards
toDateanyoptionalGet messages up to this date
messageTypesstring[]optionalFilter by specific message types

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "manage_whatsapp_channel_messages",
    "arguments": {
      "device": "...",
      "action": "get",
      "channelId": "..."
    }
  }
}
manage_whatsapp_channelsComprehensive WhatsApp channel management tool supporting all channel operations. Perfect for managing …

Comprehensive WhatsApp channel management tool supporting all channel operations. Perfect for managing channel lifecycle, membership, and content. Supports all WhatsApp channel operations through a unified action-based interface. Available actions: - list: List and retrieve channels with filtering options - get: Get detailed information about a specific channel - create: Create new channels with optional profile images - update: Update existing channel information (name, description) - search: Search for public channels by category and keywords - join: Join/follow channels via invite code or URL - leave: Leave/unfollow channels - delete: Delete channels (alias for leave) - update_image: Update channel profile images

ParameterTypeDescription
devicestringrequiredWhatsApp device ID connected to Wassenger (24 character hexadecimal string)
actionstringrequiredAction to perform on WhatsApp channels One of: list, get, create, update, search, join, leave, delete …
channelIdstringoptionalWhatsApp channel ID (required for get, update, leave, delete, update_image actions)
limitnumberoptionalNumber of results to retrieve (max 250)
pagenumberoptionalPage number for pagination (0-based)
permissionstringoptionalFilter channels by permission type (for list action) One of: admin, subscriber, owner
includestring[]optionalInclude related entities in response
sortstringoptionalSort field and order (e.g., "-createdAt", "name")
searchQuerystringoptionalText to search for in channel names and descriptions (for search action)
categorystringoptionalCategory of channels to search for (for search action) One of: recommended, trending, popular, new, featured
sortOrderstringoptionalSort order for search results One of: asc, desc
sortFieldstringoptionalField to sort search results by One of: creation_time, subscribers
countriesstring[]optionalCountry codes to filter channels by (e.g., ["US", "GB"])
namestringoptionalChannel name (required for create, optional for update)
descriptionstringoptionalChannel description (up to 2048 characters)
uploadImagebooleanoptionalWhether to upload a profile image (for create action)
imageSourcestringoptionalSource type for channel image One of: url, base64
imageUrlstringoptionalURL of image to use as channel profile picture (JPG or PNG, max 1MB)
imageDatastringoptionalBase64-encoded image data (JPG or PNG, max 1MB)
joinMethodstringoptionalMethod to join the channel (for join action) One of: code, url
inviteCodestringoptionalChannel invitation code (required if joinMethod is "code")
inviteUrlstringoptionalChannel invitation URL (required if joinMethod is "url")

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "manage_whatsapp_channels",
    "arguments": {
      "device": "...",
      "action": "list"
    }
  }
}
manage_whatsapp_chatChange a WhatsApp chat in the team inbox without sending anything to the customer: hand it to a teammate or …

Change a WhatsApp chat in the team inbox without sending anything to the customer: hand it to a teammate or department, add or remove labels, resolve or reopen it, leave an internal note, or mark it read or unread. The customer sees none of it. Your team sees the change, and your account's chat webhooks are notified. Available actions: - assign: give the chat to agentId, agentEmail or departmentId (departments need a plan that includes them). A pending chat becomes active. - unassign: take the chat off its agent and department. It goes back to pending. - add_labels / remove_labels: the labels must already exist on the number, create them first with manage_whatsapp_labels. The chat keeps any label you do not mention. - resolve: close the conversation. - reopen: back to active if someone owns the chat, pending otherwise. - add_note: private note only your team can see (2 to 6000 characters). authorId writes it as that teammate. - mark_read / mark_unread: marking a resolved chat as unread reopens it. To write to the customer, use send_whatsapp_message instead.

ParameterTypeDescription
actionstringrequiredWhat to change on the chat One of: assign, unassign, add_labels, remove_labels, resolve, reopen, add_note, mark_read …
devicestringrequiredWhatsApp number (device) ID the chat belongs to
chatstringrequiredThe chat: a phone number in international format, or its WhatsApp chat ID as returned by get_whatsapp_chats
agentIdstringoptionalTeammate user ID to assign the chat to (for assign)
agentEmailstringoptionalTeammate email to assign the chat to, instead of agentId (for assign)
departmentIdstringoptionalDepartment ID to assign the chat to (for assign). Look it up with manage_whatsapp_departments
labelsstring[]optionalLabel names (for add_labels and remove_labels)
notestringoptionalInternal note text, WhatsApp formatting allowed (for add_note)
authorIdstringoptionalTeammate user ID the note is written as. Defaults to the API key owner (for add_note)

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "manage_whatsapp_chat",
    "arguments": {
      "action": "assign",
      "device": "...",
      "chat": "..."
    }
  }
}
manage_whatsapp_contact_actionsManage WhatsApp contact blocking and unblocking operations. Handle contact blocking status with action-based …

Manage WhatsApp contact blocking and unblocking operations. Handle contact blocking status with action-based operations to control message reception from specific contacts. Contacts are identified by phone number in E.164 format, not by WhatsApp ID.

ParameterTypeDescription
actionstringrequiredAction to perform on WhatsApp contact blocking/unblocking One of: block, unblock
devicestringrequiredWhatsApp device ID connected to Wassenger (24 character hexadecimal string)
contactsstring[]requiredArray of contact phone numbers in E.164 format to block or unblock (max 50)

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "manage_whatsapp_contact_actions",
    "arguments": {
      "action": "block",
      "device": "...",
      "contacts": []
    }
  }
}
manage_whatsapp_contactsComprehensive WhatsApp contacts management with action-based operations. Supports listing, searching, …

Comprehensive WhatsApp contacts management with action-based operations. Supports listing, searching, creating, updating, deleting contacts, bulk operations, and metadata management. All contact operations including CRUD, filtering, pagination, and metadata handling in one unified tool.

ParameterTypeDescription
actionstringrequiredAction to perform on WhatsApp contacts One of: list, get, create, update, delete, bulk_create, update_metadata, upsert_metadata
devicestringrequiredWhatsApp device ID connected to Wassenger (24 character hexadecimal string)
contactWidstringoptionalWhatsApp contact ID (required for get, update, delete, update_metadata, upsert_metadata actions)
limitnumberoptionalNumber of contacts to retrieve (max 200, for list action)
pagenumberoptionalPage number for pagination (0-based, for list action)
searchstringoptionalSearch contacts by name, surname, phone, email, company, address, or notes (for list action)
typestring[]optionalFilter contacts by type (for list action)
statusstring[]optionalFilter contacts by status (for list action)
ownerstring[]optionalFilter contacts assigned to specific agents (for list action)
phonestring | any[]optionalPhone number for create action, or array of phone numbers for list filtering
widany[]optionalFilter contacts by WhatsApp IDs (for list action)
metadataKeystring[]optionalFilter contacts with specific metadata keys (for list action)
metadataValuestring[]optionalFilter contacts with specific metadata values (for list action)
afterstringoptionalFilter contacts created after this date (for list action)
beforeanyoptionalFilter contacts created before this date (for list action)
updatedAfteranyoptionalFilter contacts updated after this date (for list action)
updatedBeforeanyoptionalFilter contacts updated before this date (for list action)
includestring[]optionalInclude related entities in response
sortstringoptionalSort field and order (e.g., "-createdAt", "name", for list action)
verbositystringoptionalResponse detail level for list/get: summary = curated high-signal fields (default, token-lean); standard = broader set; full = complete contact objects (escape hatch). One of: summary, standard, full
fieldsstring[]optionalExplicit dot-path allowlist, e.g. ['wid','phone','info.email']. Overrides verbosity when set.
namestringoptionalContact first name (for create, update actions)
surnamestringoptionalContact surname/last name (for create, update actions)
titlestringoptionalContact title (Mr., Mrs., Dr., etc., for create, update actions)
kindstringoptionalContact category (for create, update actions) One of: personal, business, private
genderstringoptionalContact gender (for create, update actions) One of: male, female, other
altPhoneanyoptionalAlternative phone number (for create, update actions)
emailstringoptionalContact email address (for create, update actions)
descriptionstringoptionalContact description (for create, update actions)
birthdaystringoptionalContact birthday in YYYY-MM-DD format (for create, update actions)
timezonestringoptionalContact timezone (for create, update actions)
addressstringoptionalContact address (for create, update actions)
citystringoptionalContact city (for create, update actions)
postalCodestringoptionalContact postal code (for create, update actions)
countrystringoptionalContact country 2-letter ISO code (for create, update actions)
currencystringoptionalContact currency 3-letter ISO code (for create, update actions)
notesstringoptionalPrivate notes about the contact (for create, update actions)
companyNamestringoptionalCompany name (for create, update actions)
companyCodestringoptionalCompany code (for create, update actions)
companyTaxIdstringoptionalCompany tax ID (for create, update actions)

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "manage_whatsapp_contacts",
    "arguments": {
      "action": "list",
      "device": "..."
    }
  }
}
manage_whatsapp_deal_notesComprehensive WhatsApp deal note management tool supporting all note operations. A note is what somebody …

Comprehensive WhatsApp deal note management tool supporting all note operations. A note is what somebody wrote on a sales deal; a note that carries a due date IS a task. Perfect for managing sales notes, tracking tasks, and attaching files to deals. Supports both standalone notes and comments nested under deal history events. Available actions: - list: Retrieve all notes for a deal with filtering and metadata - create: Create a new note (optionally as a task with due date, or as a comment on a deal event) - update: Update note text, due date, completion status, or file attachments - delete: Remove a note (requires confirmation) Note: The Sales Funnel API is available on the Platform Professional subscription and above. Write endpoints return HTTP 403 when the account's plan does not include it; read endpoints are deliberately NOT plan-gated. Restricted agents (plain agent role) only ever receive their own deals, regardless of filters.

ParameterTypeDescription
actionstringrequiredAction to perform on deal notes One of: list, create, update, delete
dealIdstringoptionalDeal ID (required for all actions)
noteIdanyoptionalNote ID (required for update and delete)
textstringoptionalNote body (required for create, optional for update)
dueAtstring | nulloptionalISO 8601 date-time string. A note that has one IS a task. On update, passing null turns the task back into a plain note.
donebooleanoptionalCompletes the task (true) or reopens it (false). Update only.
eventstringoptionalId of one of the deal's own history events. Create only, set at birth and never moved. Makes the note a comment nested under that event.
filesany[]optionalIds of previously uploaded files to attach. Upload them first with the file-upload tools (POST /files). On BOTH create and update this means the COMPLETE list the note carries afterwards, never a delta: ids missing from the list are detached, and an empty …
limitintegeroptionalMaximum number of notes to return (1-200, default 50). List only.
skipintegeroptionalNumber of notes to skip (>= 0). List only.
confirmDeletionbooleanoptionalConfirmation flag required for delete action

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "manage_whatsapp_deal_notes",
    "arguments": {
      "action": "list"
    }
  }
}
manage_whatsapp_dealsComprehensive WhatsApp sales funnel deal management tool. A deal is one sales opportunity tied to a WhatsApp …

Comprehensive WhatsApp sales funnel deal management tool. A deal is one sales opportunity tied to a WhatsApp contact, sitting in one stage of one pipeline. Supports listing, retrieving, creating, updating, archiving, moving between stages, linking to chats, and fetching event history. Available actions: - list: Retrieve deals with rich filtering (pipeline, stage, status, agent, contact, device, stalled, chatStatus, unread, updatedAfter/Before, pagination) - get: Retrieve a single deal by ID - create: Create a new deal (requires pipeline, device, contactWid) - update: Update deal fields (title, amount, currency, agent, department) - stage moves are NOT here, use move_stage - archive: Archive a deal (frees the contact's open-deal slot, preserves as sales history) - move_stage: Move a deal to another stage (requires previousStage for atomic compare-and-swap) - link_chat: Link a deal to a WhatsApp conversation by contactWid - events: Fetch deal event history (limit, skip) Important notes: 1. move_stage requires previousStage - the stage the client last saw. The server performs an atomic compare-and-swap and answers 409 when it no longer matches. Always read the deal first (action: 'get') and pass its current stage value. 2. Only ONE open deal may exist per contact per pipeline. The API answers 409 otherwise, and the check spans the @c.us/@lid identity equivalence. 3. Restricted agents (plain agent role) only ever see their own deals, regardless of filters. 4. Write operations …

ParameterTypeDescription
actionstringrequiredAction to perform on deals One of: list, get, create, update, archive, move_stage, link_chat, events
dealIdstringoptionalDeal ID (required for get, update, archive, move_stage, link_chat, events)
pipelineanyoptionalFilter by pipeline ID
stagestringoptionalStage ID within the pipeline
statusstringoptionalDeal status filter (defaults to open) One of: open, won, lost, archived
agentany | nulloptionalAssigned agent user ID. Filter value on list; on update, pass null to unassign
unassignedbooleanoptionalOnly deals with no agent (cannot be combined with agent)
contactstringoptionalDeals for one contact (spans @c.us/@lid identity equivalence)
deviceany | any[]optionalWhatsApp device ID. A single ID when creating a deal; one or more IDs when filtering a list
stalledstringoptionalDeals stuck in their stage (requires pipeline) One of: true, false, sla, 1w, 1m, 3m, 6m
updatedAfterstringoptionalISO 8601 date-time, e.g. 2026-08-01T00:00:00.000Z (half-open range [after, before))
updatedBeforestringoptionalISO 8601 date-time, e.g. 2026-08-01T00:00:00.000Z (half-open range [after, before))
chatStatusstringoptionalState of the deal's WhatsApp conversation (requires pipeline, only for open deals) One of: removed, banned, archived, muted, pending, active, resolved, none
unreadbooleanoptionalOnly deals whose conversation has unread messages
pageintegeroptionalPage number (1-based)
sizeintegeroptionalPage size (default 50)
contactWidanyoptionalWhatsApp ID of the contact (required for create and link_chat)
chatWidanyoptionalWhatsApp ID of the chat the deal was created from
titlestringoptionalDeal title (defaults to contact name)
amountnumber | nulloptionalDeal amount. On update, pass null to clear it
currencystring | nulloptionalISO 4217 currency code. Defaults to the pipeline currency; on update, pass null to clear it
departmentany | nulloptionalDepartment ID. On update, pass null to clear it
cardobjectoptionalDisplay-only card seed
previousStageanyoptionalThe stage the client last saw (required for move_stage). Must be the current stage value from a prior get. Server answers 409 if stale.
lostReasonstringoptionalReason for losing the deal (only meaningful when moving to a lost stage)
limitintegeroptionalNumber of events to return (default 50)
skipintegeroptionalNumber of events to skip
confirmDeletionbooleanoptionalConfirm deal archiving (required for archive action)

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "manage_whatsapp_deals",
    "arguments": {
      "action": "list"
    }
  }
}
manage_whatsapp_departmentsComprehensive WhatsApp department management tool supporting all department operations. Perfect for …

Comprehensive WhatsApp department management tool supporting all department operations. Perfect for organizing team structure, managing agent assignments, and customizing department appearance. Supports all WhatsApp department operations through a unified action-based interface. Available actions: - list: List and retrieve all departments with complete information - create: Create new departments with agents, colors, and icons - update: Update existing department information and agent assignments - delete: Delete departments (removes department but preserves agent assignments)

ParameterTypeDescription
devicestringrequiredWhatsApp device ID connected to Wassenger (24 character hexadecimal string)
actionstringrequiredAction to perform on WhatsApp departments One of: list, create, update, delete
departmentIdstringoptionalDepartment ID (required for update, delete actions)
namestringoptionalDepartment name (required for create, optional for update)
colorstringoptionalDepartment color for visual identification One of: ruby, tomato, orange, sunflower, bubble, rose, poppy, rouge …
iconstringoptionalDepartment icon identifier One of: briefcase, users, user-tie, chart-bar, clipboard-list, comments, headset, user-cog …
descriptionstringoptionalDepartment description (max 300 characters)
agentsstring[]optionalArray of agent IDs to include in the department (required for create, optional for update)

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "manage_whatsapp_departments",
    "arguments": {
      "device": "...",
      "action": "list"
    }
  }
}
manage_whatsapp_group_participantsUniversal WhatsApp group participants management tool that handles all participant operations through …

Universal WhatsApp group participants management tool that handles all participant operations through action-based parameters. Supports add, remove, promote, demote, and approval management operations. Essential for WhatsApp group moderation.

ParameterTypeDescription
devicestringrequiredWhatsApp device ID connected to Wassenger (24 character hexadecimal string)
groupIdstringrequiredWhatsApp group ID
actionstringrequiredAction to perform on group participants One of: add, remove, promote, demote, get_pending, approve, reject
participantsobject[]optionalParticipants to add with admin status (for add action)
phonesany[]optionalPhone numbers of participants (for remove, promote, demote, approve, reject actions)
allbooleanoptionalApply action to all participants/pending members (for remove, approve, reject actions)

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "manage_whatsapp_group_participants",
    "arguments": {
      "device": "...",
      "groupId": "...",
      "action": "add"
    }
  }
}
manage_whatsapp_groupsUniversal WhatsApp group management tool that handles all group operations through action-based parameters. …

Universal WhatsApp group management tool that handles all group operations through action-based parameters. Supports search, create, update, join, leave, and invite management operations. Perfect for comprehensive WhatsApp group administration.

ParameterTypeDescription
devicestringrequiredWhatsApp device ID connected to Wassenger (24 character hexadecimal string)
actionstringrequiredAction to perform on WhatsApp groups One of: search, get, create, update, join, leave, get_invite, revoke_invite
kindstring[]optionalFilter groups by type (for search action)
pagenumberoptionalResults page number (for search action)
sizenumberoptionalResults page size (for search action)
searchstringoptionalSearch groups by name or description (for search action)
statusstring[]optionalFilter groups by status (for search action)
includestring[]optionalInclude additional data in response
sortstringoptionalSort field and order (for search action)
groupIdstringoptionalWhatsApp group ID (required for get, update, leave, get_invite, revoke_invite actions)
namestringoptionalGroup name (required for create action)
descriptionstringoptionalGroup description (for create/update actions)
participantsobject[]optionalGroup participants (required for create action)
permissionsobjectoptionalGroup permissions and settings (for create/update actions)
ephemeralstringoptionalEphemeral messages duration (for create/update actions) One of: off, 24h, 7d, 90d
codestringoptionalGroup invitation code (for join action)
urlstringoptionalGroup invitation URL (for join action)
removebooleanoptionalRemove group from chat list after leaving (for leave action)

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "manage_whatsapp_groups",
    "arguments": {
      "device": "...",
      "action": "search"
    }
  }
}
manage_whatsapp_labelsComprehensive WhatsApp label management tool supporting all label operations. Perfect for organizing …

Comprehensive WhatsApp label management tool supporting all label operations. Perfect for organizing conversations with color-coded categories and managing chat organization systems. Supports both WhatsApp Business and platform-specific labels. Available actions: - list: Retrieve all available labels with filtering and metadata - create: Create new labels with custom colors and descriptions - update: Update existing label colors and descriptions - delete: Remove labels and cleanup associated chats

ParameterTypeDescription
devicestringrequiredWhatsApp device ID connected to Wassenger (24 character hexadecimal string)
actionstringrequiredAction to perform on WhatsApp labels One of: list, create, update, delete
namestringoptionalLabel name (required for create, update, delete actions)
includeMetadatabooleanoptionalInclude additional label metadata like scope and active status
filterByScopestringoptionalFilter labels by scope for list action One of: chat, wa
activeOnlybooleanoptionalOnly return active labels (for list action)
colorstringoptionalLabel color from predefined palette (required for create, optional for update) One of: ruby, tomato, orange, sunflower, bubble, rose, poppy, rouge …
descriptionstringoptionalLabel description (optional for create, required for update)
confirmDeletionbooleanoptionalConfirm label deletion and removal from all chats/contacts (required for delete action)

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "manage_whatsapp_labels",
    "arguments": {
      "device": "...",
      "action": "list"
    }
  }
}
manage_whatsapp_message_interactionsManage WhatsApp message interactions including replies, forwards, reactions, and poll voting. Handle all …

Manage WhatsApp message interactions including replies, forwards, reactions, and poll voting. Handle all message interaction operations with action-based approach for comprehensive message engagement functionality.

ParameterTypeDescription
actionstringrequiredAction to perform for WhatsApp message interactions One of: reply, forward, reaction, vote
chatstringrequiredWhatsApp chat ID (e.g., 1234567890@c.us for phone numbers, 123456789000000000@g.us for groups, 123456789000000@newsletter for WhatsApp channels)
messagestringoptionalReply message content (required for reply action)
quotestringoptionalMessage ID to reply to (required for reply action)
selectIdstringoptionalID of selected button/list option when replying to interactive messages (for reply action)
forwardobjectoptionalForward message details (required for forward action)
reactionstringoptionalEmoji reaction to send, use "-" to remove reaction (required for reaction action)
reactionMessagestringoptionalMessage ID to react to (required for reaction action)
voteobjectoptionalVote details (required for vote action)
devicestringoptionalTarget WhatsApp device ID (24 character hex string) used for message delivery. Only required if you have multiple WhatsApp numbers connected. Use MCP tool "get_whatsapp_devices" to retrieve a list of available devices.
agentstringoptionalAgent ID (24 character hex string)
referencestringoptionalCustom reference ID for message tracking
idempotencyKeystringoptionalYour unique key for this message, 6 to 36 characters (a UUID works). Reuse the same key when retrying the same message: the API then answers 409 Conflict with the id of the message already created instead of sending it twice. Use a new key for every different …

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "manage_whatsapp_message_interactions",
    "arguments": {
      "action": "reply",
      "chat": "..."
    }
  }
}
manage_whatsapp_pipelinesComprehensive sales pipeline management tool for the WhatsApp sales funnel (CRM). A pipeline is a sales …

Comprehensive sales pipeline management tool for the WhatsApp sales funnel (CRM). A pipeline is a sales board: an ordered list of stages that deals move through, optionally fed by specific WhatsApp numbers. Use it to set up sales boards, inspect their configuration and read their headline numbers. Available actions: - list: Retrieve all sales pipelines of the account, optionally only those fed by one device - get: Retrieve a single pipeline with its full stage configuration - create: Create a new pipeline with stages, entry rules and behaviour settings - update: Update pipeline properties, stages, lost reasons or settings - delete: Remove a pipeline (refused with 409 while it still holds open deals) - summary: Per-stage deal counts and open amount totals for the board, plus won and lost totals for the last 30 days Stage ordering matters: a pipeline requires at least one open, one won and one lost stage, and the won and lost stages must come AFTER all the open ones, because a deal advances to the next open stage by position. When no stages are supplied on create, a sensible default ladder is seeded. Note: the sales funnel is available on the Platform Professional subscription and above. Write operations answer 403 on a plan without it, while reads stay available so an account that downgrades keeps access to its funnel data.

ParameterTypeDescription
actionstringrequiredAction to perform on WhatsApp sales pipelines One of: list, get, create, update, delete, summary
pipelineIdstringoptionalPipeline ID (required for get, update, delete and summary actions)
deviceanyoptionalWhatsApp device ID: only return pipelines fed by this device (for list action)
namestringoptionalPipeline name (required for create action)
descriptionstringoptionalPipeline description
colorstringoptionalPipeline color name used for quick identification
iconstringoptionalPipeline icon identifier. Defaults to funnel-dollar One of: funnel-dollar, filter, chart-line, handshake, money-bill-wave, bullseye, flag-checkered, coins …
devicesany[]optionalWhatsApp device IDs that feed this pipeline. An empty array means all the account devices
currencystring | nulloptionalISO 4217 currency code for deal amounts. Defaults to the account currency; on update, pass null to clear it back to that default
entryobjectoptionalEntry rule configuration: how chats enter this pipeline
stagesobject[]optionalPipeline stages, in order. At least one open, one won and one lost stage are required, and the won and lost stages must come after all the open ones
lostReasonsstring[]optionalPreset lost reasons offered when a deal is lost
settingsobjectoptionalPipeline behaviour settings
confirmDeletionbooleanoptionalConfirm pipeline deletion (required for delete action)

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "manage_whatsapp_pipelines",
    "arguments": {
      "action": "list"
    }
  }
}
manage_whatsapp_queueComprehensive WhatsApp queue management tool supporting all queue operations. Perfect for monitoring queue …

Comprehensive WhatsApp queue management tool supporting all queue operations. Perfect for monitoring queue health, controlling message delivery flow, and performing bulk message operations. Supports all WhatsApp queue operations through a unified action-based interface. Available actions: - get_status: Get comprehensive queue statistics and status information - update_status: Update queue processing status (pause/active/reject/freeze) with optional force delivery - delete_messages: Delete queued messages with flexible filtering options. A call with no messageIds, phoneNumbers, groupIds or dateRange would delete every queued and scheduled message, so it is refused unless confirmEmptyQueue is true

ParameterTypeDescription
devicestringrequiredWhatsApp device ID connected to Wassenger (24 character hexadecimal string)
actionstringrequiredAction to perform on WhatsApp queue One of: get_status, update_status, delete_messages
statusstringoptionalQueue processing status (required for update_status action) One of: pause, active, reject, freeze
forcebooleanoptionalForce delivery of all queued messages with no delay for 30 minutes (only works with "active" or "reject" status)
filtersobjectoptionalFiltering options for selective message deletion (for delete_messages action)
waitForCompletionbooleanoptionalWait until all messages are deleted (may take up to 90 seconds for large queues)
confirmEmptyQueuebooleanoptionalSet to true only to delete every queued and scheduled message of the number (scheduled ones are kept if filters.skipScheduled is true). delete_messages refuses a call without messageIds, phoneNumbers, groupIds or a dateRange unless this is true

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "manage_whatsapp_queue",
    "arguments": {
      "device": "...",
      "action": "get_status"
    }
  }
}
manage_whatsapp_statusComprehensive WhatsApp status management tool supporting all status operations. Perfect for managing status …

Comprehensive WhatsApp status management tool supporting all status operations. Perfect for managing status lifecycle, publishing immediate or scheduled content, and retrieving status history. Supports all WhatsApp status operations through a unified action-based interface. Available actions: - get: Search and retrieve status history with comprehensive filtering - publish: Publish immediate status updates with text, images, or videos - schedule: Schedule status updates for future publishing with advanced timing

ParameterTypeDescription
actionstringrequiredAction to perform on WhatsApp status One of: get, publish, schedule
devicestringoptionalWhatsApp device ID (24-character hex string)
flowstringoptionalFilter by message direction (for get action) One of: inbound, outbound
minebooleanoptionalReturn only status published by your own WhatsApp number (for get action)
scheduledbooleanoptionalReturn only scheduled status to be published in the future (for get action)
searchstringoptionalSearch status by text content, contact name, or media filename (for get action)
chatstringoptionalFilter status by specific chat WhatsApp ID (for get action)
phonestringoptionalFilter status from specific phone number or WhatsApp ID (for get action)
referencestringoptionalFilter by custom reference field or set reference for publish/schedule
typestring[]optionalFilter by status content types (for get action)
ackstring[]optionalFilter by delivery status (for get action)
widstring[]optionalFilter by specific WhatsApp message IDs (for get action)
fromDatestringoptionalGet status published from this date onwards (for get action)
toDateanyoptionalGet status published up to this date (for get action)
sortOrderstringoptionalSort order by creation date (for get action) One of: asc, desc
limitnumberoptionalMaximum number of status entries to retrieve (for get action)
pagenumberoptionalPage number for pagination (for get action)
messagestringoptionalText content for status update (required for text status in publish/schedule actions)
mediaobjectoptionalMedia content (image/video) for status update (for publish/schedule actions)
fontstringoptionalFont style for text status (for publish/schedule actions) One of: helvetica, serif, norican
colorstringoptionalBackground color for text status (for publish/schedule actions) One of: red_purple, moss_green, dark_khaki, wine_red, light_taupe, goldenrod, olive_green, light_plum …
scheduleobjectoptionalSchedule options for delayed publishing (for publish action)
orderbooleanoptionalEnforce strict publication order for scheduled status (for publish action)
idempotencyKeystringoptionalUnique key to prevent duplicate status publishing (for publish action)
scheduleTypestringoptionalType of scheduling method (required for schedule action) One of: delay, delayTo, date
delaynumberoptionalDelay in seconds (for schedule action with scheduleType: delay)
delayTostringoptionalTime notation delay (for schedule action with scheduleType: delayTo) One of: 15m, 30m, 1h, 2h, 6h, 12h, 1d, 2d …
publishDateanyoptionalSpecific publish date and time (for schedule action with scheduleType: date)
strictOrderbooleanoptionalEnforce strict publication order (for schedule action)
timezonestringoptionalTimezone for date scheduling (for schedule action)

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "manage_whatsapp_status",
    "arguments": {
      "action": "get"
    }
  }
}
manage_whatsapp_teamComprehensive WhatsApp team management tool supporting all team operations. Perfect for managing team member …

Comprehensive WhatsApp team management tool supporting all team operations. Perfect for managing team member lifecycle, device access, and role assignments. Supports all WhatsApp team operations through a unified action-based interface. Available actions: - search: Search and list team members with filtering options - get: Get detailed information about a specific team member by ID - create: Create a new team member and grant them access to a WhatsApp device (requires device, email, displayName, password, role and color) - update: Update an existing team member's name, email, password, role or color - delete: Delete one or more team members from the account, choosing what happens to their assigned chats - grant_access: Grant an existing team member access to a WhatsApp device - revoke_access: Revoke a team member's access to a WhatsApp device, choosing what happens to their assigned chats Notes: - New team members are always created against a specific WhatsApp device and are granted access to it immediately. - grant_access and revoke_access operate on a single team member at a time. - delete, and revoke_access when chatAction is "reassign", require reassignTo.

ParameterTypeDescription
actionstringrequiredAction to perform on WhatsApp team members One of: search, get, create, update, delete, grant_access, revoke_access
userIdstringoptionalTeam member ID (required for get, update, grant_access and revoke_access actions)
userIdsany[]optionalArray of team member IDs to delete (required for the delete action, max 10)
emailstringoptionalTeam member email address (required for create; may be used instead of userId to identify the member for delete and revoke_access)
devicestringoptionalWhatsApp device ID (required for create, grant_access and revoke_access actions; optional filter for search)
querystringoptionalFree text search over team member name and email (for search action)
rolestringoptionalFilter by team member role for search, or the role to assign for create and update One of: admin, supervisor, agent
statusstringoptionalFilter by team member status (for search action) One of: any, active, inactive, pending, removed
idsany[]optionalRestrict search results to these team member IDs
exceptIdsany[]optionalExclude these team member IDs from search results
loginBeforestringoptionalOnly team members whose last login is before this ISO 8601 date and time
loginAfteranyoptionalOnly team members whose last login is after this ISO 8601 date and time
onlineBeforeanyoptionalOnly team members last seen online before this ISO 8601 date and time
onlineAfteranyoptionalOnly team members last seen online after this ISO 8601 date and time
pageintegeroptionalResults page number
sizeintegeroptionalMaximum number of results per page
displayNamestringoptionalTeam member display name (required for create)
passwordstringoptionalTeam member password (required for create, optional for update)
colorstringoptionalTeam member color (required for create, optional for update) One of: blue, azure, indigo, purple, pink, red, orange, yellow …
invitebooleanoptionalSend an invitation email to the new team member (for create action)
chatActionstringoptionalWhat to do with the chats assigned to the removed team member One of: unassign, reassign, resolve
reassignToanyoptionalTeam member ID to reassign chats to (required when chatAction is "reassign")
forcebooleanoptionalDelete team members even when they still have access to active WhatsApp devices (for delete action)
removebooleanoptionalAlso delete the team member from the account, not just from this device (for revoke_access action)

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "manage_whatsapp_team",
    "arguments": {
      "action": "search"
    }
  }
}
manage_whatsapp_web_form_appearancecan modifyexternal accessHow the web forms of one WhatsApp number look: business name, description, accent colour, footer, privacy, …

How the web forms of one WhatsApp number look: business name, description, accent colour, footer, privacy, terms and website links, and the logo. Actions: get, update, set_logo (an https URL or a base64 PNG/JPEG up to 1 MB), remove_logo. Changes reach open forms within about a minute. On WhatsApp Cloud API numbers, a form goes out as a template outside the 24-hour window, and campaigns there only send templates: link_templates lists the number's templates whose URL button opens a form link (with that button's index), and create_link_template creates one (UTILITY, one URL button) and submits it to WhatsApp for review. Then send it with send_whatsapp_web_form and its template argument. For WhatsApp Forms (Meta WhatsApp Flows, native in-chat forms on WhatsApp Business API numbers) use send_whatsapp_flow and list_whatsapp_flows instead.

ParameterTypeDescription
actionstringrequiredWhat to do One of: get, update, set_logo, remove_logo, link_templates, create_link_template
devicestringrequiredWhatsApp number (device) ID, 24 hex characters. Use get_whatsapp_devices to find it
namestring | nulloptionalBusiness name shown on the forms; null or "" goes back to the WhatsApp profile default
descriptionstring | nulloptionalOne paragraph under the name; null or "" goes back to the WhatsApp profile default
colorstring | nulloptionalAccent colour, #RRGGBB; null goes back to the default
footerstring | nulloptionalPlain text at the foot of every form; null or "" goes back to the WhatsApp profile default
linksobjectoptionalLegal and website links, https; null removes one
logoHiddenbooleanoptionalHide the logo without removing it
urlstringoptionalset_logo: https URL of a PNG or JPEG
imagestringoptionalset_logo: the image as base64 or a data URI
languagestringoptionalcreate_link_template: WhatsApp template language code, e.g. en_US, es, pt_BR
templateNamestringoptionalcreate_link_template: template name; web_form_link by default
textstringoptionalcreate_link_template: text above the button, without variables; a default one in the template language when left out
buttonTextstringoptionalcreate_link_template: button text, up to 25 characters

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "manage_whatsapp_web_form_appearance",
    "arguments": {
      "action": "get",
      "device": "..."
    }
  }
}
manage_whatsapp_web_form_linkscan modifydestructiveexternal accessManage web form links: one link per chat, bound to the published version of a form. Actions: create (a link …

Manage web form links: one link per chat, bound to the published version of a form. Actions: create (a link without sending it: the token and url are returned once), list (the links of a form, by state: created, sent, opened, started, submitted, expired, revoked), get, revoke, renew (move the expiry forward from now), chat (the web forms sent in one chat, with their answers). revoke answers a preview and a confirmToken first. To send a form as a message, use send_whatsapp_web_form. For WhatsApp Forms (Meta WhatsApp Flows, native in-chat forms on WhatsApp Business API numbers) use send_whatsapp_flow and list_whatsapp_flows instead.

ParameterTypeDescription
actionstringrequiredWhat to do One of: create, list, get, revoke, renew, chat
formIdstringoptionalcreate, list: the web form
linkIdstringoptionalget, revoke, renew: the link
devicestringoptionalcreate: number the link is for (needed with several numbers); list: only this number; chat: the number of the chat
chatstringoptionalcreate: the chat the link is for; list: only this chat; chat: the chat to read
phonestringoptionalcreate: the phone number the link is for; list: only this phone
contactstringoptionalcreate: the contact (chat ID or phone) the link is for
expiresInstring | integeroptionalHow long the link works: "48h", "7d", or seconds (1 hour to 90 days). The form's own setting when omitted
variablesobjectoptionalFlat values the form reads as link.<key> (keys a-z, 0-9 and _, at most 2 KB in all), e.g. { "order_id": "A-1029" }
callbackUrlstringoptionalhttps URL that receives the submission as well as the webhooks
referencestringoptionalYour own reference for this link, kept with it and its submissions
idempotencyKeystringoptionalYour unique key for this request, 6 to 36 characters (a UUID works). Reuse it when retrying: the API answers the form or link already created instead of a second one
statusstring[]optionallist: only links in these states
fromstringoptionallist: created from this day, YYYY-MM-DD (UTC)
tostringoptionallist: created until this day, YYYY-MM-DD (UTC)
pageintegeroptionalPage, from 0
sizeintegeroptionalRows per page (default 25, max 100)
confirmTokenstringoptionalToken from the preview, sent back once the user approved the change

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "manage_whatsapp_web_form_links",
    "arguments": {
      "action": "create"
    }
  }
}
manage_whatsapp_web_form_submissionsread-onlyexternal accessRead what customers answered in web forms, newest first. Actions: list (filters: form, number, chat, contact, …

Read what customers answered in web forms, newest first. Actions: list (filters: form, number, chat, contact, phone, agent, source, dates), get (one submission with every answer), export (csv or json, up to 10,000 rows; when the result is too large to show, it answers the count so you can narrow the range). Answers are personal data: show only what the user asked for. Answers marked sensitive are left out. For WhatsApp Forms (Meta WhatsApp Flows, native in-chat forms on WhatsApp Business API numbers) use send_whatsapp_flow and list_whatsapp_flows instead. (their answers: list_whatsapp_flow_responses)

ParameterTypeDescription
actionstringrequiredWhat to do One of: list, get, export
submissionIdstringoptionalget: the submission
formIdstringoptionalOnly submissions of this web form
formsstring[]optionalMore web forms to include
devicestring[]optionalOnly these numbers
chatstringoptionalOnly this chat
contactstringoptionalOnly this contact (chat ID or phone)
phonestringoptionalOnly this phone number
agentstringoptionalOnly links sent by this team member
sourcestring[]optionalOnly links created this way
statusstringoptionalOne of: complete, pending_binding
pipelinestringoptionalOnly submissions whose CRM write-back is pending or failed One of: pending, failed
fromstringoptionalSubmitted from this day, YYYY-MM-DD (UTC)
tostringoptionalSubmitted until this day, YYYY-MM-DD (UTC)
idsstring[]optionalexport: only these submissions
formatstringoptionalexport: json (default) or csv One of: json, csv
pageintegeroptionalPage, from 0
sizeintegeroptionalRows per page (default 25, max 100)
verbositystringoptionalsummary (default): the fields needed most; standard: more context; full: everything the API returns One of: summary, standard, full
fieldsstring[]optionalReturn only these dot-paths, e.g. ["id", "name", "status"]. Overrides verbosity

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "manage_whatsapp_web_form_submissions",
    "arguments": {
      "action": "list"
    }
  }
}
manage_whatsapp_web_formscan modifydestructiveexternal accessBuild and manage web forms: forms customers fill in the browser from a short link sent in a WhatsApp chat, …

Build and manage web forms: forms customers fill in the browser from a short link sent in a WhatsApp chat, with the answers coming back as structured submissions. For WhatsApp Forms (Meta WhatsApp Flows, native in-chat forms on WhatsApp Business API numbers) use send_whatsapp_flow and list_whatsapp_flows instead. Actions: list, get, create (blank, from a template, or from a definition), update (name, settings, numbers, or the whole draft), edit (operations on the draft, as { type: "addBlock", step, blockType, label, ... }), publish, archive, restore, duplicate, delete, versions, version (one published version with its answers JSON Schema), templates (the gallery), metrics, set_og_image (your own link preview image: an https URL or a base64 PNG/JPEG up to 1 MB, cropped to 1200×630), remove_og_image (back to the automatic one), set_public (a standing public link anyone can open, waform.app/m/..., bound to one number: for ads, bio links and QR codes), unset_public (turn it off). Edits change the draft only: a published form keeps serving its live version until the next publish. publish, archive, delete and an edit with confirm=true answer a preview and a confirmToken first: show the preview to the user and call again with the token once they approve. To send a form, use send_whatsapp_web_form.

ParameterTypeDescription
actionstringrequiredWhat to do One of: list, get, create, update, edit, publish, archive, restore …
formIdstringoptionalWeb form ID (id from the list action)
statusstring[]optionallist: only forms in these states
searchstringoptionallist: text in the form name
devicestring[]optionallist: forms these numbers may send. metrics: only these numbers
sortstringoptionallist: order (newest first by default) One of: date:desc, date:asc, name
pageintegeroptionalPage, from 0
sizeintegeroptionalRows per page (default 25, max 100)
verbositystringoptionalsummary (default): the fields needed most; standard: more context; full: everything the API returns One of: summary, standard, full
fieldsstring[]optionalReturn only these dot-paths, e.g. ["id", "name", "status"]. Overrides verbosity
namestringoptionalcreate, update, duplicate: form name
descriptionstringoptionalcreate, update: internal description
languagestringoptionalcreate, update: form language, e.g. en, es
definitionobjectoptionalcreate, update: a whole form definition (format 1). Prefer template on create and edit afterwards
templatestringoptionalcreate: template id from the templates action
settingsobjectoptionalcreate, update: settings such as { link: { ttlHours, afterSubmit }, submit: { successTitle, successText }, crm: { mappings, contactLabels, timelineCard } }
devicesstring[]optionalcreate, update: numbers allowed to send the form (all when empty)
idempotencyKeystringoptionalcreate: your unique key for this form, 6 to 36 characters. Reuse it when retrying: the API answers the form already created
opsobject[]optionaledit: draft operations, applied all or none, e.g. [{ "type": "addBlock", "step": "details", "blockType": "email", "label": "Your email", "required": true }]
confirmbooleanoptionaledit: true to rename or remove a key a published version holds (the API refuses those edits otherwise). It answers a preview and a confirmToken first
versionintegeroptionalversion: the published version number
langstringoptionaltemplates: language of the gallery (es, en, pt, fr, it, de)
fromstringoptionalmetrics: first day, YYYY-MM-DD (UTC)
tostringoptionalmetrics: last day, YYYY-MM-DD (UTC)
groupBystringoptionalmetrics: daily rows, or totals only One of: day, none
urlstringoptionalset_og_image: https URL of a PNG or JPEG
imagestringoptionalset_og_image: the image as base64 or a data URI
slugstringoptionalset_public: the end of the public link, e.g. acme-booking
publicDevicestringoptionalset_public: the number the public link is bound to; its appearance brands the page and it receives the leads
captchabooleanoptionalset_public: ask visitors for an invisible check when the platform has one configured (default true)
deleteSubmissionsbooleanoptionaldelete: also delete the form's submissions, links and counters
confirmTokenstringoptionalToken from the preview, sent back once the user approved the change

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "manage_whatsapp_web_forms",
    "arguments": {
      "action": "list"
    }
  }
}
pingBasic ping test to check MCP server connectivity and response time. Returns server status and timestamp.

Basic ping test to check MCP server connectivity and response time. Returns server status and timestamp.

ParameterTypeDescription
messagestringoptionalOptional message to include in the ping response

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "ping",
    "arguments": {}
  }
}
search_whatsapp_chat_filesSearch and list received files from WhatsApp chats (inbound files). These are media files that were sent to …

Search and list received files from WhatsApp chats (inbound files). These are media files that were sent to your WhatsApp number by other users. Supports filtering by chat, file type, date range, and more.

ParameterTypeDescription
devicestringrequiredWhatsApp device ID connected to Wassenger (24 character hexadecimal string)
searchstringoptionalSearch files by filename or content
typestring[]optionalFilter by file media types
chatstring[]optionalFilter by specific chat IDs
flowstringoptionalFilter by message flow direction One of: in, out, inbound, outbound
afterstringoptionalFilter files received after this date (ISO 8601 format)
beforestringoptionalFilter files received before this date (ISO 8601 format)
pageintegeroptionalPage number for pagination (0-based)
sizeintegeroptionalNumber of files to return per page
sortstringoptionalSort order for results One of: date:desc, date:asc, size:desc, size:asc

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "search_whatsapp_chat_files",
    "arguments": {
      "device": "..."
    }
  }
}
search_whatsapp_chats_by_nameSearch for WhatsApp chats by contact name, group name, phone number, company, metadata or private notes. …

Search for WhatsApp chats by contact name, group name, phone number, company, metadata or private notes. Perfect for quickly finding specific conversations. Same as get_whatsapp_chats with action "search".

ParameterTypeDescription
devicestringrequiredWhatsApp device ID connected to Wassenger (24 character hexadecimal string)
querystringoptionalFree text to search for (required for search action)
contactTypesstring[]optionalFilter by chat type (required for by_contact_type action, optional elsewhere)
limitnumberoptionalNumber of WhatsApp chats per call (max 100)
pagenumberoptionalResults page, starting at 0

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "search_whatsapp_chats_by_name",
    "arguments": {
      "device": "..."
    }
  }
}
search_whatsapp_outbound_filesSearch and list uploaded WhatsApp files with advanced filtering. Returns outbound files that have been …

Search and list uploaded WhatsApp files with advanced filtering. Returns outbound files that have been uploaded to the platform for sending as media messages. Supports extensive filtering by filename, file type, size, creation date, tags, and more.

ParameterTypeDescription
searchstringoptionalSearch files by filename, tags, or reference ID
filenamestringoptionalFilter by exact filename
formatstring[]optionalFilter by file format types
mimestring[]optionalFilter by MIME types (e.g., ["image/jpeg", "video/mp4"])
kindstring[]optionalFilter by file kinds (e.g., ["image", "video", "document"])
extstring[]optionalFilter by file extensions (e.g., ["jpg", "pdf", "mp4"])
tagsstring[]optionalFilter by file tags
statusstring[]optionalFilter by file status
permissionstringoptionalFilter by access permission level One of: public, readonly, private
originstringoptionalFilter by upload origin: upload (local file) or remote (URL) One of: upload, remote
afterstringoptionalFilter files created after this date (ISO 8601 format)
beforestringoptionalFilter files created before this date (ISO 8601 format)
minSizeintegeroptionalMinimum file size in bytes
maxSizeintegeroptionalMaximum file size in bytes
pageintegeroptionalPage number for pagination (0-based)
sizeintegeroptionalNumber of files to return per page

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "search_whatsapp_outbound_files",
    "arguments": {}
  }
}
send_whatsapp_flowexternal accessSend a published WhatsApp Form (Meta WhatsApp Flow) to a chat as a native interactive message: one message …

Send a published WhatsApp Form (Meta WhatsApp Flow) to a chat as a native interactive message: one message instead of asking question after question. Only works within the 24h customer-service window; to start a conversation, send a template whose button opens the form. Pass a token to match the answers to your own record (it comes back in the message:flow:response webhook), and data to prefill the form.

ParameterTypeDescription
devicestringrequiredTarget WhatsApp device ID (24 character hex string)
phonestringrequiredRecipient phone number in international format (E.164), e.g. +34600111222
flow_idstringrequiredThe WhatsApp Flow ID to send (flowId from list_whatsapp_flows)
ctastringrequiredText of the button that opens the form (max 30 chars)
bodystringoptionalMessage text shown above the button (max 1024 chars)
screenstringoptionalScreen to open. If omitted, the form opens on its first screen.
tokenstringoptionalYour reference for this send (an order or ticket id). It comes back with the answers.
dataobjectoptionalValues to prefill the form with, by field name
headerstringoptionalHeader text above the message (max 60 chars)
footerstringoptionalFooter text under the message (max 60 chars)
idempotencyKeystringoptionalYour unique key for this message, 6 to 36 characters (a UUID works). Reuse the same key when retrying the same message: the API then answers 409 Conflict with the id of the message already created instead of sending it twice. Use a new key for every different …

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "send_whatsapp_flow",
    "arguments": {
      "device": "...",
      "phone": "...",
      "flow_id": "...",
      "cta": "..."
    }
  }
}
send_whatsapp_messageComprehensive WhatsApp message sending with action-based operations. Supports all message types including …

Comprehensive WhatsApp message sending with action-based operations. Supports all message types including text, media, location, contact, poll, event messages, with scheduling, live delivery, expiration, agent messaging, and template support. All message sending operations unified in one tool. Scheduling: pass exactly one of deliverAt, delay or delayTo on the text, media, template, agent or scheduled actions. Leaving all three out sends the message right away. On WhatsApp Cloud API (WABA) numbers a plain text, media or agent message still needs the customer to have written within the last 24 hours at delivery time, so a reminder that lands later than that must use the template action.

ParameterTypeDescription
actionstringrequiredAction to perform for WhatsApp message sending One of: text, template, scheduled, media, location, contact, poll, event …
chatstringrequiredWhatsApp chat ID (e.g., 1234567890@c.us for phone numbers, 123456789000000000@g.us for groups, 123456789000000@newsletter for WhatsApp channels)
devicestringoptionalTarget WhatsApp device ID (24 character hex string) used for message delivery. Only required if you have multiple WhatsApp numbers connected. Use MCP tool "get_whatsapp_devices" to retrieve a list of available devices.
messagestringoptionalText message content (required for text, scheduled, live, expiring, agent, template actions)
previewUrlbooleanoptionalEnable URL preview in messages (for text, template actions)
deliverAtstringoptionalAbsolute ISO 8601 instant to deliver the message at, with a time zone (e.g. 2026-09-20T09:00:00+02:00). Must be in the future and less than a year away
delayintegeroptionalDeliver the message after this many seconds (max 31536000, a year)
delayTostringoptionalDeliver the message after a duration: 30m, 2h, 3d, 2w, 1M (max a year)
mediaobjectoptionalMedia content (required for media action)
locationobjectoptionalLocation content (required for location action)
contactsobject[]optionalArray of contacts to send, max 10 (required for contact action)
pollobjectoptionalPoll content (required for poll action)
eventobjectoptionalEvent content (required for event action)
enqueuestringoptionalMessage delivery mode (for live action) One of: never, opportunistic
expirationstringoptionalTime-to-live duration e.g. "1h", "30m", "2d" (for expiring action)
agentIdstringoptionalAgent ID for agent messaging (required for agent action)
actionsobject[]optionalActions to perform after message delivery (for agent action)
templateobjectoptionalTemplate configuration (required for template action)
orderbooleanoptionalEnsure strict message delivery order
agentanyoptionalAgent ID (24 character hex string)
referencestringoptionalCustom reference ID for message tracking
sendReadAckbooleanoptionalSend chat read acknowledgment after the message is delivered
idempotencyKeystringoptionalYour unique key for this message, 6 to 36 characters (a UUID works). Reuse the same key when retrying the same message: the API then answers 409 Conflict with the id of the message already created instead of sending it twice. Use a new key for every different …

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "send_whatsapp_message",
    "arguments": {
      "action": "text",
      "chat": "..."
    }
  }
}
send_whatsapp_web_formcan modifyexternal accessSend a published web form to a WhatsApp chat as a message with a short link. The link is minted for that chat …

Send a published web form to a WhatsApp chat as a message with a short link. The link is minted for that chat only and is put where the message says {{form.url}}, or added at the end. The customer's answers arrive as a submission (see manage_whatsapp_web_form_submissions) and in the form:submitted webhook. For WhatsApp Forms (Meta WhatsApp Flows, native in-chat forms on WhatsApp Business API numbers) use send_whatsapp_flow and list_whatsapp_flows instead. On WhatsApp Cloud API numbers a free-text message needs the customer to have written within the last 24 hours. Outside that window pass template: an approved template whose URL button opens a form link (list or create one with manage_whatsapp_web_form_appearance, actions link_templates and create_link_template). Pass an idempotencyKey: a retry with the same key is refused instead of sending the form twice.

ParameterTypeDescription
formIdstringrequiredWeb form ID (id from the list action)
devicestringoptionalNumber to send from. Needed when the account has more than one
chatstringoptionalChat ID, e.g. 34600111222@c.us (individual chats only: groups and channels cannot receive web forms)
phonestringoptionalPhone number in international format (E.164), e.g. +34600111222
messagestringoptionalMessage text; put {{form.url}} where the link goes, e.g. "Hi Maria! Please confirm your delivery: {{form.url}}". The link is appended when there is none
expiresInstring | integeroptionalHow long the link works: "48h", "7d", or seconds (1 hour to 90 days). The form's own setting when omitted
variablesobjectoptionalFlat values the form reads as link.<key> (keys a-z, 0-9 and _, at most 2 KB in all), e.g. { "order_id": "A-1029" }
callbackUrlstringoptionalhttps URL that receives the submission as well as the webhooks
referencestringoptionalYour own reference for this link, kept with it and its submissions
templateobjectoptionalWhatsApp Cloud API numbers, outside the 24-hour window: send the form as this template instead of a text. message is then ignored
idempotencyKeystringoptionalYour unique key for this message, 6 to 36 characters. Reuse it when retrying the same send: the API refuses a second message with 409 instead of sending it twice

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "send_whatsapp_web_form",
    "arguments": {
      "formId": "..."
    }
  }
}
update_whatsapp_file_metadataUpdate metadata and properties of an uploaded WhatsApp file. You can modify filename, tags, expiration time, …

Update metadata and properties of an uploaded WhatsApp file. You can modify filename, tags, expiration time, access permissions, format, and reference ID to better organize and manage your files.

ParameterTypeDescription
fileIdstringrequiredFile ID (24 character hexadecimal string)
filenamestringoptionalNew filename for the file
referencestringoptionalNew reference identifier
formatstringoptionalNew file presentation format One of: gif, ptt, native
tagsstring[]optionalNew tags for the file
messagestringoptionalDefault caption text for media messages (images/videos only)
expirationstringoptionalNew expiration time-to-live One of: 10m, 30m, 1h, 6h, 12h, 1d, 2d, 3d …
permissionstringoptionalNew access permission level One of: public, readonly, private

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "update_whatsapp_file_metadata",
    "arguments": {
      "fileId": "..."
    }
  }
}
upload_whatsapp_file_from_urlUpload a file from a remote URL to the WhatsApp platform for use in media messages. The file will be …

Upload a file from a remote URL to the WhatsApp platform for use in media messages. The file will be downloaded from the provided URL and stored securely. Returns the uploaded file details including ID for use in message sending.

ParameterTypeDescription
urlstringrequiredPublic URL from which to download file contents
filenamestringoptionalCustom filename for the uploaded file
formatstringoptionalFile presentation format (gif for videos as GIF, ptt for audio as voice note) One of: gif, ptt, native
expirationstringoptionalFile expiration time-to-live One of: 10m, 30m, 1h, 6h, 12h, 1d, 2d, 3d …
permissionstringoptionalFile access permission level One of: public, readonly, private
referencestringoptionalOptional reference identifier for file tracking
tagsstring[]optionalOptional tags for file categorization

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "upload_whatsapp_file_from_url",
    "arguments": {
      "url": "..."
    }
  }
}
validatePhoneNumbersread-onlyexternal accessValidates the format of given phone numbers according to E.164 standard and checks their potential validity. …

Validates the format of given phone numbers according to E.164 standard and checks their potential validity. Can validate up to 500 phone numbers at once.

ParameterTypeDescription
phoneNumbersstring[]requiredArray of phone numbers to validate in E.164 format (max 500)

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "validatePhoneNumbers",
    "arguments": {
      "phoneNumbers": []
    }
  }
}
verifyWhatsAppNumberExistsChecks if a given phone number is associated with an active WhatsApp account.

Checks if a given phone number is associated with an active WhatsApp account.

ParameterTypeDescription
phoneNumberstringrequiredThe phone number to verify in E.164 format

Example call (required arguments only, placeholder values):

{
  "method": "tools/call",
  "params": {
    "name": "verifyWhatsAppNumberExists",
    "arguments": {
      "phoneNumber": "..."
    }
  }
}

Prompts 48

Badge

Maintain this server? Put its live status in your README:

MCP status badge

[![MCP status](https://mcp.aianytime.net/badge/wassenger.svg)](https://mcp.aianytime.net/s/wassenger/)

Edit this entry · Report a problem

More in Marketing, content & social

Checks record what a server answered, not whether it is safe. A listing is not a security audit; read a server's source and permissions before you connect it. Add a server · JSON · llms.txt · llms-full.txt

Browse: Agents, IDEs & developer tools · Search & discovery · Knowledge, memory & context · Media & generation · Security · Finance & markets · Marketing, content & social · Cloud, ops & data · Commerce, travel & logistics · Work & productivity · No account needed · Local servers