MCP Notifications 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| show_notificationC | Display a notification on macOS using the Notification Center. Can include a title, content message, and optional icon and 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
With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to compare it to. The tool's purpose is clearly defined and distinct by default.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'show_notification' follows a clear verb_noun pattern, and there are no other tools to create inconsistency.
A single tool is generally too few for a server's purpose, as it limits functionality and may indicate an incomplete or trivial implementation. For a notifications server, one tool feels thin and under-scoped, lacking operations like managing or dismissing notifications.
The tool surface is severely incomplete for a notifications domain. While 'show_notification' covers creation, there are obvious gaps such as listing, updating, or dismissing notifications, which are essential for a full notifications lifecycle. This will likely cause agent failures in more complex workflows.