Skip to main content
Glama

Related Servers

Alternatives to blipr-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to send push notifications to mobile devices via Pushover, allowing users to receive instant alerts for task completions, errors, reminders, and custom messages through their AI conversations.
      1
      6 npm
      2
      MIT
    • A
      license
      A
      quality
      D
      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
      9 npm
      1
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables AI agents to send push notifications to your phone through ntfy, with built-in security controls to prevent data exfiltration. It exposes a single tool notify_user for notifying when tasks complete or need attention.
      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
      4 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents and CLI workflows to send push notifications to a user's phone when a task finishes, fails, or needs attention. Exposes a notify_human tool with a markdown-capable message and an optional channel tag, keeping the send key out of the model's context.
      1
      738 npm
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Enables AI to send push notifications to your phone via a configurable gateway. It is a thin wrapper that posts to an Apprise push gateway.
      1
      -

    TDQS

    A4.2/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool maps to a distinct interaction mode: blocking question (ask), blocking acknowledgement (request_ack), non-blocking notification (send_alert), escalation (send_critical), and async polling (check_reply). The one soft overlap is send_alert vs send_critical, since send_alert at priority 5 does nearly the same job as send_critical; ask vs request_ack is clarified by their descriptions but still requires reading to distinguish.

    Naming Consistency4/5

    All names are lowercase snake_case and four of five follow a verb_noun shape (check_reply, request_ack, send_alert, send_critical). The bare verb `ask` is the only deviation, and it is short and unambiguous rather than genuinely inconsistent.

    Tool Count5/5

    Five tools is tightly scoped for a human-in-the-loop notification/approval service, and each one covers a genuinely different interaction pattern (ask, ack, notify, escalate, resume). Nothing looks like a redundant wrapper or a filler tool.

    Completeness4/5

    The core lifecycle — send notification, page critically, ask a question, request an ack, and resume a timed-out call — is fully covered. Minor gaps remain: no non-blocking question send (all questions block), no message listing/cancel/history, and send_alert's description doesn't state that it returns a message_id, which would make follow-up polling awkward.

    Maintenance

    ActivityActive
    ResponsivenessLimited data