waha-fast-mcp
Related Servers
Alternatives to waha-fast-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables LangChain ReAct and deep agents to manage WhatsApp sessions, chats, contacts, and messages—including sending text, images, and files—through MCP tools backed by a local WAHA instance.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible AI clients to work with self-hosted, linked WhatsApp accounts by exposing eight tools for listing sessions, chats, contacts and groups, reading message history, checking numbers, inspecting account details, and sending text messages.MIT
- FlicenseNot gradedqualityDmaintenanceOpenWA MCP server that bridges AI agents to the OpenWA WhatsApp API, exposing 40 tools for sessions, messages, contacts, groups, and webhooks so agents can read and send WhatsApp messages through a self-hosted OpenWA gateway.-
- AlicenseBqualityBmaintenanceEnables sending messages, images, documents and more on WhatsApp directly from any MCP-compatible AI, with tools for chat management, groups, and webhooks.371MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to pair multiple self-hosted WhatsApp accounts via QR and read chats, contacts, messages, and groups, as well as send text or attachments from an explicitly selected account through standard MCP transports with scoped credentials.GPL 3.0
- FlicenseNot gradedqualityNot gradedmaintenanceEnables WhatsApp automation through MCP protocol, allowing users to manage sessions, send messages, handle groups/communities, and access contacts through natural language interactions with AI agents.7 npm-
TDQS
Scored across 18 tools
Most tools target a distinct resource+action (sessions, chats, messages, media). The only mild overlaps are waha_get_session vs waha_get_me (the former already reports the linked account) and waha_send_image vs waha_send_file, which differ only by media type and are well described.
Every tool uses the waha_ prefix followed by a consistent snake_case verb_noun pattern (list_sessions, get_chat, send_text, mark_chat_read). No mixed conventions or casing deviations.
18 tools is at the upper edge but each maps to a concrete WhatsApp operation across sessions, chats, messages, and contacts. Nothing is clearly redundant, though a couple of convenience tools (waha_get_me, waha_take_screenshot) could be folded into existing calls.
Session lifecycle (create/start/stop/list/get), chat reading, message sending across three media types, and presence/contact lookups are covered. Gaps remain: no session delete/logout despite stop hinting data is retained, and no message deletion or edit, which agents may need for full lifecycle control.