Notifications MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLAUDE_START_SOUND | No | Path to a sound file for start notifications. Default: macOS system sound. | |
| CLAUDE_COMPLETE_SOUND | No | Path to a sound file for completion notifications. Default: macOS system sound. | |
| CLAUDE_NOTIFICATION_ICON | No | Path to an icon file for visual notifications. Default: none. | |
| CLAUDE_VISUAL_NOTIFICATIONS | No | Set to 'false' to disable visual notifications. Default: 'true'. |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| task_statusA | ‼️ MANDATORY: Sends notifications (sound and visual) for the user. 📢 IMPORTANT INSTRUCTIONS FOR THE LLM:
⚠️ PURPOSE: This notification alerts users when the LLM has started or completed processing. Args: message (str): Message describing the state of the task (e.g., "Started processing", "Task completed") Returns: dict: Status information about the notification |
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
Only one tool exists, so there is no ambiguity with other tools. The tool's purpose is clearly described.
The tool name 'task_status' suggests checking status, but the tool actually sends notifications. This mismatch between name and function indicates poor naming consistency.
A single tool for a notifications server is borderline. It might be sufficient for simple task notifications, but the scope is narrow.
The server only covers task status notifications, missing other common notification types (e.g., errors, warnings, arbitrary messages). This is a significant gap.