Simple Ntfy MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NTFY_BASE_URL | No | Base URL of ntfy server | https://ntfy.sh |
| NTFY_DEFAULT_TOPIC | Yes | Default topic to send notifications to |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_ntfyC | Send a notification via ntfy |
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 overlap or confusion between tools. The tool's purpose is clear and distinct from any other.
The tool name follows a consistent verb_noun pattern using snake_case. The name is descriptive and matches the action it performs.
The tool count is slightly below the typical 3-15 range, but it is entirely appropriate for the narrow scope of sending ntfy notifications. Adding more tools would be unnecessary and likely artificial.
The domain is specifically sending notifications, and this single tool fully covers that lifecycle. There are no obvious missing operations for the stated purpose.