Skip to main content
Glama
Sign In
whatsapp-tools

whatsapp-tools

by craft-agent
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to whatsapp-tools

No user-submitted related servers found.

    Related Servers

    • signal-tools

      craft-agent
      A
      license
      A
      quality
      B
      maintenance
      Enables coding agents to browse chats, read and search messages, look up contacts, save received files, and send messages or files through a linked account.
      4
      1,013 npm
      MIT

    • telegram-tools

      craft-agent
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to read Telegram chats and messages, manage mirrored chats, send messages, and save or send files on the user's own account.
      -

    • tgx

      mal4i6ka
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to operate a Telegram account through the same commands as the terminal client: messaging, chat management, voice transcription, calls, stickers, and privacy settings.
      1
      MIT

    • Telegram Account MCP

      Vlislavn
      A
      license
      B
      quality
      C
      maintenance
      Lets coding agents browse a personal Telegram account locally, retrieving per-chat text history and conversations or outgoing messages by date via QR login, read-only unless message sending is explicitly enabled. API credentials from Telegram are required, and access can be restricted to specific numeric chat IDs.
      3
      MIT

    • telegram-mcp

      Shaan-alpha
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to interact with a user's Telegram account: list chats, read history, search, and send messages through Telegram's MTProto API.
      2
      MIT

    • telegram-plugin

      kartollikaa
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to read your own Telegram account via MTProto, including listing chats, searching and reading message history, resolving chats, and downloading attachments, with sending available only when explicitly enabled.
      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

    A4.2/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool owns a distinct resource: chats/messages, contacts/numbers, history backfill, sending, and account health. The one soft boundary is fetching older messages, which can be reached via whatsapp_chat_read's `next` cursor or via whatsapp_history_backfill (server-side fetch); descriptions do distinguish them but an agent could hesitate briefly.

    Naming Consistency5/5

    Uniform pattern: whatsapp_<resource>_<action> in snake_case across all five tools (chat_read, contact_read, history_backfill, message_send, account_read). The only mild oddity is that backfill uses a different verb form than read/send, but the structural convention never wavers.

    Tool Count4/5

    Five tools is a tight, well-scoped set with no filler, and each earns its place. It sits at the low end for a broad messaging domain, but given the intentional read-centric design it is reasonable rather than thin.

    Completeness3/5

    Reading (chats, search, around, contacts, account, backfill) and a single write (text send) are covered, but obvious messaging operations are absent: media/attachment sending, edit or delete message, reactions, group administration, and any chat-state mutations. The surface is coherent but leaves agents at dead ends for common WhatsApp tasks.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources