notify
Send a simple notification with body, optional title, and optional template (e.g., 'status', 'question', 'progress', 'problem')
Push a message out of the session to the webhook you configured, so a finished run reaches you rather than sitting in the transcript.
LABSCO SUMMARY
Because the destination lives in WEBHOOK_URL and WEBHOOK_TYPE rather than in the arguments, the agent cannot choose who to notify at call time — a server instance means a destination, fixed. That is also what makes it cheap to expose: the model decides what a notification says, and with full_notify what it links to, but never where it goes.
A webhook notifier for Discord, Slack, Microsoft Teams, Feishu, ntfy or a custom endpoint, with two tools, notify and full_notify, that post to the address in WEBHOOK_URL. Maintained by zudsniper as the successor to tuberrabbit's original project.
A webhook you can post to: its address in WEBHOOK_URL and its kind in WEBHOOK_TYPE.
One command plus credentials — npm install -g mcp-notifications, then supply credentials
USE CASES
Have the agent post its own completion notice to the channel you already watch, instead of leaving it for you to find.
Listed in project code.
notifySend a simple notification with body, optional title, and optional template (e.g., 'status', 'question', 'progress', 'problem')
full_notifySend a detailed notification with advanced options (link, image, priority, attachments, actions, template data)
BEFORE YOU INSTALL
2 tools registered in the project's code.
The documented client runs the server on your machine.
INSTALLATION
npm install -g mcp-notifications{
"mcpServers": {
"notifier": {
"command": "npx",
"args": [
"-y",
"mcp-notifications"
],
"env": {
"WEBHOOK_URL": "https://ntfy.sh/webhook-url-example",
"WEBHOOK_TYPE": "ntfy"
}
}
}
}