Ntfy MCP server

ntfy-mcp-server Send, manage, and replay ntfy push notifications via MCP. STDIO or Streamable HTTP. 4 Tools • 1 Resource

Overview

Push notifications over the ntfy pub/sub HTTP API. Publish, update, and manage notifications, poll cached topic history, and look up emoji short codes for tags from any MCP client. Runs as a stdio process or a local Streamable HTTP server.

Tools

Resources

ntfyfetchmessages covers the same topic data with custom windows and filters when the resource's fixed defaults aren't enough.

Capability reference

ntfypublishmessage tool

• Topics are created on first publish — treat the topic name as a secret; anyone who knows it can publish or subscribe
• Full publish-parameter coverage — title, priority (1–5), tags, click, attach, icon, filename, markdown, delay, email, call, cache, firebase; message body capped at 4096 bytes (non-ASCII characters cost more), empty body defaults server-side to triggered
• Up to three discriminated action buttons (view, broadcast, http, copy) per message
• Update or replace a previously-sent message by passing the original sequence_id
• Per-call baseurl override forwards credentials only when it matches a registered server (NTFYBASEURL or an NTFYSERVERS entry); otherwise the request goes out unauthenticated
• Publishes carrying email, call, or a broadcast/http action button ask the user to confirm the specific target first — the call returns a confirmation request, and sends only once reissued with the answer

ntfymanagemessage tool

Shortened. The full README is on GitHub.