Skip to main content
Glama
tmgr-dev

tmgr-notify

Official
by tmgr-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to tmgr-notify

No user-submitted related servers found.

    Related Servers

    • WhatsApp MCP

      meharajM
      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.
      19 npm
      ISC

    • call-me

      radres
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to ring or text a user's actual iPhone, read a question or update aloud, and return the spoken answer back to the agent as text. Calls and messages land in a single titled thread per agent, with tools for polling results, waiting for replies, and labeling conversations.
      24
      MIT

    • herdr-voice-mcp

      lorenzkromer
      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
    • Alphorn by alphorn-dev

      Alphornofficial

      alphorn-dev
      A
      license
      Not graded
      quality
      B
      maintenance
      Let AI agents notify you on Slack, Telegram, email, SMS, or push via an Alphorn webhook.
      408 npm
      AGPL 3.0

    • lauther-mcp

      csanadymiklos
      A
      license
      A
      quality
      B
      maintenance
      Lets an AI agent ask its owner first, on their phone, before doing something irreversible: ask_approval blocks until a person answers and distinguishes DENIED from NO ANSWER, so a timeout is never read as consent. send_notification covers one-way alerts with priorities and quiet hours.
      4
      MIT
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources