Skip to main content
Glama
slchenchn

notify-mcp

by slchenchn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to notify-mcp

No user-submitted related servers found.

    Related Servers

    • ntfy MCP Server

      hexerei
      A
      license
      Not graded
      quality
      D
      maintenance
      Send push notifications to mobile devices via ntfy.sh from AI assistants.
      MIT

    • blipr-mcp

      applogico
      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
      15 npm
      MIT

    • ntfy-mcp

      TadMSTR
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables sending push notifications via ntfy with a single tool, allowing Claude agents to send notifications directly without shell access.
      MIT

    • ntfy-mcp

      MahdiHedhli
      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

    • MCP-Pushover Bridge

      pyang2045
      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
      12 npm
      2
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.5/5.0

    Scored across 1 tool

    Disambiguation5/5

    Only one tool exists, so there is no possibility of confusion between tools. The purpose is clearly distinct by default.

    Naming Consistency5/5

    With a single tool, naming is trivially consistent. The name 'send_notification' follows a clear verb_noun pattern.

    Tool Count3/5

    One tool is borderline appropriate. The server's scope is limited to sending notifications, which could justify a single tool, but it feels thin compared to typical MCP servers that offer multiple operations.

    Completeness2/5

    The tool only sends notifications; there are no operations for managing recipients, viewing history, or configuring channels. While the core action is covered, significant gaps exist for a complete notification system.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources