pushover-mcp
This server allows you to send customizable push notifications to your registered Pushover devices via a single send_notification tool.
Parameters:
message(required): The body text of the notification.title(optional): A custom title; defaults to your Pushover app name.priority(optional): How insistent the alert is:lowest— silent, no notificationlow— no sound or vibrationnormal— default behaviorhigh— bypasses quiet hoursemergency— repeats until acknowledged
sound(optional): A specific notification sound (e.g.,pushover,bike,bugle,siren,magic); omit to use the device default.url(optional): A supplementary URL to attach.url_title(optional): A clickable label for the supplementary URL.device(optional): Target a specific registered device by name; omit to send to all devices.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@pushover-mcp Send a push notification 'Deploy finished' with high priority to my phone"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
pushover-mcp
A tiny MCP server that sends push notifications through Pushover.
It exposes one tool:
send_notification— send amessagewith optionaltitle,priority,sound,url,url_title, anddevice.
Two parameters are designed to read well to an LLM:
priorityuses names instead of numbers:lowest,low,normal(default),high,emergency(repeats until acknowledged).soundis an allowlist fetched live from Pushover's sounds API once at startup and cached for the process. If that fetch fails (offline, or no token), it falls back to a baked-in list so the server still starts.
Setup
Get your user key from your Pushover dashboard and create an application to get an API token at https://pushover.net/apps/build.
Install dependencies:
uv sync
Related MCP server: mcp-gotify
Run
The server reads PUSHOVER_TOKEN and PUSHOVER_USER from the environment.
With 1Password (recommended)
.env holds secret references (op://…), not the secrets themselves.
Launch through op run to resolve them at runtime:
op run --env-file=.env -- uv run pushover_mcp.pyWith plain env vars
PUSHOVER_TOKEN=... PUSHOVER_USER=... uv run pushover_mcp.pyUse with Claude Code / Claude Desktop
Launching via op run keeps secrets out of the MCP config entirely:
claude mcp add pushover -- \
op run --env-file=/Users/charlesbine/Documents/prog/mcp/pushover/.env -- \
uv run --directory /Users/charlesbine/Documents/prog/mcp/pushover pushover_mcp.pyOr as JSON (e.g. claude_desktop_config.json):
{
"mcpServers": {
"pushover": {
"command": "op",
"args": [
"run", "--env-file=/Users/charlesbine/Documents/prog/mcp/pushover/.env", "--",
"uv", "run", "--directory", "/Users/charlesbine/Documents/prog/mcp/pushover", "pushover_mcp.py"
]
}
}
}Tests
uv run pytestTests mock the network and use no real credentials, so they run offline.
Run them with plain uv run pytest (not via op run) so the import-time sound
fetch falls back instead of calling the live API. GitHub Actions runs the suite
on every push and pull request across Python 3.10–3.13 (see
.github/workflows/ci.yml).
Run over HTTP (Docker)
The server speaks stdio by default. Set MCP_TRANSPORT=streamable-http to serve
over Streamable HTTP instead, so any
HTTP-capable MCP client can connect at http://<host>:8000/mcp. The Docker image
sets this for you.
docker build -t pushover-mcp .
docker run --rm -e PUSHOVER_TOKEN -e PUSHOVER_USER -p 8000:8000 pushover-mcpAs a Compose service — credentials live in this container's own environment (an
env_file or Docker secrets), so they stay isolated to this tool:
services:
pushover-mcp:
build: .
environment:
PUSHOVER_TOKEN: ${PUSHOVER_TOKEN}
PUSHOVER_USER: ${PUSHOVER_USER}
restart: unless-stoppedThe HTTP endpoint is unauthenticated, so don't expose it publicly — keep it on a
private/internal network (and drop the published ports: if a co-located client
reaches it over the Compose network).
License
MIT © Charles Bine
Available Tools
1 toolsend_notificationA
Send a push notification via Pushover to your registered devices.
Inputs: message (required), title, priority, sound, +3 more. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion between tools.
With a single tool, naming is trivially consistent.
A single tool is appropriate for a focused server that sends push notifications via Pushover.
The tool covers the primary action of sending notifications, but lacks secondary features like delivery status or recipient management, which are minor gaps.
Maintenance
Related MCP Connectors
Push notifications with personalized sounds - manage and trigger your vybits via MCP
Push notifications for AI agents - send instant iPhone notifications from any MCP client.
MCP server exposing the AceDataCloud Fish Audio API (text-to-speech with voice conditioning)
A very simple remote MCP server that greets you, with a custom icon.
Related MCP Servers
- AlicenseAqualityDmaintenanceA simple MCP server that can send notifications on mac devices.516 npm26MIT
- AlicenseBqualityDmaintenanceMCP server for sending Gotify push notifications to your devices.1MIT
- AlicenseAqualityDmaintenanceA lightweight MCP server that enables sending native desktop notifications with action buttons and text replies, compatible with any MCP client.129 npm1MIT
- AlicenseCqualityDmaintenanceMCP server for sending notifications to ntfy.sh or self-hosted ntfy instances.213 npmMIT