LABSCO SUMMARY

The run tells you it is done instead of you going back to check.

Priority, tags and an attached link mean a finished build and a failed one do not land on your phone looking identical. The fetch side is what makes this more than a webhook — the topic keeps its messages, and you can search them later by title, tag, priority or time window in the same session that sent them.

What it is

Two tools over an ntfy topic: one publishes a notification to it, the other reads the topic's cached messages back.

What you get

A notification published to your topic with a title, body and priority
Tags, markdown formatting, a URL and action buttons attached to that notification
Cached messages fetched back from the topic
History narrowed by message text, title, tags, priorities, a since window, or one messageId
A topic, server url and accessToken passable per call, so one install can address more than the topic in its environment

Requirements

An ntfy topic in NTFY_TOPIC. NTFY_URL points at a self-hosted server, and NTFY_TOKEN carries the credential when the topic is protected.

Setup effort

One command — npm install -g ntfy-me-mcp

See installation options

USE CASES

01

Getting told when a long run finishes

The last step of a slow job publishes to your topic with a title and a priority, so a completed run and a failed one do not arrive looking the same on your phone.

ntfy_me

02

Sending yourself something you will want to open later

A notification can carry a URL and action buttons, and render its body as markdown, which makes it a way to hand a link or a next step from the machine to the phone.

ntfy_me

03

Finding the alert you missed

The topic keeps its messages, so the one that arrived overnight can be found again by title, body text, tag, priority or a since window without opening the ntfy app.

ntfy_me_fetch

2 tools

Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.

`ntfy_me`

Send a notification to the user via ntfy. Use this tool when the user asks to 'send a notification', 'notify me', 'send me an alert', 'message me', 'ping me', or any similar request. This tool is perfect for sending status updates, alerts, reminders, or notifications about completed tasks.

BEFORE YOU INSTALL

What to know first

Tools you get

2 tools when we connected.

Requires

npx on PATH

Where it runs

All 5 documented clients run the server on your machine.

CONTEXT COST

Light Standing cost

Rated by the size of the 2 tool definitions that ride along on every turn, not by how many there are

INSTALLATION

Connect your client

Server setup

TERMINAL

npm install -g ntfy-me-mcp

MCP Clients

Claude Code

CLAUDE CODE · JSON

{
  "mcpServers": {
    "ntfy-me-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "ntfy-me-mcp"
      ],
      "env": {
        "NTFY_TOPIC": "<YOUR_NTFY_TOPIC>",
        "NTFY_URL": "https://ntfy.sh",
        "NTFY_TOKEN": "${NTFY_TOKEN}"
      }
    }
  }
}

OpenCode

OPENCODE · JSON

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ntfy-me-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "ntfy-me-mcp"
      ],
      "environment": {
        "NTFY_TOPIC": "<YOUR_NTFY_TOPIC>",
        "NTFY_URL": "https://ntfy.sh"
      }
    }
  }
}

GitHub Copilot

GITHUB COPILOT · JSON

{
  "mcpServers": {
    "ntfy-me-mcp": {
      "type": "local",
      "command": "npx",
      "args": [
        "-y",
        "ntfy-me-mcp"
      ],
      "env": {
        "NTFY_TOPIC": "<YOUR_NTFY_TOPIC>",
        "NTFY_URL": "https://ntfy.sh",
        "NTFY_TOKEN": "<YOUR_NTFY_TOKEN>"
      },
      "tools": [
        "*"
      ]
    }
  }
}

VS Code

VS CODE · JSON

{
  "inputs": [
    {
      "type": "promptString",
      "id": "ntfy_token",
      "description": "Ntfy Token",
      "password": true
    }
  ],
  "servers": {
    "ntfy-me-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "ntfy-me-mcp"
      ],
      "env": {
        "NTFY_TOPIC": "<YOUR_NTFY_TOPIC>",
        "NTFY_URL": "<YOUR_NTFY_URL>",
        "NTFY_TOKEN": "${input:ntfy_token}"
      }
    }
  }
}

Docker

DOCKER · JSON

{
  "mcpServers": {
    "ntfy-me-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "NTFY_TOPIC",
        "-e",
        "NTFY_URL",
        "-e",
        "NTFY_TOKEN",
        "gitmotion/ntfy-me-mcp:latest"
      ],
      "env": {
        "NTFY_TOPIC": "<YOUR_NTFY_TOPIC>",
        "NTFY_URL": "https://ntfy.sh"
      }
    }
  }
}

Ntfy