A CLI and MCP server for the Pushover notification service. Send and receive push notifications from the command line or integrate with AI assistants via the Model Context Protocol.

• Send notifications to your devices via the Pushover Message API
• Receive messages via the Pushover Open Client API
• Persist messages to a local SQLite database for history and search
• MCP server for AI assistant integration (Claude, etc.)
• XDG-compliant paths on all platforms (~/.config/push/, ~/.local/share/push/)

You'll need:

1. A Pushover account
2. An application token from pushover.net/apps (create a new application)
3. Your user key from pushover.net (shown on your dashboard)

# From source
git clone https://github.com/harper/push.git
cd push
go build -o push .

# Or with go install
go install github.com/harper/push@latest

push login

You'll be prompted for:

• App token - from your Pushover application
• User key - from your Pushover dashboard
• Email - your Pushover account email
• Password - your Pushover account password
• 2FA code - if two-factor authentication is enabled

This registers a device for receiving messages and stores credentials securely.

push send "Hello from the CLI!"
push send -t "Alert" -p 1 "Something important happened"

push messages

push history
push history --since yesterday
push history --search "important"

Authenticate with Pushover and register a device for receiving messages.

push login
push login --device-name "my-server"

Remove stored device credentials (keeps app token and user key).

push logout

Send a push notification.

push send "Simple message"
push send -t "Title" "Message with title"
push send -p 2 "Emergency priority message"
push send -u "https://example.com" "Message with link"
push send -d "iphone" "Send to specific device"
push send -s "cosmic" "Message with custom sound"

Priority levels:

• -2 - Lowest (no notification)
• -1 - Low (quiet)
• 0 - Normal (default)
• 1 - High (bypass quiet hours)
• 2 - Emergency (requires acknowledgment)

Fetch unread messages from Pushover. Messages are automatically persisted to the local database.

push messages
push messages -n 5

Query persisted message history from the local SQLite database.

push history
push history -n 50
push history --since "2025-01-01"
push history --since yesterday
push history --search "error"

Show current configuration.

push config           # Show config contents
push config --path    # Show config file path only

Start the MCP server for AI assistant integration.

push mcp

The server runs on stdio and implements the Model Context Protocol.

The push mcp command starts a Model Context Protocol server, allowing AI assistants like Claude to send and receive Pushover notifications.

Add to your Claude Code MCP settings (~/.claude/claude_desktop_config.json):

{
  "mcpServers": {
    "push": {
      "command": "/path/to/push",
      "args": ["mcp"]
    }
  }
}

Send a push notification through Pushover.

Parameters:

Poll the Pushover Open Client API, persist new messages, and return the newest ones.

Parameters:

Query persisted message history from the local SQLite database.

Parameters:

Delete unread messages from Pushover up to (and including) the provided ID.

Parameters:

Configuration is stored in TOML format at ~/.config/push/config.toml:

app_token = "your-app-token"
user_key = "your-user-key"
device_id = "device-identifier"
device_secret = "device-secret-from-login"
default_device = "push-cli"
default_priority = 0

Messages are persisted to a SQLite database at ~/.local/share/push/push.db.

The database contains two tables:

• messages - Received messages from Pushover
• sent - Log of sent notifications

• Config file is created with mode 0600 (owner read/write only)
• Credentials are stored locally, never transmitted except to Pushover's API
• Device secrets are obtained via Pushover's official Open Client API

Push uses two Pushover APIs:

• Message API - For sending notifications
• Open Client API - For receiving messages and device registration

MIT