mcp-os-notifications
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| dispatch_os_notificationA | Dispatch a native OS notification. Use this tool whenever the user asks to be notified, for example:
Args: title: Short title for the notification (e.g. "Task finished"). message: Body text explaining what happened (e.g. "Your download is ready"). urgency: Notification priority: "low", "normal" (default), or "critical". sound: Whether to play an audible alert alongside the notification. timeout: Number of seconds before the notification auto-dismisses. -1 means use the OS default. token: Optional stable identifier for this notification. Reusing the same token replaces the previous notification instead of creating a new one. mobile: Also send to configured mobile backends (ntfy.sh, Telegram, Pushover). Returns: A dictionary with the scheduled notification id, success flag, and details of any mobile dispatch attempts. |
| notify_userC | Alias for |
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 are actually the same; notify_user is explicitly an alias for dispatch_os_notification. This creates complete overlap and makes it impossible for an agent to distinguish between them.
Both tool names follow a verb_noun pattern (dispatch_os_notification, notify_user), so the naming convention is consistent. However, the presence of a duplicate alias reduces the overall pattern's clarity.
With only 2 tools (one of which is a duplicate), the count is minimal but still reasonable for a focused notification dispatch server. It is not excessive, but could be consolidated into a single tool.
The server covers the core functionality of dispatching OS notifications with configurable options (urgency, sound, timeout, mobile). However, it lacks any management or querying capabilities, which could be considered a minor gap.