Skip to main content
Glama
Notifications MCP Server

Notifications MCP Server

README.md
# Notifications MCP Server

[![Tests](https://github.com/charles-adedotun/notifications-mcp-server/actions/workflows/python-test.yml/badge.svg)](https://github.com/charles-adedotun/notifications-mcp-server/actions/workflows/python-test.yml)

MCP server that lets Claude Desktop or another MCP client trigger macOS sound and visual notifications through a `task_status` tool.

## Current Status

This is a macOS-focused utility. It is not an automatic Claude completion detector by itself: an MCP client or model must call the `task_status` tool when it wants a notification.

## What Works Today

- Registers a `task_status` MCP tool.
- Plays macOS system sounds with `afplay`.
- Sends visual notifications using terminal-notifier, AppleScript, PyObjC, or pync fallbacks.
- Supports separate start and completion sounds.
- Supports disabling visual notifications through an environment variable.
- Includes tests for the modular notification and sound managers.

## Important Limitations

- macOS is the only implemented platform.
- Linux and Windows support are not implemented.
- Notifications only happen when the MCP tool is called.
- The packaged console script is `claude-notifications`.
- The Python package is `notifications`; there is no `notifications_mcp_server` module entry point.
- Custom sound configuration uses environment variables, not the JSON configuration block that older README versions showed.

## Installation

Run directly from GitHub with `uvx` (zero manual virtualenv setup required):

```bash
uvx --from git+https://github.com/charles-adedotun/notifications-mcp-server claude-notifications
```

Or install into your Python environment directly from GitHub:

```bash
pip install "git+https://github.com/charles-adedotun/notifications-mcp-server.git"
```

Optional visual notification dependencies:

```bash
pip install "notifications-mcp-server[visual] @ git+https://github.com/charles-adedotun/notifications-mcp-server.git"
pip install "notifications-mcp-server[pync] @ git+https://github.com/charles-adedotun/notifications-mcp-server.git"
```

For `terminal-notifier` fallback support on macOS:

```bash
brew install terminal-notifier
```

## Claude Desktop / Claude Code Configuration

Configure via `uvx` (recommended):

```json
{
  "mcpServers": {
    "notifications": {
      "command": "uvx",
      "args": [
        "--from",
        "git+https://github.com/charles-adedotun/notifications-mcp-server",
        "claude-notifications"
      ]
    }
  }
}
```

Or if installed globally via `pip` / `uv tool install`:

```json
{
  "mcpServers": {
    "notifications": {
      "command": "claude-notifications"
    }
  }
}
```

Restart Claude Desktop after changing the config.

## Configuration

Environment variables:

```bash
export CLAUDE_START_SOUND="/System/Library/Sounds/Glass.aiff"
export CLAUDE_COMPLETE_SOUND="/System/Library/Sounds/Hero.aiff"
export CLAUDE_VISUAL_NOTIFICATIONS="true"
export CLAUDE_NOTIFICATION_ICON="/path/to/icon.png"
```

If no custom sounds are set, the server uses macOS system sounds.

## MCP Tool

`task_status`

Input:

```json
{
  "message": "Task completed"
}
```

Messages containing `start` or `processing` are treated as start notifications. Other messages are treated as completion notifications.

## Verification Demo

Run the local diagnostic script on macOS to test the available notification paths:

```bash
python3 test_notification.py
```

The MCP tool returns a compact status object after attempting sound and visual notification delivery:

```json
{
  "status": "success",
  "message": "Task completed",
  "sound": "/System/Library/Sounds/Hero.aiff",
  "visual": true
}
```

For a quieter smoke test that skips visual notification prompts:

```bash
CLAUDE_VISUAL_NOTIFICATIONS=false claude-notifications
```

## Development

```bash
git clone https://github.com/charles-adedotun/notifications-mcp-server.git
cd notifications-mcp-server
pip install -e ".[dev]"
pytest
```

## License

MIT

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