mcp-server-notify
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-server-notify任务完成后通知我"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-server-notify
一个轻量级的桌面通知工具,支持 MCP 协议集成和命令行直接调用,让 Agent 能够智能发送系统通知。
特性
🔔 发送系统桌面原生通知
🤖 完整的 MCP 协议支持,轻松集成各类 Agent 工具
🎵 可自定义声音和图标(本地文件或URL)
📱 跨平台支持(基于 node-notifier)
🎯 支持点击通知后激活指定应用、URL或可执行文件。
⚡ 极致轻量,开箱即用,无需复杂配置
Related MCP server: MCPal
使用方法
1. MCP服务
使用 npm
集成到 Cursor、Claude Code 或其他支持 MCP 协议的编辑器和 Agent 工具中:
{
"mcpServers": {
"notify": {
"command": "npx",
"args": ["-y", "@6starlong/mcp-server-notify"]
}
}
}使用示例
配置完成后,您可以通过以下方式触发通知:
- "任务完成后通知我"
- "测试全部通过了,庆祝一下"
- "发现安全漏洞,用警告音效和图标通知我"
- "通知我代码审核结果,点击时激活 Code"
- "帮我设置一个番茄钟,25分钟后提醒我休息"你可以通过在 ~/rules/notify.md 中创建自定义规则来避免每次手动输入这些偏好设置。例如,设置默认的通知样式、常用的声音文件路径、或特定项目的通知行为。
注意事项
默认设置:系统使用 coding.png 作为默认图标,done.wav 作为默认提示音
资源管理:支持本地文件路径和网络URL,网络资源可能有加载延迟,系统会自动降级处理(默认3秒)
静音模式:对于频繁通知,可以指定静音模式避免干扰
应用关联:点击通知后返回原应用(Windows)或打开指定的URL、程序、可执行文件。
2. 命令行使用
# 安装
npm install -g @6starlong/mcp-server-notify
# 查看帮助
mcp-notify -h
# 基本通知
mcp-notify -c "标题" "消息内容"
# 流程通知
mcp-notify -c "任务完成" "代码编译成功" --open Code
# 自动化任务通知
mcp-notify -c "测试通过" "所有单元测试已通过" --sound C:\\Windows\\Media\\tada.wav
# 集成到脚本中
npm run build && mcp-notify -c "构建成功" "可以开始部署了"3. 编程接口
import { sendNotification } from '@6starlong/mcp-server-notify'
await sendNotification('标题', '消息', {
icon: './icon.png', // 本地文件或URL,false禁用
sound: './sound.wav', // 本地文件或URL,false禁用
open: 'Code', // 点击通知后要激活的应用名称
})开发和测试
# 构建项目
pnpm run build
# 测试
pnpm test
# 开发模式(启动MCP服务器)
pnpm run dev许可证
MIT License
贡献
欢迎提交问题和PR!
Available Tools
1 toolsend_notificationA
发送系统桌面通知。可用于任务完成提醒、状态更新、重要事件通知等场景。支持自定义图标、声音和点击通知打开指定应用。
| Name | Required | Description | Default |
|---|---|---|---|
| icon | No | 图标设置(可选):string(文件路径/URL)、false(禁用图标)、不传表示使用默认图标 | |
| open | No | 点击通知后要激活的应用名称(可选) | |
| sound | No | 声音设置(可选):string(文件路径/URL)、false(静音)、不传表示使用默认声音 | |
| title | Yes | 通知标题,应该简洁明了地概括通知的主要内容 | |
| message | Yes | 通知的详细内容,可以包含具体信息和上下文 |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description discloses the tool's core behavior (sending a desktop notification) and mentions customization options (icon, sound, click-to-open). However, it does not address permission requirements, failure behavior, or whether notifications are disruptive, leaving some behavioral gaps.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the action, then scenarios, then features. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers purpose, scenarios, and feature highlights, while the schema handles parameter constraints. Given no output schema, it is adequately complete for a simple notification tool, though it could mention potential permission prerequisites.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the baseline is 3. The description merely echoes the schema's custom icon/sound/open features without adding new semantic details about the parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with 'Send system desktop notification' (发送系统桌面通知), a specific verb+resource pair, and lists concrete use cases (task completion reminders, status updates, important events), making the tool's purpose unmistakable even without sibling context.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly states applicable scenarios ('可用于任务完成提醒...'), providing clear when-to-use guidance. No alternatives are named because there are no sibling tools, but the context is sufficient.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
TDQS
Only one tool exists, so there is no possibility of confusion. The purpose of sending a system desktop notification is clearly defined and distinct.
The tool name 'send_notification' follows a clear verb_noun pattern. While the set is minimal, the naming is consistent and descriptive.
A single tool is below the typical 3-15 range and feels thin for a server. However, for a narrow purpose like sending notifications, it may be acceptable, but the overall utility is limited.
For the stated purpose of sending desktop notifications, the tool is complete. It supports custom icons, sounds, and click actions, covering the core needs without obvious gaps.
Maintenance
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
Push notifications for AI agents - send instant iPhone notifications from any MCP client.
Let your AI agent notify you by email, Slack, Discord, or webhook. One tool: send_notification.
Agent-native notes, tasks, dev-docs, vaults, sync & handoffs. MCP + OpenAPI dual surface.
MCP-first toolbox for agents: KV storage, auth, queue, and utility tools. Free in early access.
Related MCP Servers
- AlicenseDqualityDmaintenanceEnables MCP agents to send desktop notifications for completed tasks, failures, and important updates, providing visible and reliable feedback.1682Apache 2.0
- AlicenseNot gradedqualityCmaintenanceA lightweight MCP server that enables sending native desktop notifications with action buttons and text replies, compatible with any MCP client.161MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to send cross-platform desktop notifications with priority levels, categories, and configurable duration.
- FlicenseNot gradedqualityDmaintenanceMCP server for macOS native notifications with 67 AI brand icons and system sound support, enabling AI agents to send desktop notifications via one-line tool calls.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/6starlong/mcp-server-notify'
If you have feedback or need assistance with the MCP directory API, please join our Discord server