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.
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.
- 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.
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.
One command plus a key — npx -y mcp-remote https://api.wassenger.com/mcp?key=YOUR_WASSENGER_API_KEY, then supply credentials