Skip to main content
Glama

Related Servers

Alternatives to Cue

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to request human decisions and send notifications through chat platforms like Slack and WhatsApp, with ephemeral in-memory pending requests and no central backend.
      2
      22 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Human-in-the-loop approvals and notifications for AI agents via WhatsApp. Enables Cursor, Claude Code, and autonomous AI agents to reach users away from their computers.
      53 npm
      ISC
    • A
      license
      Not graded
      quality
      B
      maintenance
      Let AI agents notify you on Slack, Telegram, email, SMS, or push via an Alphorn webhook.
      383 npm
      AGPL 3.0
    • A
      license
      A
      quality
      A
      maintenance
      Enables agents and applications to send notifications through configurable channels such as Telegram or a JSONL file, with queued delivery, status tracking, idempotency, and event-based routing.
      2
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to reach users on their phone through push notifications, and to raise urgent, escalating alarms that fall back to a voice call until someone acknowledges. It also ships hooks that notify users automatically when Claude Code or Codex needs input or finishes a turn.
      3
      10 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      A lightweight notification service that sends webhooks when AI agents complete tasks. Supports multiple providers like Discord, Slack, Teams, Feishu, and Ntfy.
      1
      7 npm
      4
      MIT

    TDQS

    A4.6/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action, and descriptions explicitly cross-reference to prevent confusion (e.g. send_event vs send_message, get_event vs get_message, explain vs preview_template). The send/get pairs operate on different entities (events vs messages), so an agent can reliably select the right tool.

    Naming Consistency4/5

    Names follow a predictable snake_case verb_noun pattern (list_templates, send_message, get_approval, etc.) with consistent list/get/send/request/preview prefixes. The only deviation is 'explain', a bare verb that breaks the pattern, though it remains clear.

    Tool Count5/5

    10 tools is well within the ideal 3-15 range for an agent-facing notification platform, and each tool covers a distinct operation (send, inspect, dry-run, approvals). No tool feels redundant or missing from a count perspective.

    Completeness4/5

    The surface covers core agent workflows: templates (list, preview), sending (event, message), inspection (event, message, list), approvals (request, get), and dry-run (explain). Minor gaps exist—no list_events, list_approvals, or message cancellation—but agents can work around these for most tasks.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues