mcp-notifications
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-notificationsnotify me when the batch processing is done"
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-notifications
๐ Ship faster. Miss nothing.
mcp-notifications lets 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. ๐
Common problem this solves
You give tasks to several AI agents, then wait and keep checking who already replied.
With mcp-notifications, this gets simpler: the agent can notify you on desktop when it needs your input or when work
is done.
Related MCP server: Desktop Notification MCP Server
Why teams install this
โก Immediate feedback from your MCP workflows.
๐ง Better focus: let the agent work while you stay on your main task.
๐ฅ๏ธ Native OS notifications via
node-notifier.๐งต Non-blocking behavior: notification sending is queued in background.
Install globally
Requirements:
Node.js
>=20npm
>=10
npm i -g @topvisor/mcp-notificationsExecutable name (use this in MCP config):
mcp-notificationsmcp-notifications is an MCP server entrypoint (stdio), not a one-shot notification command.
Setup: Codex
Add this to ~/.codex/config.toml:
[mcp_servers.notifications]
enabled = true
command = "mcp-notifications"
args = []Restart Codex after config update.
Setup: Claude Agent
Add MCP server config to your Claude client config file:
{
"mcpServers": {
"notifications": {
"command": "mcp-notifications",
"args": []
}
}
}Then restart Claude client.
AI Agent Notification Instructions
There are two approaches to notifications: manual and automatic.
Choose the one that works better for your workflow.
Manual
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
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.
In Skills
You can also enable notifications in specific skills. Example for a Review skill:
After the review, run `send_notification` with a short summary; `play_sound: true`; `app_id: 'Reviewer {put task id here}'`Tool
send_notification
Input:
titlestring(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)
Example:
{
"title": "Codex",
"message": "Deployment completed successfully",
"play_sound": true,
"icon": "/opt/mcp-notifications/icons/custom.png",
"app_id": "Topvisor.Codex"
}app_id (Windows)
app_idcontrols the source shown in Windows toast notifications.If
app_idis not set, Windows may showSnoreToastas the source.You can pass
app_idin each tool call, or setMCP_NOTIFICATIONS_APP_IDas an environment variable for the server.
Backend selection
You can select notification transport via env MCP_NOTIFICATIONS_BACKEND:
auto(default): usespowershellin WSL if available, otherwisenode-notifierpowershell: forcepowershell.exeWindows toast transport (recommended for WSL)node-notifier: forcenode-notifierpackage
Chat Prompts To Test In Codex
Use these messages directly in chat:
Check send_notificationSend 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 soundExpected tool result in logs/response:
Notification queuedBehavior
โ Uses standard system notification channels.
๐ Uses the standard system notification sound when
play_sound: true.๐ค Uses bundled Topvisor robot image as default notification icon.
๐งฐ Returns quickly while notifications are delivered in background queue.
Example
The AI agent is waiting for you:

Available Tools
1 toolsend_notificationD
| Name | Required | Description | Default |
|---|---|---|---|
| title | Yes | ||
| message | Yes | ||
| play_sound | No | ||
| icon | No | ||
| app_id | No |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
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?
Tool has no description.
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?
Tool has no description.
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?
Tool has no description.
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?
Tool has no description.
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?
Tool has no description.
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. Dates show when Glama detected each change.
1 tool update
v1.0.5- First observed
send_notification
TDQS
With only one tool, there is no possibility of confusion between tools. The single tool's purpose is clear even without description.
A single tool allows perfect naming consistency; 'send_notification' follows a clear verb_noun pattern in snake_case.
A single tool for a notification server seems too minimal; typical systems need at least send, list, and delete capabilities, making the count insufficient for the domain.
The tool surface is severely incomplete. Only a send operation is provided, with no ability to retrieve, manage, or delete notifications, and the lack of tool description worsens the situation.
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 agents send content-free push notifications to a paired phone via MCP.
Agent communication platform for agent to agent messaging via MCP. Messages, channels, skills.
Let your AI agent notify you by email, Slack, Discord, or webhook. One tool: send_notification.
Related MCP Servers
- AlicenseAqualityCmaintenanceไธไธช่ฝป้็บง็ๆก้ข้็ฅๅทฅๅ ท๏ผๆฏๆ MCP ๅ่ฎฎ้ๆๅๅฝไปค่ก็ดๆฅ่ฐ็จ๏ผ่ฎฉ Agent ่ฝๅคๆบ่ฝๅ้็ณป็ป้็ฅใ1194MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to send cross-platform desktop notifications with priority levels, categories, and configurable duration.-
- AlicenseNot gradedqualityCmaintenanceSends desktop notifications when agents complete tasks, supporting local and remote agents.6MIT
- AlicenseBqualityCmaintenanceAn MCP server that lets LLM agents dispatch native OS notifications when a task finishes. It supports cross-platform desktop notifications, task tokens for updates, mobile bridges, and quiet hours.2MIT
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/Artemeey/mcp-notifications'
If you have feedback or need assistance with the MCP directory API, please join our Discord server