Skip to main content
Glama
Aaryan-Kapoor

Simple Ntfy MCP Server

by Aaryan-Kapoor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Simple Ntfy MCP Server

npm version License: MIT

A simple MCP (Model Context Protocol) server for sending push notifications via ntfy.sh. Works seamlessly with Claude Desktop and other MCP-compatible clients.

Features

  • Zero configuration - Works out of the box with npx

  • Push notifications - Send notifications to any device via ntfy

  • Lightweight - Minimal dependencies

  • Customizable - Support for titles, priorities, tags, click actions, and action buttons

Related MCP server: ntfy-mcp

Installation & Usage

With npx (Recommended)

No installation needed! Just add to your Claude Desktop config (%APPDATA%\Claude\claude_desktop_config.json on Windows or ~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

{
  "mcpServers": {
    "ntfy": {
      "command": "npx",
      "args": ["-y", "simple-ntfy-mcp"],
      "env": {
        "NTFY_DEFAULT_TOPIC": "your-topic-name"
      }
    }
  }
}

Global Installation

npm install -g simple-ntfy-mcp

Then use in your Claude Desktop config:

{
  "mcpServers": {
    "ntfy": {
      "command": "simple-ntfy-mcp",
      "env": {
        "NTFY_DEFAULT_TOPIC": "your-topic-name"
      }
    }
  }
}

Configuration

Environment Variables

Variable

Description

Default

NTFY_DEFAULT_TOPIC

Default topic to send notifications to

(required)

NTFY_BASE_URL

Base URL of ntfy server

https://ntfy.sh

Tool: send_ntfy

Send a push notification to your configured ntfy topic.

Parameters

Parameter

Type

Required

Description

message

string

✅

The notification message

topic

string

❌

Topic to send to (uses default if not specified)

title

string

❌

Notification title

priority

number

❌

Priority level 1-5 (default: 3)

tags

string[]

❌

Array of tags/emojis

click

string

❌

URL to open when notification is clicked

actions

object[]

❌

Action buttons

Example Usage

Once configured, you can ask Claude to send you notifications:

"Send me a notification when you're done with this task"

Or be more specific:

"Send a high priority notification with the title 'Build Complete' and message 'Your project has finished building'"

Example Tool Call

{
  "message": "Your task is complete!",
  "title": "Task Completed",
  "priority": 4,
  "tags": ["white_check_mark", "rocket"],
  "click": "https://example.com"
}

What is ntfy?

ntfy is a simple HTTP-based pub-sub notification service. It allows you to send push notifications to your phone or desktop from any script or application. It's free, open source, and you can even self-host it.

To receive notifications:

  1. Install the ntfy app on your Android or iOS device

  2. Subscribe to your chosen topic

  3. Configure this MCP server with the same topic name

License

MIT

Available Tools

1 tool
send_ntfyC

Send a notification via ntfy

ParametersJSON Schema
NameRequiredDescriptionDefault
tagsNoOptional tags/emojis
clickNoURL to open when notification is clicked
titleNoOptional notification title
topicNoThe ntfy topic to send to
actionsNoAction buttons
messageYesThe message to send
priorityNoPriority level (1-5, default 3)

TDQS

C2.7/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must disclose behavioral traits such as delivery guarantees, authentication requirements, rate limits, or what happens on failure. The one-line description offers none of this, leaving the agent without any insight into the tool's side effects or operational constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, tightly worded sentence with no wasted words. It is appropriately front-loaded and concise. However, it is also under-specified in terms of content, which slightly lowers the score from 5, but it does not suffer from verbosity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has 7 parameters, no output schema, no annotations, and no sibling tools. The description provides minimal context about what ntfy is, how the notification is delivered, or any operational expectations. While the schema covers parameter details, the overall description is too sparse to fully understand the tool's purpose and behavior in a broader context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema provides 100% coverage of parameter descriptions, including details for message, topic, priority, tags, click, title, and actions. The description itself adds no parameter semantics, but the schema fully compensates, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Send') and the resource ('a notification via ntfy'), making it easy to understand what the tool does. It is not a tautology and provides enough specificity to distinguish the tool's core function, though it lacks detail about topics or parameters.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool or how it fits among alternatives. The description only states the basic action without any context about prerequisites, suitable scenarios, or alternative tools. Since there are no sibling tools or additional context, the user is left with no direction beyond the obvious.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev1.0.1
    • First observedsend_ntfy
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

B3.3/5.0

Scored across 1 tool

Disambiguation5/5

With only a single tool, there is no possibility of overlap or confusion between tools. The tool's purpose is clear and distinct from any other.

Naming Consistency5/5

The tool name follows a consistent verb_noun pattern using snake_case. The name is descriptive and matches the action it performs.

Tool Count4/5

The tool count is slightly below the typical 3-15 range, but it is entirely appropriate for the narrow scope of sending ntfy notifications. Adding more tools would be unnecessary and likely artificial.

Completeness5/5

The domain is specifically sending notifications, and this single tool fully covers that lifecycle. There are no obvious missing operations for the stated purpose.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • 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
    537 npm
    44
    Apache 2.0

  • 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
    104 npm
    73
    GPL 3.0

  • mcp-gotify

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