Ntfy
for LuumenAI
Push alerts to the on-call phone from the terminal you already work in
Connect ntfy and Luumen can reach the people who need to know. It reads server health, statistics, service tiers, and queued messages for context, then publishes to a topic as an approved step. Useful for maintenance notices, escalation pings, and confirming a notification path works before you depend on it. Luumen authenticates with basic auth.
The Ntfy toolbox
12 tools: 7 read, 5 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadFetch Scheduled MessagesFetch messages scheduled for later delivery from a topic.
- ReadGet Account InformationRetrieve account data for authenticated user or anonymous user.
- ReadGet Server StatisticsRetrieve server statistics including message counts and publishing rates.
- ReadGet Service TiersList all available ntfy service tiers with their limits and features.
- ReadGet File Attachment MetadataGet file attachment metadata from a message without downloading the file content.
- ReadCheck NTFY Service HealthCheck the health status of the ntfy service.
- ReadSubscribe to Topic (Raw Stream)Subscribe to a topic and receive message bodies as raw text stream.
- WriteCreate NTFY AccountRegister a new user account on ntfy. Approval by default
- WriteCreate Web Push SubscriptionRegister a web push subscription for browser notifications. Approval by default
- WriteDelete Web Push SubscriptionUnregister a web push subscription from the ntfy server. Approval by default
- WritePublish Message to TopicPublish a message to a ntfy topic. Approval by default
- WritePublish Message via GETPublish messages to ntfy via GET request with URL parameters. Approval by default
One prompt, start to finish
What a governed Ntfy run looks like inside Luumen.
Questions
Authorize once with Basic auth. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — create ntfy account, create web push subscription, delete web push subscription, publish message to topic, and more — is shown as a plan and requires approval by default, including the 1 action classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Ntfy — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
SlackRead the incident thread; post updates and approvals back.
GmailVendor and alert mail as context; replies drafted for review.
Microsoft TeamsRead Teams channels and chats for context, then make membership changes as approved steps.
DiscordRead Discord command permissions and app context, then change them with approvalPut Ntfy to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.