ntfy-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NTFY_URL | Yes | The base URL of the ntfy instance (e.g., https://ntfy.sh) | |
| NTFY_TOKEN | No | Bearer token for authentication (optional, takes precedence over basic auth) | |
| NTFY_TOPIC | Yes | The topic to publish notifications to | |
| NTFY_PASSWORD | No | Password for basic authentication (optional) | |
| NTFY_USERNAME | No | Username for basic authentication (optional) |
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
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ntfy_publishC | Send a notification to the server-configured ntfy topic. |
| ntfy_pingC | Send a simple notification to the server-configured ntfy topic. |
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
Both tools perform the same action—sending a notification to the server-configured topic. The only distinction is 'simple' vs. regular, which is not meaningful enough for an agent to reliably choose between them.
Both tools follow a consistent ntfy_verb pattern with snake_case, which is predictable. Minor deviation is that 'publish' and 'ping' are synonymous verbs for notification delivery.
Two tools is borderline for a notification-focused server, but one is essentially redundant, making the count feel padded. A single publish tool would be more appropriate.
The domain is ntfy notifications, but the server only covers sending. There is no tool for subscription, topic management, or retrieving notification history, leaving significant gaps beyond the core publish action.