ntfy-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NTFY_TOKEN | No | Bearer token used for the Authorization header. | |
| NTFY_TOPIC | Yes | Default topic. Must pass topic validation. | |
| NTFY_SOURCE | No | Operator-controlled source label. | agent |
| NTFY_DRY_RUN | No | Validate and return success without network I/O. | false |
| NTFY_BASE_URL | No | HTTPS ntfy server base URL. | https://ntfy.sh |
| NTFY_ALLOWED_TOPICS | No | Comma-separated allow-list of topics. | NTFY_TOPIC |
| NTFY_DEFAULT_PRIORITY | No | Default priority for info and success. | 3 |
| NTFY_MAX_MESSAGE_LENGTH | No | Maximum message length before truncation. | 1800 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| notify_userB | Send an allow-listed ntfy push notification to the configured user. |
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 1 tool
With only a single tool, there is no possibility of confusion or overlap between tools.
The single tool uses a clear verb_noun pattern (notify_user), which is consistent within the set.
One tool is minimal; while it may suffice for sending a notification, a more feature-rich server might benefit from additional tools like listing or managing subscriptions.
The tool covers the core action of sending a notification, but lacks any additional operations such as checking delivery status or managing notification preferences.