Labsco
MCP SERVER

MCP Server Notifier

by tuberrabbit

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

Notifications & Alerting to HumansVerified
Summary
A single-purpose outbound pipe: configured once, called with nothing but text.

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: message is the only thing the model controls.

What it is

A webhook notifier with a single call, notify-feishu, which takes a message and posts it to the address held in WEBHOOK_URL.

What you get
  • Outbound notification from inside the agent: notify-feishu takes a message and posts it to the configured webhook.
  • A destination fixed by configuration rather than by argument: the address comes from WEBHOOK_URL and its kind from WEBHOOK_TYPE, so the call itself carries nothing but the text.
Requirements

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

Setup effort

One command plus a key — npm install -g mcp-server-notifier, then supply credentials