mcp-ntfy
Related Servers
Alternatives to mcp-ntfy
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server for ntfy: publish notifications, read cached messages, manage users and topic access1341 npmMIT
- AlicenseCqualityDmaintenanceMCP server for sending notifications to ntfy.sh or self-hosted ntfy instances.212 npmMIT
- AlicenseBqualityDmaintenanceMCP server for sending Gotify push notifications to your devices.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables publishing and retrieving ntfy-style notifications via MCP, supporting topics, titles, tags, priorities, and WebSocket streaming.MIT
- AlicenseBqualityDmaintenanceA lightweight MCP server for sending push notifications via ntfy.sh, supporting customizable titles, priorities, tags, and action buttons.16 npm7MIT
- AlicenseNot gradedqualityAmaintenanceMCP server and CLI for Gotify that lets agents send push notifications, check server health, list messages, and manage Gotify apps and clients over stdio or streamable HTTP, with authentication support.2AGPL 3.0
TDQS
Scored across 3 tools
Each tool targets a distinct operation: publishing notifications, polling cached messages, and checking server health. There is no overlap or ambiguity between them.
publish and poll follow a clear verb pattern, while server_health is a noun phrase rather than a verb-based action. The naming is mostly consistent and intuitive, with only a minor deviation.
Three tools is well-scoped for an ntfy integration: send, receive, and health check. Each tool earns its place without unnecessary bulk.
The core notification lifecycle is covered: publishing, retrieving messages, and verifying server status. Real-time subscription is not included, but polling cached messages covers the main retrieval use case adequately.