About Pushover Notifications
Pushover Notifications is an MCP server for sending Pushover push notifications to phones and other devices. It supports notification delivery and related validation, sound, limit, and receipt operations.
Key features
- 01Send notifications with priority and sounds
- 02Validate users
- 03List available sounds
- 04Check and cancel emergency receipts
- 05Get API limits
Use cases
- 01Send an alert to a phone from an MCP client
- 02Validate a Pushover user key
- 03Check or cancel an emergency notification receipt
MCP support
Exposes Pushover API operations as MCP tools. It runs over stdio or Streamable HTTP and requires a Pushover application token.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
docker run -i --rm -e PUSHOVER_TOKEN -e PUSHOVER_USER_KEY ghcr.io/joshuawowk/pushover-mcp:1.0.1PUSHOVER_TOKENSecretPushover application API tokenPUSHOVER_USER_KEYSecretDefault Pushover user or group keyLocal servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
ghcr.io/joshuawowk/pushover-mcp:1.0.1stdioTools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEpushover-mcp
An MCP server for the Pushover notification API. Send push notifications to your phone and other devices from any MCP client. Single-file Python; runs over stdio or streamable HTTP.
Tools
send (full parameter coverage incl. priority, sounds, and emergency receipts), validate_user, list_sounds, get_limits, check_receipt, cancel_receipt.
Configuration (environment variables)
| Variable | Required | Description |
|---|---|---|
PUSHOVER_TOKEN | yes | Pushover application API token |
PUSHOVER_USER_KEY | no | Default user/group key (tools accept a user override) |
PUSHOVER_DEVICE | no | Default device name(s), comma-separated |
PUSHOVER_MCP_ALLOWED_HOSTS | HTTP only | Host:port values the DNS-rebinding guard accepts |
Install
The server ships as a multi-arch container image on GHCR (and is listed in the MCP Registry as io.github.joshuawowk/pushover-mcp). Run with no arguments the image serves streamable HTTP on port 8735; pass --stdio for a stdio server.
Docker, stdio (e.g. Claude Desktop)
{
"mcpServers": {
"pushover": {
"command": "docker",
"args": ["run","-i","--rm","-e","PUSHOVER_TOKEN","-e","PUSHOVER_USER_KEY","ghcr.io/joshuawowk/pushover-mcp:latest","--stdio"],
"env": { "PUSHOVER_TOKEN": "your-app-token", "PUSHOVER_USER_KEY": "your-user-key" }
}
}
}
Self-host as a streamable-HTTP server
cp .env.example .env # fill in your tokens
docker compose up -d # serves MCP at http://<host>:8735/mcp
Run from source
pip install "mcp>=1.2,<2" "httpx>=0.27"
python pushover_mcp.py # stdio (same as --stdio)
python pushover_mcp.py --http --host 0.0.0.0 --port 8735 # HTTP
License
MIT © jwowk · https://jwowk.net
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.