A
licenseNot graded
qualityC
maintenancemacOS Notification MCP enables AI assistants to trigger native macOS sounds, visual notifications, and text-to-speech. Built for Claude and other AI models using the Model Context Protocol.
37
MIT
MCP Notify Server
by Cactusinhand
📢 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 pywin32macOS
# 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.のようなプロンプトを追加するだけで、通知をトリガーするための AI へのタスク入力が完了します。
カーソルでは、このプロンプトをCursor Settings -> Rulesでルールとして追加できるため、毎回手動で入力する必要はありません。
⚡️ VSCode + Copilot で使用する場合:
サービスマネージャーuv/uvxをインストールします:
pip install uvVSCode 設定にサービスを追加します。
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": {} } } }VSCodeの最新バージョンを使用していることを確認してください。MCPサービスが自動的に実行されます。
VSCode を開く → Copilot を有効にする → エージェント モードに切り替えます。
と入力すると、#send_notification オプションが表示されます。
エージェントに依頼します: #send_notification を実行します (通知は自動的に処理されます)。
エージェント モードの Copilot はデスクトップ通知を送信できるようになりました。
🐳 Docker で実行する
環境互換性の問題により、現在ご利用いただけません。ホストOSがWindows、macOS、Linuxのいずれであっても、Dockerコンテナがホスト通知をトリガーする必要がある場合、ソリューションははるかに複雑になり、ネイティブ通知を直接使用することは通常不可能です。
主な問題点:
OS 固有の通知システム 各オペレーティング システム (Windows、macOS、Linux) には独自の通知メカニズムがあります。
Docker の分離 Docker コンテナの分離により、ホスト オペレーティング システムのリソースに直接アクセスする機能が制限されます。
依存関係の管理 オペレーティング システムごとに異なる通知ライブラリと依存関係を処理する必要があります。
🧾 ライセンス
マサチューセッツ工科大学
💻 貢献
問題やプルリクエストを歓迎します!
Available Tools
1 toolsend_notificationC
Send system notification with optional sound
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| title | Yes | ||
| message | Yes | ||
| play_sound | No | ||
| timeout | No |
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 tool update
- First observed
send_notification
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
Related MCP Connectors
Push notifications for AI agents - send instant iPhone notifications from any MCP client.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Let your AI agent notify you by email, Slack, Discord, or webhook. One tool: send_notification.
Build agents to automate any background task. Works with your ChatGPT/Claude subscription.
Related MCP Servers
- AlicenseBqualityCmaintenanceA Model Context Protocol server that allows AI agents to play notification sounds when tasks are completed.132 npm14Apache 2.0
- AlicenseCqualityFmaintenanceA Model Context Protocol server for macOS that enables AI assistants to play system sounds for audio feedback, offering informational, warning, and error sound options.41MIT
- AlicenseAqualityCmaintenanceA persistent state machine and notification system for AI agents to manage complex, multi-step workflows via the Model Context Protocol, preventing context drift by maintaining structured checklists and sending desktop alerts.1410 npm2Apache 2.0