Skip to main content
Glama
brendandebeasi

Zappy MCP

by brendandebeasi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Zappy MCP

No user-submitted related servers found.

    Related Servers

    • Zapr WhatsApp MCP Server

      fcavalcantirj
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables sending WhatsApp messages through Claude Desktop and other MCP-compatible LLMs. Supports single and bulk messaging, phone number validation, and session management via the zapr.link service.
      MIT

    • wa-web-mcp

      myi1
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that lets Claude read and send WhatsApp messages using a genuine WhatsApp Web client behind a code-enforced human-behavior middleware for safety.
      -

    • claude-whatsapp-mcp

      ferazfhansurie
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude Code to interact with WhatsApp for reading messages, sending replies, and searching contacts through the Model Context Protocol. It uses whatsapp-web.js to facilitate local connection management with QR code authentication and session persistence.
      4
      MIT

    • whatsapp-mcp

      nelcolon
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to read, search, and reply to your personal WhatsApp messages by linking as an extra device, with support for chat history, full-text search, media downloads, and sending messages or files.
      35 npm
      MIT

    • WhatsApp MCP Server

      Skael-GmbH
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to read and send WhatsApp messages through a self-hosted REST API, supporting multi-user sessions, media, groups, contacts, and webhooks.
      4 npm
      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.7/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: delete_message removes messages, get_messages retrieves messages, get_status checks connection, list_allowed shows recipients, list_chats enumerates chats, and send_message sends messages. The descriptions reinforce these distinct roles, making misselection unlikely.

    Naming Consistency5/5

    All tools follow a consistent verb_noun naming pattern (e.g., delete_message, get_messages, send_message). There are no deviations in style or convention, making the set predictable and easy to understand at a glance.

    Tool Count5/5

    With 6 tools, the set is well-scoped for managing WhatsApp interactions, covering core operations like messaging, chat/recipient listing, status checks, and deletions. Each tool earns its place without feeling excessive or insufficient for the domain.

    Completeness4/5

    The tool surface covers essential CRUD-like operations for WhatsApp messaging (send, get, delete) and administrative tasks (list chats, list allowed recipients, check status). A minor gap exists in lacking update or permission modification tools, but agents can work around this for basic workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources