# teddyzxcv/ntfy-mcp [Health: Active]

**Category:** 💬 Communication  
**Repository:** https://github.com/teddyzxcv/ntfy-mcp  
**GitHub Stars:** 44  
**Views:** 4  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/teddyzxcv-ntfy-mcp

## Description
The MCP server that keeps you informed by sending the notification on phone using ntfy

## Claude Desktop Quick Installation
Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low):

```json
"mcpServers": {
  "ntfy-mcp": {
    "command": "npx",
    "args": ["-y","teddyzxcv-ntfy-mcp"],
    "env": {
      "NTFY_TOPIC": ""
    }
  }
}
```

**Requires environment variables:** `NTFY_TOPIC` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What teddyzxcv/ntfy-mcp MCP server does

The teddyzxcv/ntfy-mcp MCP server connects an MCP-compatible assistant to ntfy, a notification service with a phone app. Its purpose is narrow: deliver a notification when the assistant finishes a requested task, allowing the user to step away from the active session and return when the work is complete.

The repository describes one MCP capability, `notify_user`. The assistant must invoke that function for a notification to be sent. A prompt such as asking for a Python hello-world program and requesting a notification after completion is used as the trigger in the documented workflow.

## How it works

The project is implemented as a local Node.js process. MCP supplies the server connection and tool interface, while the server sends the notification through ntfy. The selected topic is provided through an environment variable, so the topic used by the server must match the topic subscribed to in the ntfy mobile application.

A typical flow is:

1. Clone the repository and install its npm dependencies.
2. Build the project.
3. Start the resulting MCP server through npm.
4. Configure an MCP client with the server process and `NTFY_TOPIC`.
5. Subscribe to that topic in the ntfy app.
6. Ask the assistant to notify you when a task is complete.

## Setup and configuration

The documented setup uses `git clone`, `npm install`, `npm run build`, and `npm start`. The README also shows a Cline configuration that launches `build/index.js` with Node and passes `NTFY_TOPIC` through the environment. Replace the documented topic placeholder with the topic name you intend to use; the placeholder itself is not a runnable value.

Cline's example marks `notify_user` for automatic approval. That setting is presented as recommended for the example configuration, but the server's core requirement is that the assistant can call the notification tool.

## Tools and capabilities

- Exposes the `notify_user` MCP tool.
- Sends task-completion notifications through ntfy.
- Reads the destination topic from `NTFY_TOPIC`.
- Runs locally as a built Node.js application.
- Supports the Cline configuration shown in the README.

## Limitations and notes

The teddyzxcv/ntfy-mcp MCP server does not describe a general notification history, multiple tools, scheduling, or custom notification controls. The README emphasizes that the assistant needs an explicit instruction to notify the user; custom instructions may not reliably cause the function to be called.

The provided material documents Cline but does not establish compatibility with Claude Desktop, Cursor, or Windsurf. It also does not specify authentication for ntfy, additional environment variables, or a published npm package. The repository is licensed under Apache License 2.0.

_Full upstream README: https://allmcps.com/mcp/teddyzxcv-ntfy-mcp/readme_