That is the difference between notifying yourself and notifying whoever is on call, without standing up a second server for the second destination. priority and sound exist for the same reason at the message level — the notification that a build finished and the notification that it failed do not have to feel the same. Nothing reads back, so this is a one-way channel and any acknowledgement has to happen somewhere else.
A single-tool bridge to Pushover: pushover_send_message posts a notification, with the application token and user key either configured up front or passed per call.
- pushover_send_message delivers a notification carrying a title and a message.
- Priority and sound ride on the same call, so an alert that needs attention can be made to arrive differently from a routine status update.
- api_token and user_key are parameters as well as configuration, so a single install can send to more than one Pushover application or recipient.
A Pushover account with an application token and a user key, supplied as PUSHOVER_DEFAULT_TOKEN and PUSHOVER_DEFAULT_USER; the same values can also be passed on the call as api_token and user_key.
One command plus a key — npx mcp-pushover, then supply credentials