Skip to main content
Glama
Notifications MCP Server

Notifications MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CLAUDE_START_SOUNDNoPath to a sound file for start notifications. Default: macOS system sound.
CLAUDE_COMPLETE_SOUNDNoPath to a sound file for completion notifications. Default: macOS system sound.
CLAUDE_NOTIFICATION_ICONNoPath to an icon file for visual notifications. Default: none.
CLAUDE_VISUAL_NOTIFICATIONSNoSet 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

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": true
}
resources
{
  "subscribe": false,
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
task_statusC

‼️ MANDATORY: Sends notifications (sound and visual) for the user.

📢 IMPORTANT INSTRUCTIONS FOR THE LLM:

  1. ALWAYS call this tool at the START of EVERY response

  2. Call this tool BEFORE using any other tools

  3. Call this tool at the END of conversations

  4. Use this tool even if no other tools are needed

⚠️ PURPOSE: This notification alerts users when the LLM has started or completed processing.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.1/5.0

Scored across 1 tool

Disambiguation5/5

There is only one tool on the server, so there is no possibility of selecting the wrong tool. The tool's dual role (start and end notifications) is handled by a single surface, but that is a completeness issue rather than an ambiguity across tools.

Naming Consistency4/5

With a single tool there is no cross-tool inconsistency to penalize, and 'task_status' is a readable snake_case identifier. It is a noun phrase rather than the more typical verb_noun pattern, which keeps it slightly short of ideal.

Tool Count3/5

Notification is a narrow purpose where one tool can suffice, but a single tool conflating start-of-response and end-of-conversation signalling is borderline thin. A parameterized stage or separate start/complete operations would make the scope feel better earned.

Completeness2/5

The surface offers no way to specify notification stage, type (sound vs visual), or opt-out, so an agent cannot express the distinct events the description promises. For a notification domain, the lack of any start/complete distinction or configuration options is a significant gap.

Maintenance

ActivityMaintained
ResponsivenessOutdated data