home / mcp / pushover mcp server

Pushover MCP Server

Sends notifications via Pushover.net from MCP-enabled AI agents.

Installation
Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "ashiknesin-pushover-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "pushover-mcp@latest",
        "start",
        "--token",
        "YOUR_TOKEN",
        "--user",
        "YOUR_USER"
      ]
    }
  }
}

You can send notifications from MCP-enabled AI agents to Pushover.net by using a dedicated Pushover MCP Server. This integration lets your agents trigger real-time alerts on your devices, with options for priority, sound, and contextual links.

How to use

Install and run the Pushover MCP Server locally or remotely, then connect it to your MCP client. The server exposes a single tool named send that you can call to deliver a Pushover notification. You only need your Pushover application token and your user key. In your MCP client, trigger the send tool when you want to push a message to Pushover.

How to install

Prerequisites you need before installation: a supported Node.js environment and npm or npx available on your system.

# Ensure Node is installed (check with node -v and npm -v)

# Run the MCP server using npx with your Pushover credentials
npx -y pushover-mcp@latest start --token YOUR_TOKEN --user YOUR_USER

Configuration and usage notes

The Pushover MCP Server requires two credentials from Pushover.net: an application token and a user key. Provide these when starting the server so it can authenticate and send notifications on your behalf.

When you configure your MCP client, you can use a project-level or global setup to start the server. The server is designed to be accessible to your MCP agent via standard initialization commands. You can opt into automatic sending or explicitly request notification delivery as needed.

Example tool usage

The server exposes the send tool. You can supply a message and optional fields like title, priority, sound, and a URL to include with the notification.

Security considerations

Treat your Pushover credentials as sensitive. Do not expose YOUR_TOKEN or YOUR_USER in public code or logs. Use environment isolation and secure storage practices when handling credentials in automation environments.

Troubleshooting

  • Ensure you pass the correct token and user key.
  • Verify that Node.js and npm/npx are available on the system.
  • Check that the MCP client can reach the MCP server if you’re hosting remotely.
  • Review any error messages from the tool call to adjust parameters (e.g., missing message, invalid priority).

Examples

{
  "name": "send",
  "params": {
    "message": "Hello from AI",
    "title": "AI Notification",
    "priority": 1
  }
}
```

```bash
# Direct command example shows how you would start the MCP server with credentials via npx
npx -y pushover-mcp@latest start --token YOUR_TOKEN --user YOUR_USER

Available tools

send

Sends a notification via Pushover with options for message, title, priority, sound, and optional URL and device targeting.