Wassenger WhatsApp MCP connector
Wassenger WhatsApp MCP connector. The mcp wassenger mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 4 defined tools rather than through you.
🚀 Supercharge your WhatsApp automation driven by AI! Send messages, summarize conversations, and manage chats using natural language from your favorite AI assistant like ChatGPT, Claude, or custom AI agents.
Wassenger is a versatile WhatsApp Team Chat and API solution for business messaging to automate anything on WhatsApp.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Everything the assistant can do here goes through one of these:
Flags — The Flags tool exposed by this serverCursor — Official Docs. The configuration file is located at ~/.cursor/mcp.jsonWindsurf — Official Docs. The configuration file is located at ~/.codeium/windsurf/mcp_config.jsonCline — Official Docs. The configuration file is located at ~/.cline/mcp_servers.jsonYou will need 4 environment variables: WASSENGER_API_KEY, WASSENGER_API, OPENAI_API_KEY, YOUR_WASSENGER_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the team communication group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP Wassenger's toolset — Flags, Cursor, Windsurf and 1 more — is a fair guide to whether it matches your workflow. It is maintained by wassengerhq; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Flags | The Flags tool exposed by this server. |
| Cursor | [Official Docs](https://docs.cursor.com/context/model-context-protocol). The configuration file is located at ~/.cursor/mcp.json. |
| Windsurf | [Official Docs](https://docs.codeium.com/windsurf/mcp). The configuration file is located at ~/.codeium/windsurf/mcp_config.json. |
| Cline | [Official Docs](https://cline.bot/docs/mcp). The configuration file is located at ~/.cline/mcp_servers.json. |
{
"mcpServers": {
"wassenger": {
"type": "http",
"url": "https://api.wassenger.com/mcp?key=YOUR_WASSENGER_API_KEY"
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| WASSENGER_API_KEY | Credential the server authenticates with. | Yes |
| WASSENGER_API | Configuration value read at startup. | Optional |
| OPENAI_API_KEY | Credential the server authenticates with. | Yes |
| YOUR_WASSENGER_API_KEY | Credential the server authenticates with. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
MCP server enabling room-based messaging between multiple agents
AI-powered access to Attio CRM. Manage contacts, companies, deals, tasks, and notes. Search records, update pipelines, and automate workflows for