Skip to main content
Glama
tmgr-dev

tmgr-notify

Official
by tmgr-dev

Related Servers

Alternatives to tmgr-notify

No user-submitted related servers found.

    Related Servers

    • 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.
      60 npm
      ISC
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables voice-driven control of coding agents via Claude on your phone, allowing status checks, stand-ups, sending prompts, and receiving push notifications when agents finish or need decisions.
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to send push alerts to your phone via Blipr, useful for notifying when tasks complete, builds break, or approvals are needed.
      5
      361 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to send push notifications and interactive alerts to iPhone and Mac devices via the BotBell app. It allows AI to receive user replies and manage notification bots for tasks like alerts, reminders, and remote approvals.
      2
      7 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables an AI agent to place outbound phone calls through the user's own Twilio account, delivering a spoken message or asking a single question and returning the recipient's transcribed reply to the agent. It exposes just two tools—one-way notifications and one-question calls to a fixed, preconfigured number with built-in rate limits and guardrails.
      28 PyPI
      1
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to send push notifications through the kweenkl service. Allows users to receive contextual notifications from their AI when tasks are complete or important events occur.
      1
      10 npm
      MIT

    TDQS

    B3.4/5.0

    Scored across 3 tools

    Disambiguation4/5

    notify_user and alarm both push to the user's phone, so there is some surface overlap, but the descriptions sharply delineate when to use each (routine vs. urgent incident escalation). alarm_status is clearly a distinct read/check operation tied to the alarm tool.

    Naming Consistency3/5

    notify_user follows a verb_noun pattern, but alarm is a bare noun and alarm_status is noun_noun. The convention is mixed, though all names remain readable and inferable from their descriptions.

    Tool Count4/5

    Three tools is a tight, well-scoped set for a notification/escalation service: one soft notify, one hard escalation, one status check. It is slightly lean but each tool clearly earns its place.

    Completeness3/5

    The core lifecycle (notify, escalate, check status) is covered, but there is no tool to cancel/resolve an alarm, explicitly acknowledge it, or list past notifications/alarms. Agents must rely on out-of-band phone interaction to close out an escalation.