manage_whatsapp_messagesLABSCO SUMMARY
WhatsApp work an agent can actually carry out.
The connector reaches the real messaging surface — send and reply, read and summarise history, run groups and channels, launch campaigns, watch the send queue — rather than a read-only view of it. The numbers stay on Wassenger and the agent drives them from whichever client you already use, which also means the API key in that config controls a live business inbox.
What it is
Wassenger's connector between WhatsApp numbers managed on Wassenger and MCP clients such as Claude, ChatGPT, Cursor and VS Code Copilot. The server is hosted, so a client that speaks HTTP streaming connects by URL alone; the npm package exists for clients that cannot.
What you get
- Sending and replying: manage_whatsapp_messages covers text, media, location, contact, poll, event, scheduled, live, expiring and template sends; manage_whatsapp_message_interactions covers reply, forward, reaction and poll voting.
- Conversation history and analysis: get_whatsapp_chat_messages retrieves by recency, search, date range, sender, type, ID and thread context; analyze_whatsapp_chat_messages returns statistics, delivery status and exports.
- Inbox navigation: get_whatsapp_chats by recent, unread, status, assignment, contact type, search, archived or date range, with analyze_whatsapp_chats and search_whatsapp_chats_by_name beside it.
- Groups, teams and departments: manage_whatsapp_groups, manage_whatsapp_group_participants, manage_whatsapp_team, manage_whatsapp_departments.
- Broadcasting: manage_whatsapp_channels, manage_whatsapp_channel_messages, and manage_whatsapp_status for Stories.
- Bulk sending: manage_whatsapp_campaigns, manage_whatsapp_campaign_contacts, and manage_whatsapp_queue for queue state and cleanup.
- Contacts and files: manage_whatsapp_contacts, manage_whatsapp_contact_actions, manage_whatsapp_labels, search_whatsapp_outbound_files, search_whatsapp_chat_files.
- Connection checks: get_whatsapp_devices, get_whatsapp_device_details, health_check and ping.
Requirements
A Wassenger account with a connected WhatsApp number, and an API key from the Wassenger API settings page. The key goes on the hosted URL as a key query parameter, or in an Authorization: Bearer header. Nothing is installed unless your client lacks HTTP streaming, in which case the npm package bridges it over stdio.
Setup effort
Get your endpoint, then paste it — add your endpoint to your client
USE CASES
01
Answering a customer thread
Find the chat, read what was said, and reply in the same conversation.
02
Summarising a long conversation
Pull the recent history for a contact and get statistics and delivery state over it.
03
Running a bulk send
Build the campaign, set its recipients, start it, then watch the queue drain.
04
Setting up a team group
Create the group and manage who is in it and who is an admin.
05
Checking a number is still connected
Read device status and session state before a send depends on it.
06
Organising the inbox
Label chats, maintain the contact records, and find a conversation by name.
26 tools
Listed in project docs. Your client may show a different list.
manage_whatsapp_message_interactionsget_whatsapp_chat_messagesanalyze_whatsapp_chat_messagesget_whatsapp_chatsanalyze_whatsapp_chatssearch_whatsapp_chats_by_namemanage_whatsapp_groupsmanage_whatsapp_group_participantsmanage_whatsapp_teammanage_whatsapp_departmentsmanage_whatsapp_channelsmanage_whatsapp_channel_messagesmanage_whatsapp_statusmanage_whatsapp_campaignsmanage_whatsapp_campaign_contactsmanage_whatsapp_queueget_whatsapp_devicesget_whatsapp_device_detailshealth_checkmanage_whatsapp_contactsmanage_whatsapp_contact_actionsmanage_whatsapp_labelssearch_whatsapp_outbound_filessearch_whatsapp_chat_filespingBEFORE YOU INSTALL
What to know first
Tools you get
26 tools named in the project's documentation.
Requires
- A client that can reach a remote MCP server over HTTP
- A Wassenger API key, pasted into the URL in place of YOUR_WASSENGER_API_KEY
INSTALLATION
Connect your client
Server setup
ENDPOINT URL
https://api.wassenger.com/mcp?key=<YOUR_WASSENGER_API_KEY>Add this hosted endpoint to your MCP client using the credentials listed under Requirements.
MCP Clients
VS Code
VS CODE · JSON
{
"servers": {
"wassenger": {
"url": "https://api.wassenger.com/mcp?key=<YOUR_WASSENGER_API_KEY>",
"type": "http"
}
}
}OpenAI Responses API
OPENAI RESPONSES API · JSON
{
"tools": [
{
"type": "mcp",
"server_label": "wassenger",
"server_url": "https://api.wassenger.com/mcp?key=${wassengerKey}",
"require_approval": "never"
}
]
}${wassengerKey} comes from the project's JavaScript example, where it is set with const wassengerKey = process.env.WASSENGER_API_KEY. Outside that script, put your Wassenger API key there.
