Skip to main content
Glama
deenesjakoruzh
Cactusinhand

MCP Notify Server

by Cactusinhand
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

PyPI 版本

📢 MCP 通知服务器

英语|中文

当代理任务完成时，MCP 服务器会发送带有声音效果的桌面通知。

🥩 功能

  • 代理任务完成后发送系统桌面通知

  • 播放警报声音来吸引用户注意力，其中包含声音文件。

  • 跨平台支持（Windows、macOS、Linux）

  • 基于标准MCP协议，可与多种LLM客户端集成

Related MCP server: Notifications MCP Server

⏬ 安装

使用uv包管理器安装

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

安装完成后直接调用模块检查是否安装成功：

python -m mcp_server_notify

该模块接受--debug或--file选项，我们可以像这样使用它：

python -m mcp_server_notify --debug
python -m mcp_server_notify --debug --log-file=path/to/logfile.log

⚠️❕ 特殊要求

** 我们使用Apprise API 来发送桌面通知，因此我们需要在桌面上安装一些特殊要求 **

视窗

# windows:// minimum requirements
pip install pywin32

macOS

# Make sure terminal-notifier is installed into your system
brew install terminal-notifier

📚 使用方法

与 Claude Desktop 一起使用：

找到配置文件claude_desktop_config.json

{
    "mcpServers": {
        "NotificationServer": {
            "command": "uv",
            "args": [
              "--directory",
              "path/to/your/mcp_server_notify project",
              "run",
              "mcp-server-notify",
            ]
        }
    }
}

如果全局安装，也可以使用python命令：

{
    "mcpServers": {
        "NotificationServer": {
            "command": "python",
            "args": [
              "-m",
              "mcp_server_notify",
            ]
        }
    }
}

⚡️ 与光标一起使用：

找到配置文件~/.cursor/mcp.json或者your_project/.cursor/mcp.json

{
    "mcpServers": {
        "NotificationServer": {
            "command": "uv",
            "args": [
              "--directory",
              "path/to/your/mcp_server_notify project",
              "run",
              "mcp-server-notify",
            ]
        }
    }
}

配置完成后，只需finally, send me a notification when task finished. ”即可触发通知。

在 Cursor 中，您可以在Cursor Settings -> Rules中将此提示添加为规则，这样您就不必每次都手动输入它。

⚡️ 与 VSCode + Copilot 一起使用：

  1. 安装服务管理器uv/uvx ： pip install uv

  2. 将服务添加到 VSCode 设置：

    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. 确保您使用的是最新的 VSCode 版本——它会自动运行 MCP 服务

  4. 打开 VSCode → 启用 Copilot → 切换到代理模式。

  5. 输入# → 您将看到#send_notification 选项。

  6. 询问代理：运行#send_notification（它将自动处理通知）。

  7. 现在代理模式下的 Copilot 可以发送桌面通知。

🐳 使用 Docker 运行

由于环境兼容性问题，目前暂不可用。如果 Docker 容器需要触发主机通知，无论主机操作系统是 Windows、macOS 还是 Linux，解决方案都会变得更加复杂，直接使用原生通知通常不可行。

主要问题：

  1. 特定于操作系统的通知系统 每个操作系统（Windows、macOS、Linux）都有其独特的通知机制。

  2. Docker 隔离 Docker 容器的隔离限制了它们直接访问主机操作系统资源的能力。

  3. 依赖管理需要处理每个操作系统不同的通知库和依赖项。

🧾 许可证

麻省理工学院

💻 贡献

欢迎提出问题和请求！

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.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • First observedsend_notification
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.1/5.0

Scored across 1 tool

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
ResponsivenessUnresponsive

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches