# Cactusinhand/mcp_server_notify [Health: Active]

**Category:** 💬 Communication  
**Repository:** https://github.com/Cactusinhand/mcp_server_notify  
**GitHub Stars:** 54  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/cactusinhand-mcp-server-notify

## Description
A MCP server that send desktop notifications with sound effect when agent tasks are completed.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "mcp-server-notify": {
    "command": "uvx",
    "args": ["mcp-server-notify"]
  }
}
```

## Documentation

## What Cactusinhand/mcp_server_notify MCP server does

Cactusinhand/mcp_server_notify MCP server gives an agent a way to notify the user through the local desktop when a task is complete. Notifications include a sound effect, and the project includes the sound file used for the alert. The intended workflow is to add an instruction such as asking the agent to notify you after finishing a task, then let the agent invoke the notification capability.

The server is designed for desktop environments rather than hosted notification delivery. It supports Windows, macOS, and Linux, and follows the standard Model Context Protocol so it can be configured in MCP-compatible clients.

## How it works

The package runs as a local Python MCP process. Desktop notification delivery is implemented through the Apprise API, while the MCP client exposes the notification action to the agent. In VS Code with Copilot agent mode, the README identifies the action as `send_notification`; equivalent client behavior depends on how the MCP client presents server tools.

After the server is registered with a client, an agent can call the notification action when it reaches a completion point. For Cursor, the README suggests adding a completion instruction to prompts or configuring it as a rule. The server does not provide Docker support because native host notification access is not currently available from the project's Docker setup.

## Setup and configuration

Install the package from PyPI with either `uv pip install mcp-server-notify` or `pip install mcp-server-notify`. The module can be started with `python -m mcp_server_notify`. It also accepts `--debug` and a `--file` option for logging; the documented example uses `--log-file=path/to/logfile.log`.

For clients that support `uvx`, the package can be launched with `uvx mcp-server-notify`. Claude Desktop and Cursor examples instead show a local `uv` configuration using the project directory and `uv run mcp-server-notify`, or a Python module configuration using `python -m mcp_server_notify`.

Platform dependencies may be required. Windows needs `pywin32`. macOS needs the `terminal-notifier` utility installed through Homebrew. The README does not list an additional desktop dependency for Linux.

## Tools and capabilities

- Sends a system desktop notification after an agent task completes.
- Plays an alert sound to draw attention to the notification.
- Exposes a notification action for MCP clients, identified as `send_notification` in the VS Code usage instructions.
- Supports local use on Windows, macOS, and Linux.
- Provides debug and log-file command-line options.

## Limitations and notes

Cactusinhand/mcp_server_notify MCP server depends on the desktop environment being able to receive native notifications. The required setup differs by operating system, so a successful Python package installation alone may not be sufficient on Windows or macOS.

Docker is documented as unavailable because containers are isolated from host operating-system notification facilities and the project would need to handle different native notification systems and dependencies. The provided material does not document remote hosting, authentication, notification history, or delivery to external messaging services. Cactusinhand/mcp_server_notify MCP server is licensed under MIT.

_Full upstream README: https://allmcps.com/mcp/cactusinhand-mcp-server-notify/readme_