Skip to main content
Glama
mcp-server-notifier

mcp-server-notifier

by tuberrabbit

Related Servers

Alternatives to mcp-server-notifier

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables sending real-time and webhook notifications when AI agents complete tasks, with support for Discord, Slack, Teams, Feishu, Ntfy, and custom webhooks.
      6
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Let your AI agent notify you via email, Slack, Discord, or webhook using a single tool.
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      An MCP server that lets LLM agents dispatch native OS notifications when a task finishes. It supports cross-platform desktop notifications, task tokens for updates, mobile bridges, and quiet hours.
      2
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that lets AI agents send desktop notifications during tasks, ask for attention, and report completion. Supports macOS, Linux, and Windows, with optional webhook delivery.
      835
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Universal notification infrastructure for AI Agents. Enables Claude, Cursor, and DeepSeek to push real-time alerts to 80+ platforms (Telegram, Discord, Slack, Email) via Apprise.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to push a notification to a person's phone through channels such as Slack, ntfy, Pushover, Telegram, Discord, or email, carrying a link back to the conversation so the recipient can reply there. Runs either locally over stdio for a single operator or as a hosted multi-user service over HTTP with sign-in, per-user channel grants, and administrator-managed access.
      MIT

    TDQS

    A3.7/5.0

    Scored across 1 tool

    Disambiguation5/5

    Only one tool exists, so there is no possibility of ambiguity between tools.

    Naming Consistency5/5

    The single tool name 'notify' is appropriate for its function, and no inconsistencies exist.

    Tool Count4/5

    One tool for a notification server is slightly minimal but still reasonable for sending notifications to configured webhooks.

    Completeness3/5

    The notification tool covers the core sending operation, but lacks tools for managing webhook configurations or testing connectivity, which are notable gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues