Ntfy Mcp Server
Let Claude or Cursor send and manage ntfy push alerts when deploys, cron jobs, or agent tasks finish without building a custom notifier.
Overview
io.github.cyanheads/ntfy-mcp-server is an Operate-phase MCP server that lets agents send, manage, and replay ntfy push notifications from your dev environment.
What is this MCP server?
- Send ntfy messages to topics with priority, tags, and attachments via MCP tools
- Support multiple ntfy servers via NTFY_SERVERS JSON with per-server auth
- Manage subscriptions, replay messages, and use ntfy.sh or self-hosted bases
- stdio transport with Bun runtime (npm package ntfy-mcp-server v2.1.0)
- Per-call base_url override when registered servers are configured
- Server version 2.1.0
- stdio transport via npm identifier ntfy-mcp-server
- Default public base https://ntfy.sh when NTFY_SERVERS is unset
Community signal: 16 GitHub stars.
What problem does it solve?
Agents finish work in the background but you only find out if you keep checking the terminal or inbox.
Who is it for?
Solo builders who already use ntfy (or ntfy.sh) and want zero-custom-code alerts from agent workflows and scripts.
Skip if: Teams needing email campaigns, Slack-style threading, or notification UX inside their own SaaS product.
What do I get? / Deliverables
Your agent can publish ntfy alerts to your phone or desktop the moment something succeeds, fails, or needs a decision.
- Agent-callable tools to publish and manage ntfy messages
- Multi-server ntfy configuration from environment variables
- Replay and subscription operations against your ntfy API
Recommended MCP Servers
Journey fit
Operational awareness fits the Operate phase: you wire agents to ping you when production or background work needs human attention. Monitoring is the canonical shelf for outbound alerts and notification replay, not one-off feature coding.
How it compares
MCP push-notification bridge, not a hosted incident-management product or an agent skill for writing copy.
Common Questions / FAQ
Who is ntfy-mcp-server for?
Indie developers and operators who use ntfy topics and want Claude Code, Cursor, or similar agents to trigger pushes automatically.
When should I use ntfy-mcp-server?
Use it when deploys, jobs, or agent runs should notify you out-of-band via ntfy—including self-hosted servers with tokens or basic auth.
How do I add ntfy-mcp-server to my agent?
Register the npm package ntfy-mcp-server with stdio (bun run start:stdio) and set NTFY_BASE_URL or NTFY_SERVERS plus optional auth variables in your MCP config.