Push a ntfy notification

Push phone notifications from your AI with near-zero setup (ntfy topics).

Publish to a ntfy topic - the fastest reminder demo in the catalog. Public topics need no credential at all; protected topics use a token.

The credential never enters the model context: it lives in the FlurryPORT secret store, deliveries are signed server-side, and every send returns a receipt your agent can quote.

npx flurryport mcp

Tools your agent gains

flry_ntfy_push

Push a notification to the configured ntfy topic. Input: message (required), title, priority 1-5.

Setup walkthrough

1. NTFY_TOKEN: Only needed for protected topics on ntfy.sh or a self-hosted server (Settings, Access tokens). Public topics: skip the secret entirely - but anyone who knows the topic name can subscribe, so pick a long random topic and treat the name itself as the secret.

Intent schema

{
  "type": "object",
  "required": [
    "message"
  ],
  "properties": {
    "message": {
      "type": "string",
      "maxLength": 4000
    },
    "title": {
      "type": "string"
    },
    "priority": {
      "type": "integer",
      "minimum": 1,
      "maximum": 5
    }
  }
}

Install-time parameters

topic

install-time: The ntfy topic this install publishes to.

Transformation

{ "topic": $install.topic, "message": $body.message, "title": $body.title, "priority": $body.priority }

Delivery target

POST https://ntfy.sh

Placeholders like $secrets.NAME resolve server-side at delivery, never in the agent.

Gotchas

• JSON publishing goes to the ROOT URL with the topic in the body; posting JSON to /topic-name silently becomes a raw-text message instead.
• A public topic name is itself the only gate: anyone who knows it can subscribe, so pick a long random name and treat it like a password.

Where this fits

• Destination: ntfy
• Notifications recipes
• What agent tokens can and cannot do
• All recipes

Related recipes