Skip to main content
Glama
deenesjakoruzh
Cactusinhand

MCP Notify Server

by Cactusinhand
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

PyPI version

Trust Score

📢 MCP Notify Server

English | 中文

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

Related MCP server: Notifications MCP Server

⏬ 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:

  1. Install the service manager uv/uvx: pip install uv

  2. 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": {}
        }
    }
}

  3. Make sure you are using the latest VSCode version — it automatically runs MCP services

  4. Open VSCode → enable Copilot → switch to agent mode.

  5. Type # → you will see the #send_notification option.

  6. Ask the agent: run #send_notification (it will handle the notification automatically).

  7. 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:

  1. OS-specific notification systems Each operating system (Windows, macOS, Linux) has its unique notification mechanism.

  2. Docker isolation The isolation of Docker containers limits their ability to access host operating system resources directly.

  3. Dependency management Need to handle different notification libraries and dependencies for each operating system.

🧾 License

MIT

💻 Contributions

Issues and pull requests are welcome!

Available Tools

1 tool
send_notificationC

Send system notification with optional sound

ParametersJSON Schema
NameRequiredDescriptionDefault
titleYes
messageYes
play_soundNo
timeoutNo

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It states the tool sends a notification but doesn't disclose behavioral traits like whether it's synchronous/asynchronous, what happens on failure, if it requires specific permissions, or how notifications are delivered. 'Optional sound' hints at a feature but lacks details on default behavior or sound types.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise with a single sentence that directly states the tool's function. It's front-loaded and wastes no words, making it easy to parse quickly. Every part of the sentence contributes to understanding the tool's purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, no output schema, and 0% schema description coverage for 4 parameters, the description is incomplete. It covers the basic action but lacks details on behavior, parameters, return values, or error handling. For a notification-sending tool with multiple parameters, more context is needed to guide effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description doesn't add meaning beyond what the schema provides. It mentions 'optional sound' which corresponds to the 'play_sound' parameter, but doesn't explain other parameters like 'title', 'message', or 'timeout'. With 4 parameters and no schema descriptions, the description fails to compensate adequately, resulting in a baseline score.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('send') and resource ('system notification') with an additional feature ('optional sound'). It's specific about what the tool does, though without sibling tools, differentiation isn't applicable. The purpose is unambiguous but could be more detailed about the notification type or system context.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool, such as appropriate contexts, prerequisites, or alternatives. It mentions 'optional sound' but doesn't explain when sound should be enabled or disabled. With no sibling tools, this is less critical, but still lacks usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.1/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'send_notification' has a clear, distinct purpose that cannot be confused with any other tool in the set.

Naming Consistency5/5

The tool name 'send_notification' follows a clear verb_noun pattern (send + notification). Since there is only one tool, consistency is inherently perfect with no deviations or mixed conventions to evaluate.

Tool Count2/5

A single tool is too few for a server named 'MCP Notify Server', which suggests a broader notification domain. This minimal set feels thin and likely incomplete for typical notification workflows, such as managing notifications or checking statuses.

Completeness2/5

The tool surface is severely incomplete for a notification server. While 'send_notification' covers sending, there are obvious gaps like listing notifications, updating them, deleting them, or configuring notification settings, which agents would need for full functionality.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Cactusinhand/mcp_server_notify'

If you have feedback or need assistance with the MCP directory API, please join our Discord server