Wassenger

You can extend your MCP-powered assistants to control Wassenger’s WhatsApp API, enabling automated messaging, group management, analytics, and workflows directly from your AI client. This MCP server lets you run remote HTTP access or a local stdio bridge so your agent can send messages, schedule tasks, analyze conversations, and manage contacts and groups with natural language prompts.

How to use

Connect to the Wassenger MCP server using either a remote HTTP URL or a local stdio bridge. Once connected, you can issue prompts to send WhatsApp messages, manage chats and groups, schedule messages, analyze conversations, and run bulk operations. Use plain language commands like scheduling a message, summarizing a chat, or creating a group. The MCP server exposes a wide set of actions that map to WhatsApp operations, so your AI client can orchestrate complex flows without manual scripting.

How to install

Prerequisites: Node.js (18 or higher) or your MCP client environment with support for MCP servers.

Install the Wassenger MCP server via your chosen integration method. The following options are shown in code blocks you can reproduce exactly in your setup.

{
  "mcpServers": {
    "wassenger_http": {
      "type": "http",
      "url": "https://api.wassenger.com/mcp?key=YOUR_WASSENGER_API_KEY",
      "args": []
    }
  }
}

Or run a local stdio bridge using the following command and provide your API key as an argument.

{
  "mcpServers": {
    "wassenger_stdio": {
      "type": "stdio",
      "command": "npx",
      "args": ["mcp-wassenger", "API_KEY_GOES_HERE"]
    }
  }
}

Additional setup notes

If you plan to use HTTP streaming with your MCP client, you can connect directly to the Wassenger MCP server via the HTTP URL above. For environments that require a local bridge, use the stdio configuration and supply the API key.

Configuration and security

Set your Wassenger API key as an environment variable or include it in the HTTP URL as shown in the examples. Protect your API key and avoid sharing it in logs or screenshots.

If you use the HTTP method, you can provide the key in an env var for cleaner configuration.

Troubleshooting

Clear local credentials if you encounter authentication issues: delete the MCP credential directory and re-authenticate through your client.

Ensure Node.js version is 18 or higher and confirm your MCP client is configured to connect to the Wassenger MCP endpoint.

If you are behind a VPN or corporate firewall, verify that SSL certificates are accessible to your MCP client and consider pointing NODE_EXTRA_CA_CERTS to the appropriate CA bundle if needed.

Tools and endpoints

The Wassenger MCP server exposes a comprehensive set of actions for messaging, analytics, groups, campaigns, devices, contacts, files, and system utilities. You can perform operations such as sending messages, managing chats and groups, scheduling messages, analyzing conversations, and exporting data for reporting.

Usage notes

To use the HTTP method, you can place your API key directly in the URL or pass it via environment variables depending on your client’s capabilities. For local development with a stdio bridge, provide the key as part of the command arguments.

License

MIT license applies to the Wassenger MCP server.

Available tools

manage_whatsapp_messages

Universal message sending with support for text, media, location, contact, poll, event, scheduled, live, expiring, agent, and template messaging.

manage_whatsapp_message_interactions

Handle reply, forward, reaction, and poll voting actions on messages.

get_whatsapp_chat_messages

Retrieve messages with various filters like recent, by sender, by type, date ranges, and media filtering.

analyze_whatsapp_chat_messages

Provide statistics and data exports for message delivery and chat activity.

get_whatsapp_chats

Retrieve chats with actions for recent, unread, by status, by contact, and more.

analyze_whatsapp_chats

Analytics and export capabilities for chat-level metrics.

search_whatsapp_chats_by_name

Search chats by contact name, group name, or channel name.

manage_whatsapp_groups

Create, search, update, join, leave, and manage group invitations.

manage_whatsapp_group_participants

Add, remove, promote, demote participants and manage approvals.

manage_whatsapp_team

Manage team members, including device access control and CRUD operations.

manage_whatsapp_departments

List, create, update, delete departments with agent assignments.

manage_whatsapp_channels

Lifecycle operations for channels including list, create, update, search, join, leave.

manage_whatsapp_channel_messages

Retrieve messages in channels with filtering and pagination.

manage_whatsapp_status

Manage WhatsApp Status (Stories) including publish and schedule.

manage_whatsapp_campaigns

Bulk messaging campaigns: create, start, stop, update, delete.

manage_whatsapp_campaign_contacts

Manage campaign recipients with search and filtering.

manage_whatsapp_queue

Monitor and control message queues with bulk operations.

get_whatsapp_devices

List devices with status, session, and filtering options.

get_whatsapp_device_details

Obtain detailed device configuration, status, and metrics.

health_check

System health check for MCP server and connected devices.

manage_whatsapp_contacts

CRUD operations for contacts with metadata handling.

manage_whatsapp_contact_actions

Block and unblock contacts.

manage_whatsapp_labels

Label management for organizing chats and contacts.

search_whatsapp_outbound_files

Search uploaded outbound files by type, size, date, and tags.

search_whatsapp_chat_files

Search received files in chats with advanced filters.

ping

Basic connectivity check and server status.