Skip to main content
Glama
harshwasan

NTFY MCP Server

by harshwasan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to NTFY MCP Server

  • ntfy-me-mcp

    gitmotion
    A
    license
    A
    quality
    C
    maintenance
    A streamlined MCP server that enables AI assistants to send real-time notifications to your devices through the ntfy service, allowing you to receive alerts when tasks complete or important events occur.
    2
    165 npm
    74
    GPL 3.0

Related Servers

  • EchoLoopMCP

    aidevksh
    A
    license
    A
    quality
    C
    maintenance
    Enables AI agents to notify users via Telegram or Discord when tasks complete, then wait for and receive the user's reply as the next instruction within the same session.
    2
    1
    Apache 2.0

  • beacon

    ZiAn-Su
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables AI agents to communicate with humans using notify and ask semantics, supporting session management and blocking or non-blocking messages.
    4 npm
    MIT

  • ntfy MCP Server

    hexerei
    A
    license
    Not graded
    quality
    C
    maintenance
    Send push notifications to mobile devices via ntfy.sh from AI assistants.
    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

  • 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
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

A3.8/5.0

Scored across 3 tools

Disambiguation5/5

Each tool serves a distinct purpose: sending messages, changing topic, and waiting for incoming messages. No overlap, clear boundaries.

Naming Consistency3/5

Tool names mix patterns: 'send-ntfy' and 'set-ntfy-topic' use verb-ntfy, but 'wait-and-read-inbox' uses a different structure with 'and'. Inconsistent naming conventions.

Tool Count5/5

Three tools is appropriate for a focused notification server: send, configure topic, and receive. Each tool is necessary and none are redundant.

Completeness4/5

Core publish/subscribe functionality is covered with send and wait. The set-topic tool adds flexibility. A minor gap is lack of explicit unsubscribe or message history, but not essential for core use.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources