send_notificationLABSCO SUMMARY
The only decisions this asks of you are what to say and whether it should interrupt, which is the whole of what a notifier should be asking.
icon and app_id are about attribution, and attribution starts to matter the moment more than a single thing is allowed to interrupt you. There is nothing to read back and nothing to configure, so what it costs to keep installed is the size of its tool definition. The description that ships with send_notification is empty, so the parameter names are the contract — anything about how the notification is presented has to be established by trying it.
What it is
A single-tool notifier: send_notification takes a title and a message, with icon, app_id and play_sound shaping how it arrives.
What you get
- send_notification raises a notification carrying a title and a message.
- Icon and app_id travel with the call, so a notification arrives attributed rather than anonymous.
- play_sound is decided per call, so routine progress can stay silent while something that needs attention does not.
Requirements
No credentials are configured; the call carries everything it needs.
Setup effort
One command — npm i -g @topvisor/mcp-notifications
USE CASES
01
Being told when a long job is done
Raise a desktop notification with a title, message and icon at the point the agent finishes something, and decide on that call whether it makes a sound — so a long build can be silent and a failure is not.
1 tool
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool when we connected. MCP_NOTIFICATIONS_BACKEND picks the transport, and MCP_NOTIFICATIONS_APP_ID sets the name Windows shows; left unset, it may show SnoreToast. A success means the notification was queued, not seen.
Requires
- Node.js >=20
- npm >=10
Where it runs
Both documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the one tool definition that rides along on every turn
INSTALLATION
Connect your client
Server setup
TERMINAL
npm i -g @topvisor/mcp-notificationsMCP Clients
Codex
CODEX · TOML
[mcp_servers.notifications]
enabled = true
command = "mcp-notifications"
args = []Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"notifications": {
"command": "mcp-notifications",
"args": []
}
}
}
