send
Send a notification via Pushover
LABSCO SUMMARY
A long job can tell you it finished, on your phone.
One tool with the fields Pushover itself takes: priority decides whether it interrupts, sound decides what it sounds like, and url with url_title puts something tappable in the notification rather than a bare string. Delivery only — nothing here reads notifications back or reports whether one was opened.
What it is
A single-tool notification sender over Pushover, carrying the message, its title, priority, sound and an optional URL.
What you get
- send delivering a message with a title and a priority
- Device to reach one registered device rather than all of them
- Url and url_title to attach a tappable link, and sound to choose the alert tone
Requirements
A Pushover account with an application token and a user key, and a device registered to receive the notification. MIT licensed.
Setup effort
One command — npx -y pushover-mcp@latest start --token <YOUR_TOKEN> --user <YOUR_USER>
USE CASES
01
Getting told when something you started finishes
Send the result to your phone with a priority that matches how much it matters, and a link back to the build, the dashboard or the file it produced.
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.
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": {
"pushover-mcp": {
"command": "npx",
"args": [
"-y",
"pushover-mcp@latest",
"start",
"--token",
"<YOUR_TOKEN>",
"--user",
"<YOUR_USER>"
]
}
}
}npx
TERMINAL
npx -y pushover-mcp@latest start --token <YOUR_TOKEN> --user <YOUR_USER>
