ntfy-me-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NTFY_URL | No | URL of the ntfy server (change to your self-hosted ntfy server URL if needed) | https://ntfy.sh |
| NTFY_TOKEN | No | Access token for authentication with protected topics/servers | |
| NTFY_TOPIC | Yes | Your ntfy topic name for sending notifications |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ntfy_meA | Send a notification to the user via ntfy. Use this tool when the user asks to 'send a notification', 'notify me', 'send me an alert', 'message me', 'ping me', or any similar request. This tool is perfect for sending status updates, alerts, reminders, or notifications about completed tasks. |
| ntfy_me_fetchA | Fetch cached messages from an ntfy server topic. Use this tool when the user asks to 'show notifications', 'get my messages', 'show my alerts', 'find notifications', 'search notifications', or any similar request. Great for finding recent notifications, checking message history, or searching for specific notifications by content, title, tags, or priority. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one sends notifications, the other retrieves cached messages. There is no overlap or ambiguity in their functions.
Both tools share the prefix 'ntfy_me_', but the first tool lacks a specific verb suffix (e.g., 'send') while the second has '_fetch'. The pattern is mostly consistent but has a minor deviation.
With only two tools, the set is minimal but appropriate for the narrow scope of sending and fetching notifications. It feels slightly thin but not unreasonable for a simple domain.
The tool set covers the basic operations of sending and retrieving notifications, but lacks additional expected functionality such as deleting or managing topics, leaving some gaps for full lifecycle management.