Skip to main content
Glama
IndyukovAnton

notification-mcp

Related Servers

Alternatives to notification-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to send structured notifications to recipients via configurable channels (initial SMTP provider) without exposing delivery addresses or credentials, with tools for listing recipients, listing channels, and sending notifications.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables scheduled AI workflows to route notifications to QQ and Telegram via REST, MCP, or Gmail, with retries and audit, without the relay calling paid LLM APIs.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Unified notification MCP server with 36 tools to send messages across 23 channels — Email, SMS, Slack, Telegram, Discord, Teams, WhatsApp, Firebase Push, and more.
      5
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables sending messages and scheduling reminders through multiple platforms including Telegram and Feishu. Supports real-time messaging and cron-based scheduled notifications with comprehensive logging and error handling.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI coding agents to send structured Telegram notifications for events like questions, plan_ready, final, attention_needed, and error.
      MIT

    TDQS

    A3.7/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are clearly distinct: notify creates/queues a notification, while notification_status reads its delivery state. There is no overlap in purpose or ambiguity about which to call.

    Naming Consistency3/5

    The names are readable and individually clear, but they follow different conventions: 'notify' is a bare verb while 'notification_status' is a noun phrase without an action prefix. This is a minor inconsistency rather than chaotic naming.

    Tool Count3/5

    Two tools is on the thin side for a notification server, but the pair covers the essential send-and-check workflow without unnecessary bloat. It feels slightly under-scoped but not unusably so.

    Completeness4/5

    The basic lifecycle of queueing and checking delivery status is covered, and the details around idempotency and state are thoughtfully described. Missing capabilities like canceling a queued notification or confirming read receipt are notable but not fatal gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues