Skip to main content
Glama
ni-c

ntfy-mcp

by ni-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to ntfy-mcp

No user-submitted related servers found.

    Related Servers

    • ntfy-mcp

      Edqe14
      A
      license
      C
      quality
      D
      maintenance
      MCP server for sending notifications to ntfy.sh or self-hosted ntfy instances.
      2
      12 npm
      MIT

    • mcp-gotify

      fastmcp-me
      A
      license
      B
      quality
      D
      maintenance
      MCP server for sending Gotify push notifications to your devices.
      1
      MIT

    • ntfy-cf

      kyeshmz
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables publishing and retrieving ntfy-style notifications via MCP, supporting topics, titles, tags, priorities, and WebSocket streaming.
      MIT

    • ntfy-mcp

      teddyzxcv
      A
      license
      Not graded
      quality
      D
      maintenance
      The MCP server that keeps you informed by sending the notification on phone using ntfy.sh
      562 npm
      45
      Apache 2.0

    • Simple Ntfy MCP Server

      Aaryan-Kapoor
      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
    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.4/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool maps to a distinct action/resource: message publishing, listing, fetching, updating, deleting, marking read, plus user/access management and server/account introspection. The close pair delete_messages vs mark_messages_read is explicitly differentiated in the descriptions, so an agent can reliably pick the right tool.

    Naming Consistency5/5

    All 13 tools follow a consistent snake_case verb_noun pattern: publish_message, list_messages, get_message, create_user, delete_messages, manage_user_access, etc. Verbs are clear and predictable, and the minor singular/plural variation matches the object being acted on.

    Tool Count5/5

    13 tools is well within the ideal range for a domain-specific server. Each tool earns its place by covering a meaningful ntfy operation: message lifecycle, user administration, access control, and server introspection. There are no redundant or filler tools.

    Completeness4/5

    The message lifecycle is complete with publish, list, get, update, delete, and mark-read. User management is also solid with create, list, delete, access management, and access checking. Minor gaps include no user account update/password reset tool and no way to test write access without actually publishing, but these are workable via existing tools or the ntfy CLI.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources