Skip to main content
Glama
gitmotion

ntfy-me-mcp

by gitmotion

Related Servers

Alternatives to ntfy-me-mcp

  • A
    license
    Not graded
    quality
    D
    maintenance
    The MCP server that keeps you informed by sending the notification on phone using ntfy.sh
    574 npm
    45
    Apache 2.0
  • A
    license
    Not graded
    quality
    A
    maintenance
    A Model Context Protocol server enabling AI systems to send real-time notifications to phones, desktops, and other devices through the ntfy publish/subscribe service.
    574 npm
    22
    Apache 2.0

Related Servers

  • A
    license
    B
    quality
    D
    maintenance
    A lightweight MCP server for sending push notifications via ntfy.sh, supporting customizable titles, priorities, tags, and action buttons.
    1
    6 npm
    7
    MIT
  • F
    license
    A
    quality
    D
    maintenance
    An MCP server that lets AI assistants send spoken audio notifications using high-quality AI voices, so you don't have to stare at the screen waiting for long tasks to finish.
    2
    -
  • A
    license
    C
    quality
    D
    maintenance
    MCP server for sending notifications to ntfy.sh or self-hosted ntfy instances.
    2
    12 npm
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    An MCP server that enables AI agents to send notifications and request user input via Discord during long-running tasks. It allows users to remotely interact with their AI assistants and provide feedback through the Discord messaging platform.
    26 npm
    2
    MIT
  • A
    license
    A
    quality
    D
    maintenance
    A local MCP server that rings a bell through your speakers to provide audible notifications when AI completes tasks or needs attention.
    2
    MIT
  • A
    license
    A
    quality
    C
    maintenance
    A lightweight MCP server that enables sending native desktop notifications with action buttons and text replies, compatible with any MCP client.
    1
    13 npm
    1
    MIT

TDQS

A3.9/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: one sends notifications, the other retrieves cached messages. There is no overlap or ambiguity in their functions.

Naming Consistency4/5

Both tools share the prefix 'ntfy_me_', but the first tool lacks a specific verb suffix (e.g., 'send') while the second has '_fetch'. The pattern is mostly consistent but has a minor deviation.

Tool Count4/5

With only two tools, the set is minimal but appropriate for the narrow scope of sending and fetching notifications. It feels slightly thin but not unreasonable for a simple domain.

Completeness3/5

The tool set covers the basic operations of sending and retrieving notifications, but lacks additional expected functionality such as deleting or managing topics, leaving some gaps for full lifecycle management.

Maintenance

ActivityInactive
ResponsivenessResponsive