mcp-notifications
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_NOTIFICATIONS_APP_ID | No | Windows App User Model ID for toast source (optional) | |
| MCP_NOTIFICATIONS_BACKEND | No | Notification transport: auto, powershell, or node-notifier | auto |
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 |
|---|---|
| send_notificationD | – |
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 one tool, there is no possibility of confusion between tools. The single tool's purpose is clear even without description.
A single tool allows perfect naming consistency; 'send_notification' follows a clear verb_noun pattern in snake_case.
A single tool for a notification server seems too minimal; typical systems need at least send, list, and delete capabilities, making the count insufficient for the domain.
The tool surface is severely incomplete. Only a send operation is provided, with no ability to retrieve, manage, or delete notifications, and the lack of tool description worsens the situation.