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
      40 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Turns Claude Code, Claude Desktop, Cursor, Windsurf or ChatGPT into a WhatsApp operator that knows your customers, your templates, your wallet, and your funnel.
      15 npm
      3
      MIT
    • F
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables seamless integration with WhatsApp through the Model Context Protocol, featuring multi-user support and Supabase cloud storage for persistent message history and media. Users can send messages, search chat records, and manage contacts across platforms like Claude Desktop, Cursor, and OpenClaw.
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables driving a Claude Code session from a linked personal number or an official business API account, with bidirectional text and media messaging, local voice-note transcription, emoji-based remote approval of tool requests, and pairing-code allowlist access control. Also supports per-group personalities, scheduled cron tasks, and conversation context recovery after restarts.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Connects Claude to your personal Telegram and Slack accounts, letting it read real DMs, groups, channels, unread messages, and search chats, with optional sending enabled by the user.
      47 npm
      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