LabscoMCP early access ↗
LyazSMCP SERVER

Windows Notification Server

Lets an assistant raise a Windows system notification — a title, a message, and optionally a sound — so a finished job reaches you when the window is not in front.

by LyazS ↗Notifications & Alerting to HumansCommunity

LABSCO SUMMARY

One tool, and it is the right one.

The value of a notification server is entirely in how little it asks of you: no account, no webhook, no service to sign up for — the notification surface is the one your operating system already has. Two consequences. It is Windows-only by construction, and it only goes one way: the assistant can tell you something happened, but nothing comes back.

What it is

A small Node.js MCP server whose whole job is to put a native Windows notification on screen. It exists for the moment a long task ends while you are looking at something else.

What you get

  • One tool that raises a Windows system notification — send_notification
  • A required title and message, so the notification says what happened without you opening anything
  • An optional sound, defaulting to on, for when a silent banner would be missed

Requirements

Windows, and Node.js. No account and no key. Clone the repository, npm install, then start it — the client config in the README points at a batch file wrapper, and the server can also be run directly with node against its entry script.

Setup effort

Build from source — get the source, then follow the steps on this page and add the configuration for your client