Desktop Notification MCP Server
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send-notificationB | Display a cross-platform desktop notification with title, message, priority, category, duration control, and optional sound |
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
There is only one tool, so there is no possibility of confusing it with another tool. Its purpose—sending a desktop notification—is completely unambiguous.
The single tool uses a clear, readable kebab-case verb-noun pattern (send-notification). With only one tool, there are no competing conventions to create inconsistency.
A server whose sole purpose is desktop notifications is reasonably scoped with one tool, since sending a notification is the only meaningful operation. However, a single-tool server is inherently limited and feels thin compared to typical multi-tool MCP servers.
The tool covers the core notification lifecycle operation with title, message, priority, category, duration, and sound options. There are no obvious missing CRUD operations for a one-way notification service, though features like listing or dismissing notifications could be considered minor gaps.