Skip to main content
Glama

Related Servers

Alternatives to kalagh-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables Claude to interact with WhatsApp through a unified backend API, providing 20 tools for messaging, media, groups, contacts, and chat management.
      22
      19 npm
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Turns a linked messaging account into a bidirectional bridge to a Claude Code session, sending and receiving text, media, and transcribed voice notes while an allowlist, pairing codes, and per-group policies gate every inbound message. It also lets users approve or deny the assistant's tool requests remotely with an emoji reaction and keep working across restarts via context recovery.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude to read, triage, answer, and organize personal WhatsApp conversations through a local MCP server backed by a SQLite mirror. Keeps message data on the machine and exposes tools for search, messaging, chat organization, and cleanup.
      6 npm
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Lets users drive a Claude Code session directly from WhatsApp by relaying messages, media, and voice notes in both directions, transcribing voice input, and allowing tool-permission requests to be approved or denied with an emoji reaction. Inbound traffic is gated by pairing codes, allowlists, and per-group policies, and it runs either as a linked personal device or through Meta's official Cloud API for business DMs.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables driving a Claude Code session from WhatsApp over a linked device or the official Cloud API, with bidirectional messaging, full media support, local voice-note transcription, per-group personalities, and context recovery after restarts. Access control gates every inbound message, and tool-use requests can be approved or denied remotely with an emoji reaction.
      MIT

    TDQS

    B3/5.0

    Scored across 67 tools

    Disambiguation4/5

    Tools are cleanly namespaced by domain (chats_, contacts_, messages_, channels_, logs_) and most have a single distinct action. A few boundaries are soft — e.g. messages_send versus the specialized send_media/send_contact/send_event variants, and messages_list vs messages_history vs messages_sync — but descriptions clarify the fetch-vs-store distinction.

    Naming Consistency5/5

    Every tool follows a strict snake_case namespace_verb_noun pattern (chats_add_participant, messages_send_poll, channels_request_qr). Verb choices are consistent across domains, making the set highly predictable.

    Tool Count2/5

    67 tools is very heavy and exceeds the range where an agent can hold the surface in mind comfortably. Although the domain (channels, chats, contacts, messages, media, storage, logs) is genuinely broad and most tools earn their place, the sheer granularity is excessive.

    Completeness5/5

    The surface covers full lifecycle operations: create/get/list/update/delete for chats, contacts, and channels; a rich message action set (send, reply, forward, react, edit, delete, read); plus media storage, sync, search, and logs. No obvious dead ends for the stated messaging-platform purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues