HomeCommunication › ntfy

ntfy

Publish ntfy notifications, read the message cache, and manage users and topic access

TypeScript CloudLocal
★ 0 stars Last pushed 2026-09-20 License: MIT

Topics: Communication

Connect

Review any command before running it. Package names and URLs come from the server's own registry entry.

Package (npm 0.3.0)

npx -y @ni-c/[email protected]

Or add to your MCP client config:

{
  "mcpServers": {
    "ntfy-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@ni-c/[email protected]"
      ],
      "env": {
        "NTFY_URL": "<YOUR_VALUE>",
        "NTFY_TOKEN": "<YOUR_VALUE>",
        "NTFY_USERNAME": "<YOUR_VALUE>",
        "NTFY_PASSWORD": "<YOUR_VALUE>",
        "NTFY_TOPICS": "<YOUR_VALUE>",
        "NTFY_READ_ONLY": "<YOUR_VALUE>",
        "NTFY_INSECURE_TLS": "<YOUR_VALUE>",
        "NTFY_ALLOW_TOOLS": "<YOUR_VALUE>",
        "NTFY_DENY_TOOLS": "<YOUR_VALUE>"
      }
    }
  }
}
  • NTFY_URL required — Base URL of the ntfy server, e.g. https://ntfy.example.net. There is deliberately no default.
  • NTFY_TOKEN secret — ntfy access token (tk_...). Optional: an open instance needs no credentials. Mutually exclusive with NTFY_USERNAME/NTFY_PASSWORD.
  • NTFY_USERNAME — Username for basic authentication. Must be set together with NTFY_PASSWORD.
  • NTFY_PASSWORD secret — Password for basic authentication. Must be set together with NTFY_USERNAME.
  • NTFY_TOPICS — Comma-separated topics the server may use. The first is the default when a tool omits one, and the list restricts every read and write tool.
  • NTFY_READ_ONLY — Set to exactly true to register only the six read tools (default: false — ntfy exists to publish)
  • NTFY_INSECURE_TLS — Set to true to accept a self-signed certificate from the ntfy server (default: false)
  • NTFY_ALLOW_TOOLS — Comma-separated tool names or list_* prefixes to register; 'essential' selects a curated preset (default: all tools)
  • NTFY_DENY_TOOLS — Comma-separated tool names or list_* prefixes to remove from whatever the allow list left

Package (oci)

docker run -i --rm ghcr.io/ni-c/ntfy-mcp:0.3.0

Or add to your MCP client config:

{
  "mcpServers": {
    "ntfy-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/ni-c/ntfy-mcp:0.3.0"
      ],
      "env": {
        "NTFY_URL": "<YOUR_VALUE>",
        "NTFY_TOKEN": "<YOUR_VALUE>",
        "NTFY_USERNAME": "<YOUR_VALUE>",
        "NTFY_PASSWORD": "<YOUR_VALUE>",
        "NTFY_TOPICS": "<YOUR_VALUE>",
        "NTFY_READ_ONLY": "<YOUR_VALUE>",
        "NTFY_INSECURE_TLS": "<YOUR_VALUE>",
        "NTFY_ALLOW_TOOLS": "<YOUR_VALUE>",
        "NTFY_DENY_TOOLS": "<YOUR_VALUE>"
      }
    }
  }
}
  • NTFY_URL required — Base URL of the ntfy server, e.g. https://ntfy.example.net. There is deliberately no default.
  • NTFY_TOKEN secret — ntfy access token (tk_...). Optional: an open instance needs no credentials. Mutually exclusive with NTFY_USERNAME/NTFY_PASSWORD.
  • NTFY_USERNAME — Username for basic authentication. Must be set together with NTFY_PASSWORD.
  • NTFY_PASSWORD secret — Password for basic authentication. Must be set together with NTFY_USERNAME.
  • NTFY_TOPICS — Comma-separated topics the server may use. The first is the default when a tool omits one, and the list restricts every read and write tool.
  • NTFY_READ_ONLY — Set to exactly true to register only the six read tools (default: false — ntfy exists to publish)
  • NTFY_INSECURE_TLS — Set to true to accept a self-signed certificate from the ntfy server (default: false)
  • NTFY_ALLOW_TOOLS — Comma-separated tool names or list_* prefixes to register; 'essential' selects a curated preset (default: all tools)
  • NTFY_DENY_TOOLS — Comma-separated tool names or list_* prefixes to remove from whatever the allow list left

Related servers

Listed in punkpeye/awesome-mcp-servers (MIT)

Data from the Official MCP Registry