Skip to main content
Glama
jevil25

WhatsApp Messaging API by Retention Stack

by jevil25
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to WhatsApp Messaging API by Retention Stack

No user-submitted related servers found.

    Related Servers

    • whatsapp-mcp

      OmarYousef95
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables sending WhatsApp messages from MCP clients using a personal WhatsApp account via WebSocket protocol, without needing the Business API or browser automation.
      27 npm
      MIT

    • whatsapp-mcp

      vimal-v-2006
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents and MCP clients to read and send WhatsApp messages and media, search chats, and manage contacts and groups after a one-time QR pairing.
      27 npm
      MIT

    • WhatsApp MCP

      ionutsss1
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to read, search, and send personal WhatsApp messages and files through a locally linked device.
      27 npm
      MIT

    • WhatsApp MCP

      mcp-dir
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables connecting a personal or business WhatsApp account via QR pairing and then sending/reading messages, managing chats, contacts, groups, and searching message history through MCP tools.
      MIT

    • personal-whatsapp-mcp

      Gnaneshdivi
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables connecting a personal WhatsApp number to any MCP client, providing tools to send, search, and manage WhatsApp messages, with an optional auto-reply feature.
      17 PyPI
      4
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools target distinct actions: session creation/auth vs. sending messages vs. contact checks. There is slight overlap between list_sessions and get_session_status, since list_sessions may reveal statuses too, but the descriptions keep them reasonably separated.

    Naming Consistency5/5

    All tool names follow a clear lowercase snake_case verb_noun pattern: list_sessions, create_session, get_qr_code, send_text_message, etc. The naming is predictable and consistent across the set.

    Tool Count5/5

    Nine tools is well-scoped for a WhatsApp messaging API: session lifecycle management, authentication, contact validation, and message sending. Each tool serves a clear purpose without excessive redundancy.

    Completeness4/5

    The core workflow is covered: create and authenticate sessions, check contacts, and send text/image/file messages. Minor gaps exist such as no delete/stop session tool and no video/audio sending, but the essential use cases are supported.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources