Skip to main content
Glama

Related Servers

Alternatives to Parley

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      A 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.
      4
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A 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.
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      A self-hosted WhatsApp gateway that connects a personal WhatsApp account to AI agents and applications over REST and MCP. It maintains a local message archive and enforces per-client, per-chat permissions for reading and sending messages.
      6
      GPL 3.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Self-hosted WhatsApp management over Model Context Protocol, exposing a streamable HTTP MCP endpoint with 30 tools for session/QR pairing, messaging, media storage, and optional on-CPU voice note transcription via whisper.cpp.
      MIT
    • F
      license
      Not graded
      quality
      Not graded
      maintenance
      A 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
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      A 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.
      1
      MIT

    TDQS

    A3.8/5.0

    Scored across 24 tools

    Disambiguation4/5

    Most tools target clearly distinct resources and actions: outbound messages, inbound reading, media, connections, and webhooks are cleanly separated. There is some overlap between get_notifications and list_chats with only_new/new counts, and between read_inbox and load_history, but the descriptions provide clear selection guidance.

    Naming Consistency4/5

    All tool names use snake_case and are highly readable, with a strong verb_noun pattern such as list_outbox, send_message, and create_webhook. A few names like message_status, connection_status, and search depart from that pattern, so it is not perfectly uniform.

    Tool Count3/5

    24 tools is heavy for a single MCP server, even though the domain spans messaging, media, connections, and webhooks. The surface is well organized and avoids obvious redundancy, but it sits in the 16-25 'borderline heavy' range.

    Completeness4/5

    The set covers the main messaging lifecycle: connecting accounts, sending/canceling/deleting messages, reading/searching/history/notifications, media, pacing, and webhook creation/testing/resending. Minor gaps remain, such as disconnecting or unlinking a connection and some explicit chat-level management, but core workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues