mcp-notifications
About
Desktop system notifications for MCP agents — instant feedback on tasks, failures, and workflow events.
Details
- Author
- artemeey
- Categories
- Productivity
Jump to
Setup
Install mcp-notifications in your MCP client (Claude Desktop, Cursor, Windsurf, and others).
Repository: https://github.com/artemeey/mcp-notifications
Follow the installation instructions in the repository README, then restart your MCP client.
- Send a desktop notification— Ask the agent to callsend_notificationwith a custom title and message when a task finishes.
- Include an audible alert— Setplay_sound: trueso the notification plays the system sound on delivery.
- Customize the notification source on Windows— Pass anapp_idto control the app name shown in the toast, or set it globally via theMCP_NOTIFICATIONS_APP_IDenvironment variable.
- Use a custom icon— Provide aniconpath to replace the default image in the notification.
mcp-notificationslets your MCP agent send desktop notifications for completed tasks, failures, and important updates.
This is especially useful for console AI agents, because they usually have no built-in notifications by default.
No more checking chats every minute.
No more silent agent responses.
Just visible, reliable feedback on your desktop. 🔔
You give tasks to several AI agents, then wait and keep checking who already replied.
Withmcp-notifications, this gets simpler: the agent can notify you on desktop when it needs your input or when work is done.
- ⚡ Immediate feedback from your MCP workflows.
- 🧠 Better focus: let the agent work while you stay on your main task.
- 🖥️ Native OS notifications vianode-notifier.
- 🧵 Non-blocking behavior: notification sending is queued in background.
Executable name (use this in MCP config):
mcp-notificationsis an MCP server entrypoint (stdio), not a one-shot notification command.
[mcp_servers.notifications] enabled = true command = "mcp-notifications" args = []
Add MCP server config to your Claude client config file:
{ "mcpServers": { "notifications": { "command": "mcp-notifications", "args": [] } } }
There are two approaches to notifications: manual and automatic.
Choose the one that works better for your workflow.
In a task where you want to be notified, explicitly ask the agent. Example:
Count files in the project; after the task is fully complete, notify me with sound.
You can also define sound, topic, and frequency rules inside a specific chat. Example:
Notify me about your replies without sound, include the reply text, and use title: "Large Refactoring"
Automatic notifications can be configured globally or per project.
Example instruction to enable automatic notifications for agent replies:
Send send_notification after your replies (actual task time >5 seconds or many steps); play_sound: false; app_id: '{put your chat name here}'`
Time is a rough threshold and depends on model behavior, so adjust this instruction to your own preferences.
You can also enable notifications in specific skills. Example for a Review skill:
After the review, runsend_notificationwith a short summary;play_sound: true;app_id: 'Reviewer {put task id here}'
- title`string(required)
- messagestring(required)
- play_soundboolean(optional, default:false)
- iconstring(optional, absolute or relative path to image file)
- app_idstring(optional, Windows App User Model ID for toast source)
{ "title": "Codex", "message": "Deployment completed successfully", "play_sound": true, "icon": "/opt/mcp-notifications/icons/custom.png", "app_id": "Topvisor.Codex" }
- app_idcontrols the source shown in Windows toast notifications.
- Ifapp_idis not set, Windows may showSnoreToastas the source.
- You can passapp_idin each tool call, or setMCP_NOTIFICATIONS_APP_IDas an environment variable for the server.
You can select notification transport via envMCP_NOTIFICATIONS_BACKEND:
- auto(default): usespowershellin WSL if available, otherwisenode-notifier
- powershell: forcepowershell.exeWindows toast transport (recommended for WSL)
- node-notifier: forcenode-notifierpackage
Send a notification without sound: title "Test", message "Check"
Send a notification with sound: title "Test", message "Check"
Send a notification with app_id "Topvisor.Codex": title "Test", message "Check"
Send 3 test notifications in a row without sound
- ✅ Uses standard system notification channels.
- 🔊 Uses the standard system notification sound whenplay_sound: true.
- 🤖 Uses bundled Topvisor robot image as default notification icon.
- 🧰 Returns quickly while notifications are delivered in background queue.
The 1Password MCP server creates a bridge that allows MCP clients such as Codex and Kiro to manage your 1Password Environments with secure authorization prompts.
This is the 1st, easiest, and cheapest PPT, slides, presentation AI generation MCP Server in the world.
Persistent memory for any AI assistant. Zero token cost until recall. Stores memories in local SQLite, ranks by 6-factor scoring, returns results 79% smaller than JSON. Works with Claude, ChatGPT, Grok, Cursor, Windsurf, and any MCP client.
A MCP server that enables AI assistants to interact with Anki, the spaced repetition flashcard application.
Enables LLM clients to interact with macOS applications through AppleScript. Built using the @beyondbetter/bb-mcp-server library, this server provides safe, controlled execution of predefined scripts with optional support for arbitrary script execution.
An MCP server for WordPress plugin audits
Turn your AI assistant into a digital marketing hub that creates, organizes, and analyzes links and QR Codes on demand.
Connect AI clients to Cal.com scheduling through the Model Context Protocol using the hosted server at mcp.cal.com or a local instance.
Sync Calendars, Scheduling Links, AI Executive Scheduling Assistant, Unified Calendar
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.



