Polls the cached messages of one or more topics, oldest first. Returns "next_since": pass it back as "since" to get only what arrived after this call.

ntfy has no way to list the topics that exist — a topic is created by publishing to it. You either know the name or you find it in get_account or list_users.

Retention is whatever the instance configures (12 hours by default), so an empty result usually means "nothing recent", not "no such topic". Message bodies are shortened here; use get_message for one in full. Entries with an "updates" field revise an earlier notification rather than being new ones.

Fetches a single cached message in full, including the untruncated body, its action buttons and any attachment. Ids come from list_messages or from the result of publish_message.

Reports whether the configured credentials may SUBSCRIBE to each topic, without publishing anything.

Read the result carefully: ntfy grants read and write separately, and this endpoint tests the read side only. A write-only publishing token is denied here and can still publish perfectly well — that combination is the single most common source of confusion with ntfy.

Health, capabilities and usage of the ntfy instance. Health, config and stats are public, so this is the one tool that works before the credentials are right — a good first call after setup.

Each section is fetched independently; one that is unavailable is reported as such and does not fail the call. "version" needs an admin account, so its absence is normal.

Identity, role, tier, limits and current usage of the configured credentials. Access token values are redacted — only their labels and timestamps are shown.

Every account on the instance with its per-topic grants — the answer to "who can read or write topic X". Requires an admin account; get_server_info reports whether the current one qualifies.

Where NTFY_TOPICS restricts this server, the grants are reported against those topics only: a grant on a wildcard appears once per allowed topic it covers, and one that covers none of them is not shown at all.

Sends a notification to one or more topics.

ntfy has no multi-topic publish, so this sends one request per topic and reports each outcome separately — a rejection on one topic does not discard the ones that succeeded. Check the "ok" field per entry rather than assuming the whole call worked.

The returned id is also the notification's sequence id: pass it to update_message to revise this notification in place, which is how a progress report stays one notification instead of five.

Replaces the content of a notification already published, so subscribers see it change in place instead of receiving another one.

The sequence id is the id returned by publish_message. It only exists for cached messages: one published with "cache": false cannot be updated. Only the fields given are sent; the cache keeps each revision as its own entry pointing back at the original, which is why list_messages shows them with an "updates" field — the original keeps its old text and a second entry carries the new one.

Needs ntfy 2.16.0 or newer, and the failure below that is silent: an older server simply publishes a new notification instead of revising the old one, and answers success. If subscribers report receiving two, that is why — check get_server_info for the version.

Asks a person first; where the client cannot show a dialog, call once to receive a token and again with it.

Clears notifications on subscribers' devices. The messages stay in the server cache and remain readable with list_messages — that is the whole difference from delete_messages, which also leaves them there but tells subscribers to remove rather than to clear.

Needs ntfy 2.16.0 or newer. Against an older server every id comes back with ok:false inside a result that is not an error — check the per-id results rather than only whether the call succeeded.

Deletes notifications and cancels scheduled ones that have not been delivered yet. Requires a confirmation token: call once without it to receive the token, then again with it.

"Deleted" means subscribers are told to remove their copy. ntfy publishes a message_delete event and does not remove anything from its own cache, so list_messages and get_message still return the message afterwards, until it expires. Do not read that as the delete having failed, and do not delete again: the delete event is in the list too, alongside the message it refers to.

Needs ntfy 2.16.0 or newer. Against an older server every id comes back with ok:false inside a result that is not an error — check the per-id results rather than only whether the call succeeded.

Creates a non-admin account on a self-hosted instance. Requires an admin account. Grant it access to topics with manage_user_access — a new account can reach nothing until you do.

The API cannot create administrators; only the ntfy CLI can (ntfy user add --role=admin).

Asks a person first; where the client cannot show a dialog, call once to receive a token and again with it.

Be aware that a password passed as a tool argument stays in the conversation transcript. For an account that matters, create it on the server instead.

Removes an account and every access grant attached to it. Requires an admin account and a confirmation token: call once without it to receive the token, then again with it.

Sets or removes an account's access to a topic or topic pattern. Requires an admin account and a confirmation token.

Destructive in both directions, which is why it is gated: taking access away breaks a running publisher, and granting it exposes a topic's traffic to another account.

A pattern may end in "*" to cover a family of topics. "deny" writes an explicit refusal — the only way to carve an exception out of a wildcard grant — whereas "revoke" removes the rule entirely, so a broader wildcard or the server default applies again.

Where NTFY_TOPICS restricts this server, the topic must be one of its entries and a wildcard is refused: a pattern covers topics that are not on that list.