A notification that accepts a typed reply, an action button or a dropdown choice turns a one-way status ping into a question an agent can actually ask mid-run, which is a real gap in unattended work. The description does more than describe, though — it instructs the calling model on style, telling it the message input should always be quirky and engaging, which puts a voice decision inside a tool definition rather than in your hands.
A single-tool bridge to desktop notifications: send_notification puts a title and message in front of the user and can collect a typed reply, a chosen action or a dropdown selection.
- send_notification raises a native desktop notification with a title and message, which gives an unattended run a way to reach the person who started it.
- Reply=true turns the notification into an input: the user types a response directly into it and that response comes back to the caller, so a question can be asked mid-run instead of ending the run.
- Actions and dropdownLabel offer a choice rather than free text, and timeout bounds how long the notification waits for one.
No account and no key. The notification is raised on the machine the server runs on, so the person you want to reach is the one sitting at it.
One command — npx mcpal@latest