pushover_send_message
Send a notification via Pushover
LABSCO SUMMARY
The credentials being call parameters as well as environment defaults is what makes this more than a wrapper: a single install can address more than a single recipient.
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.
What it is
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.
What you get
- 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.
Requirements
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.
Setup effort
One command plus a key — npx mcp-pushover, then supply credentials
USE CASES
01
Getting told on your phone when something finishes
Send a Pushover notification from the client with the title, priority and sound set on the call itself — so a failure can be loud and a routine finish can be quiet.
1 tool
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool when we connected. It only sends; user_key and api_token can be passed per call instead of set in config. Priority 2 keeps alerting until acknowledged, and priority -2 sends no alert.
Requires
- npx on PATH
- PUSHOVER_DEFAULT_TOKEN in your environment
- PUSHOVER_DEFAULT_USER in your environment
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the one tool definition that rides along on every turn
INSTALLATION
Connect your client
Server setup
TERMINAL
npx mcp-pushoverMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"pushover": {
"command": "npx",
"args": [
"mcp-pushover"
],
"env": {
"PUSHOVER_DEFAULT_TOKEN": "<YOUR_PUSHOVER_DEFAULT_TOKEN>",
"PUSHOVER_DEFAULT_USER": "<YOUR_PUSHOVER_DEFAULT_USER>"
}
}
}
}
