WaWarden
Related Servers
Alternatives to WaWarden
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA self-hosted WhatsApp gateway that exposes messaging capabilities via MCP, allowing AI agents to send, receive, and manage WhatsApp messages through a single-command setup with SQLite storage.1MIT
- AlicenseNot gradedqualityBmaintenanceA self-hosted WhatsApp bridge that exposes a stdio MCP server with ~20 tools for reading conversations, sending messages, managing groups, contacts, and aliases, enabling AI agents to operate WhatsApp directly.4MIT
- AlicenseNot gradedqualityCmaintenanceA self-hosted WhatsApp bridge with an AI agent enabling searchable context, message drafting, and approval workflow via MCP protocol for Claude Desktop and other MCP clients.1MIT
- FlicenseNot gradedqualityNot gradedmaintenanceA self-hosted MCP server that connects AI clients to WhatsApp via the WAHA HTTP API. It enables users to manage sessions, search contacts, and send or receive messages and media directly through natural language interfaces.2 npm-
- AlicenseNot gradedqualityBmaintenanceA secure, zero-setup WhatsApp MCP server that lets AI assistants read, search, summarize, and (with user confirmation) act on personal WhatsApp chats via a safety-focused toolset, built as a maintained successor to the abandoned whatsapp-mcp.5MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that connects AI agents to WhatsApp using the multi-device API, enabling messaging, group management, and more as a regular user.3 npm1MIT
TDQS
Scored across 6 tools
Each tool targets a distinct operation: listing chats, fetching one chat, fetching messages, searching messages, syncing changes, and sending. The boundaries between get_chat, get_messages, and search_messages are clear from their descriptions. No obvious tool-selection ambiguity.
All tools use a consistent snake_case verb_noun pattern: get_changes, get_chat, get_messages, list_chats, search_messages, send_message. The convention is predictable throughout.
Six tools is well-scoped for a chat/messaging server with read, list, search, sync, and send capabilities. Each tool appears to earn its place without redundant surface area.
Core read and send workflows are covered, but the surface lacks message edit/revoke/delete operations even though get_changes references edited and revoked messages. Chat creation or other write-side lifecycle operations are also absent, leaving notable gaps.