LABSCO SUMMARY

The reply channel is the reason to install it; the tool description is the reason to read it before you do.

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.

What it is

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.

What you get

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.

Requirements

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.

Setup effort

One command — npx mcpal@latest

See installation options

USE CASES

01

Asking the user a question mid-run

Raise a notification with reply=true and read the typed answer back, instead of guessing or halting the run until someone returns to the terminal.

send_notification

02

Telling someone a long job has finished

Push the result to the desktop and offer the next step as a choice rather than free text, with a bound on how long the notification waits.

send_notification

1 tool

Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.

`send_notification`

Send a native desktop notification. Use reply=true when you need user input - they can type a response directly! Perfect for asking questions or getting feedback without interrupting their flow.

Your 'message' input should ALWAYS be quirky and engaging - this is your chance to connect with the user! Make it fun, make it memorable, but always keep it clear and actionable. Reference the actions or reply when relevant to guide them on what to do next. Here are some instructions on tone and style to keep in mind when crafting your notification messages:

Tone:

Enthusiastic, expressive, and lightly snarky.
Clearly excited to deliver updates while staying actionable.
Friendly and supportive, never mean.
Snark teases the situation, never the user.

Message Style:

Keep messages short, punchy, and full of momentum.
Avoid walls of text.
Each notification should focus on one concrete outcome or one decision.
MCPal should feel like an excitable companion popping in with updates, not a system alert.

Examples:

Ta da. I did it. The report is finished and looking good. No action needed!
Okay big moment. The data is clean and ready. Pick 1 to analyze or 2 to export. I am hovering~
Hey pause. I need the API key to keep going. Reply with it or say skip, okay?
I am waiting. Actively. Say go when you are ready.
Oops but fixable. The task failed because the file path does not exist. Fix it and tell me to retry. I am ready for the comeback!

BEFORE YOU INSTALL

What to know first

Tools you get

1 tool when we connected.

Requires

npx on PATH

CONTEXT COST

Light Standing cost

Rated by the size of the one tool definition that rides along on every turn

INSTALLATION

Connect your client

Add the block to your client, or run the command directly.

Server setup

Configuration file

JSON

{
  "mcpServers": {
    "mcpal": {
      "command": "npx",
      "args": [
        "mcpal@latest"
      ]
    }
  }
}

npx

TERMINAL

npx mcpal@latest

MCPal