About 📢 MCP Notify Server
MCP Notify Server is an MCP server that sends desktop notifications with a sound when agent tasks finish. It is intended for users who want to be alerted when long-running tasks complete, and it supports Windows, macOS and Linux.
Key features
- 01Desktop notifications after agent tasks complete
- 02Alert sounds with a bundled sound file
- 03Cross-platform support for Windows, macOS and Linux
- 04Works with MCP-compatible LLM clients
Use cases
- 01Alerting the user when an agent task finishes
- 02Triggering completion notifications from Cursor or VS Code Copilot
MCP support
The project runs as an MCP server and exposes a send_notification tool to MCP clients, which can be configured in clients such as Claude Desktop, Cursor and VS Code.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project README📢 MCP Notify Server
A MCP server that send desktop notifications with sound effect when agent tasks are completed.
🥩 Features
- Send system desktop notifications after agent tasks completion
- Play alert sounds to grab user attention, with sound file inside.
- Cross-platform support (Windows, macOS, Linux)
- Based on standard MCP protocol, integrates with various LLM clients
⏬ Installation
Install using uv package manager
git clone https://github.com/Cactusinhand/mcp_server_notify.git
cd mcp_server_notify
uv venv
source .venv/Scripts/activate
uv pip install mcp-server-notify
# or
pip install mcp-server-notify
After installation, call the module directly to check if installation was successful:
python -m mcp_server_notify
This module accepts --debug or --file option, we can use it like:
python -m mcp_server_notify --debug
python -m mcp_server_notify --debug --log-file=path/to/logfile.log
⚠️❕ Special requirements
** We use Apprise API for our Desktop notification deliver,so we need to install some special requirements in our Desktop **
Windows
# windows:// minimum requirements
pip install pywin32
macOS
# Make sure terminal-notifier is installed into your system
brew install terminal-notifier
📚 Usage
Using with Claude Desktop:
Find the configuration file claude_desktop_config.json
{
"mcpServers": {
"NotificationServer": {
"command": "uv",
"args": [
"--directory",
"path/to/your/mcp_server_notify project",
"run",
"mcp-server-notify",
]
}
}
}
If installed globally, you can also use the python command:
{
"mcpServers": {
"NotificationServer": {
"command": "python",
"args": [
"-m",
"mcp_server_notify",
]
}
}
}
⚡️ Using with Cursor:
Find the configuration file ~/.cursor/mcp.json or your_project/.cursor/mcp.json
{
"mcpServers": {
"NotificationServer": {
"command": "uv",
"args": [
"--directory",
"path/to/your/mcp_server_notify project",
"run",
"mcp-server-notify",
]
}
}
}
After configuration, simply add a prompt like finally, send me a notification when task finished. at the end of your task input to the AI to trigger notifications.
In Cursor, you can add this prompt as a rule in Cursor Settings -> Rules so you don't have to type it manually each time.
⚡️ Using with VSCode + Copilot:
-
Install the service manager uv/uvx:
pip install uv -
Add the service to VSCode settings:
Windows
%APPDATA%\Code\User\settings.json
macOS$HOME/Library/Application\ Support/Code/User/settings.json
Linux$HOME/.config/Code/User/settings.json"mcp": { "servers": { "notifier": { "command": "uvx", "args": [ "mcp-server-notify" ], "env": {} } } } -
Make sure you are using the latest VSCode version — it automatically runs MCP services
-
Open VSCode → enable Copilot → switch to agent mode.
-
Type # → you will see the #send_notification option.
-
Ask the agent: run #send_notification (it will handle the notification automatically).
-
Now the Copilot in agent mode can send desktop notifications.
🐳 Running with Docker
Currently not available due to environment compatibility issues. If Docker containers need to trigger host notifications regardless of whether the host OS is Windows, macOS, or Linux, the solution becomes much more complex, and direct use of native notifications is usually not feasible.
Main issues:
-
OS-specific notification systems Each operating system (Windows, macOS, Linux) has its unique notification mechanism.
-
Docker isolation The isolation of Docker containers limits their ability to access host operating system resources directly.
-
Dependency management Need to handle different notification libraries and dependencies for each operating system.
🧾 License
MIT
💻 Contributions
Issues and pull requests are welcome!
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.
