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