Skip to main content
Glama
box7e7

mcp-notify

by box7e7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-notify

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
      17 npm
      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

    • Barkme MCP Server

      thevibeworks
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables sending iOS push notifications through the Bark service directly from Claude conversations. Supports device aliases, all Bark API parameters, and async delivery.
      67 npm
      3
      MIT

    • MCPing

      toolprint
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to send desktop notifications on macOS with rich formatting, urgency levels, and sound options.
      1
      11 npm
      1
      MIT

    • @trigv/mcp

      Trigv
      A
      license
      A
      quality
      C
      maintenance
      Enables AI clients in Cursor, Claude Code, and VS Code to send notification events to your Trigv workspace.
      1
      5 npm
      1
      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.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools target clearly distinct actions: pairing, sending, history, quota, and device management. The only mild overlap is between check_pairing_status and get_setup_status, but their descriptions differentiate an in-progress QR scan from overall readiness.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case, such as pair_device, send_notification, get_history, and remove_device. The verbs are clear and the pattern is predictable throughout.

    Tool Count5/5

    Eight tools is a well-scoped size for a notification server, covering setup, sending, status, history, quota, and device management without unnecessary redundancy. Each tool earns its place.

    Completeness5/5

    The surface covers the full notification lifecycle: pairing, setup verification, sending, history, quota monitoring, device listing, and device removal. No obvious blocking gaps exist for the stated purpose.

    Resources