Pushover Notifications

io.github.joshuawowkPublished by GitHub account joshuawowkv1.0.1Updated Oct 26, 2026

Send push notifications to your devices and groups via the Pushover API.

VerifiedSTDIODesktop onlyProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

Sends Pushover push notifications to your phone, devices and groups, and checks delivery limits and emergency receipts.

What you can do
  • Send notifications with priority, sounds and emergency receipt options
  • Validate a Pushover user or group key
  • List available notification sounds and check account limits
  • Check or cancel emergency notification receipts
When to use it
Useful when you want an assistant to alert you or a team on phones and devices, for example when a long task finishes, a build fails, or a monitoring check needs a human. Also handy for testing Pushover credentials and limits.
Requirements
Runs as a local process, typically the published container image via Docker, or from Python source with the mcp and httpx packages. Needs a Pushover application API token in PUSHOVER_TOKEN; PUSHOVER_USER_KEY is optional as a default recipient. Optional PUSHOVER_DEVICE and, for HTTP mode, PUSHOVER_MCP_ALLOWED_HOSTS. Requires network access to the Pushover API.
Before you install
Requires a Pushover API token and user key as secrets; anyone with them can send notifications to that account. Sending notifications is an outward action that reaches real devices and groups, and emergency-priority messages can repeat until acknowledged. Self-hosting over HTTP exposes an endpoint on port 8735, so restrict hosts and network exposure.

Installation

In SourceWeft

  1. Open Pushover Notifications in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

pushover-mcp

[Release] [License: MIT]

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)

VariableRequiredDescription
PUSHOVER_TOKENyesPushover application API token
PUSHOVER_USER_KEYnoDefault user/group key (tools accept a user override)
PUSHOVER_DEVICEnoDefault device name(s), comma-separated
PUSHOVER_MCP_ALLOWED_HOSTSHTTP onlyHost: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)

json
{  "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

bash
cp .env.example .env   # fill in your tokensdocker compose up -d   # serves MCP at http://<host>:8735/mcp

Run from source

bash
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

Source: README.md at commit 70a659f

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the package type cannot run in the sandbox.

Version history

2
  1. v1.0.1LatestOct 20, 2026
  2. v1.0.0Sep 26, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts