loginwa
OfficialRelated Servers
Alternatives to loginwa
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables AI agents to control WhatsApp, including sending messages and media, reading chats, managing groups and communities, with QR/pairing auth and session persistence.1417 npm2MIT
- FlicenseNot gradedqualityBmaintenanceOpenWA 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.-
- FlicenseNot gradedqualityBmaintenanceWhatsApp MCP server that exposes messaging, groups, contacts, and profile management as tools and resources for AI agents, supporting Baileys and Meta Cloud API.22-
- AlicenseAqualityBmaintenanceConnects AI agents to WhatsApp via the Baileys library using QR code pairing, enabling sending and receiving messages without the Meta Business API. Supports persistent sessions, access control, and message buffering.51MIT
- AlicenseNot gradedqualityBmaintenanceA 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
- AlicenseAqualityBmaintenanceMCP server for Kirimi WhatsApp API, enabling AI agents to send messages, broadcast, manage devices, and contacts.1933 npmMIT
TDQS
Scored across 8 tools
Every tool has a clearly distinct purpose: device status, OTP start/verify, message sending, and campaign management (list, get, create, send). No two tools overlap in function, so an agent can confidently select the right one based on the action needed.
Most tools follow the verb_noun pattern (get_campaign, send_message, list_campaigns, etc.), but device_status breaks the pattern by using a noun_noun form instead of something like get_device_status. This is a minor deviation from an otherwise consistent style.
With 8 tools, the set is well-scoped for a WhatsApp service covering messaging, OTP, and campaigns. Each tool earns its place without bloat or excess, staying comfortably within the ideal 3-15 range.
The core workflows are covered: send messages, handle OTP, and manage campaigns. However, campaign management lacks update/delete operations, and device management is limited to status only. These are minor gaps that agents can work around but might require external fallback.