LabscoMCP early access ↗
zudsniperMCP SERVER

Webhook Notifications MCP

Push a message out of the session to the webhook you configured, so a finished run reaches you rather than sitting in the transcript.

by zudsniper ↗Notifications & Alerting to HumansCommunity

LABSCO SUMMARY

An outbound pipe set up once: the agent writes the message, never the address.

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.

What it is

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.

What you get

  • Outbound notification from inside the agent: notify sends a message with an optional title and template, and full_notify adds a link and an image, plus a priority, attachments and action buttons on ntfy.
  • A destination fixed by configuration rather than by argument: the address comes from WEBHOOK_URL and its kind from WEBHOOK_TYPE, so a call carries the message, never the destination.

Requirements

A webhook you can post to: its address in WEBHOOK_URL and its kind in WEBHOOK_TYPE.

Setup effort

One command plus credentials — npm install -g mcp-notifications, then supply credentials