MCP-Pushover Bridge

Provides a dedicated MCP server to push notifications via Pushover using MCP-compatible clients.

typescript

1

GitHub Stars

typescript

Language

5 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "pyang2045-mcp-pushover": {
      "command": "npx",
      "args": [
        "mcp-pushover"
      ],
      "env": {
        "PUSHOVER_DEFAULT_USER": "your_user_key",
        "PUSHOVER_DEFAULT_TOKEN": "your_app_api_token"
      }
    }
  }
}

You can run an MCP server that lets your AI assistant push notifications to your mobile device via Pushover. This makes it easy to receive instant alerts when tasks complete, issues arise, or you want quick reminders, improving your workflow and response times.

How to use

Use this MCP server with your MCP-enabled client to send push notifications to your mobile device. Create a notification by supplying message content and optional metadata like a title, priority, and sound. You can trigger notifications from automated tasks, alerts, or direct prompts to your assistant. The server handles communication with the Pushover API and applies configurable retry logic to ensure delivery even if network hiccups occur.

How to install

Prerequisites: you need Node.js and npm installed on your machine.

# Quick Start (Recommended)
npx mcp-pushover

# Global Installation
npm install -g mcp-pushover
mcp-pushover

# From Source
git clone https://github.com/pyang2045/mcp-pushover.git
cd mcp-pushover
npm install
npm run build
npm start

Configuration and setup

To enable notifications, configure Pushover credentials in environment variables. You can place these in a .env file or export them in your session.

# Required (unless provided as tool parameters)
PUSHOVER_DEFAULT_TOKEN=your_pushover_app_token
PUSHOVER_DEFAULT_USER=your_pushover_user_key

# Optional
NODE_ENV=production
LOG_LEVEL=info
RETRY_MAX_ATTEMPTS=3
RETRY_INITIAL_DELAY=1000

Pushover setup and test

Before you start, set up a Pushover account and application, then test your credentials.

# Test credentials
curl -s \
  --form-string "token=YOUR_API_TOKEN" \
  --form-string "user=YOUR_USER_KEY" \
  --form-string "message=Test from MCP-Pushover" \
  https://api.pushover.net/1/messages.json

Claude Desktop integration

If you use Claude Desktop, add an MCP server entry to load this bridge and supply credentials via environment variables.

{
  "mcpServers": {
    "pushover": {
      "command": "npx",
      "args": ["mcp-pushover"],
      "env": {
        "PUSHOVER_DEFAULT_TOKEN": "your_app_api_token",
        "PUSHOVER_DEFAULT_USER": "your_user_key"
      }
    }
  }
}

Available tool

pushover_send_message sends a notification to your mobile device with configurable options.

Parameters include message, user_key, api_token, title, priority, and sound. Use these to tailor each notification.

Security

API tokens are not logged. Credentials can be supplied via environment variables. All Pushover API calls use HTTPS.

Available tools

pushover_send_message

Send a notification via Pushover to your mobile device. You can specify message, user_key, api_token, title, priority, and sound to customize the alert.