Skip to main content
Glama
pyang2045

MCP-Pushover Bridge

by pyang2045

MCP-Pushover Bridge

A Model Context Protocol (MCP) server that enables AI assistants to send push notifications via Pushover. Perfect for getting instant mobile alerts when Claude completes tasks, encounters errors, or when you want to send yourself messages through your AI assistant.

Features

  • ๐Ÿ“ฑ Send push notifications through Pushover API

  • ๐Ÿ”„ Configurable retry logic with exponential backoff

  • ๐ŸŽ›๏ธ Support for all Pushover message parameters (title, priority, sound)

  • โš™๏ธ Environment-based configuration

  • ๐Ÿ”ท Full TypeScript support

  • ๐Ÿค– Built for Claude Desktop and MCP-compatible clients

Related MCP server: Jon's Pushover MCP Server

Installation

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

Pushover Setup

Before using this MCP server, you need to set up Pushover:

1. Create Pushover Account

  1. Sign up at pushover.net

  2. Note your User Key from the dashboard

2. Download Pushover App

  1. Install the Pushover app on your mobile device:

  2. Log in with your Pushover account credentials

3. Create Application

  1. Go to pushover.net/apps/build

  2. Create a new application (e.g., "MCP Bridge")

  3. Note your API Token/Key

4. Test Your Setup

You can test your credentials using curl:

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

Configuration

Environment Variables

Create a .env file or set these environment variables:

# 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

Claude Desktop Integration

Add to your Claude Desktop configuration file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%/Claude/claude_desktop_config.json

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

After updating the configuration, restart Claude Desktop to load the MCP server.

Available Tools

pushover_send_message

Send a notification via Pushover to your mobile device.

Parameters:

  • message (required): The message content to send

  • user_key (optional): Pushover user or group key (defaults to env var)

  • api_token (optional): Pushover application API token (defaults to env var)

  • title (optional): Message title

  • priority (optional): Message priority:

    • -2: No notification/alert

    • -1: Quiet notification

    • 0: Normal priority (default)

    • 1: High priority

    • 2: Emergency priority (requires acknowledgment)

  • sound (optional): Notification sound (pushover, bike, bugle, cashregister, classical, cosmic, falling, gamelan, incoming, intermission, magic, mechanical, pianobar, siren, spacealarm, tugboat, alien, climb, persistent, echo, updown, vibrate, none)

Example:

{
  "message": "Task completed successfully!",
  "title": "Claude Notification",
  "priority": 1,
  "sound": "magic"
}

Use Cases

Personal Messaging

Ask Claude to send yourself reminders or messages:

  • "Send me a notification to call mom at 5 PM"

  • "Remind me to check the server logs"

  • "Send a message saying the backup is complete"

Task Completion Alerts

Get notified when Claude finishes work:

  • "Let me know when you're done analyzing this data"

  • "Send me a notification when the report is ready"

  • "Alert me if you find any errors in the code"

Workflow Integration

Integrate with your daily routines:

  • Morning briefings and daily summaries

  • Build completion and deployment notifications

  • Error monitoring and system alerts

  • Meeting reminders and calendar notifications

Emergency Notifications

High-priority alerts that require immediate attention:

  • System failures or critical errors

  • Security alerts or unusual activity

  • Time-sensitive reminders

  • Urgent task completions

Simply ask Claude: "Send me a push notification that says 'Deploy completed successfully'" and you'll receive it instantly on your mobile device!

Security

  • API tokens are never logged

  • Supports environment variables for credential management

  • All Pushover API calls use HTTPS

License

MIT

Available Tools

1 tool
pushover_send_messageC

Send a notification via Pushover

ParametersJSON Schema
NameRequiredDescriptionDefault
messageYesThe message content to send
user_keyNoPushover user or group key (defaults to env var)
api_tokenNoPushover application API token (defaults to env var)
titleNoOptional message title
priorityNoMessage priority (-2 to 2)
soundNoNotification sound

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('send a notification') but doesn't cover critical aspects like authentication requirements (though implied by parameters), rate limits, error handling, or what happens when the notification is sent. This leaves significant gaps for a tool that performs an external action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's purpose with zero wasted words. It's appropriately sized and front-loaded, making it easy to understand immediately.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (external notification service with 6 parameters) and lack of annotations and output schema, the description is insufficient. It doesn't explain what happens after sending (success/failure indicators), authentication defaults, or behavioral constraints, leaving the agent with incomplete context for proper use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all 6 parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema, meeting the baseline for high coverage but not providing extra value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('send') and resource ('notification via Pushover'), making the purpose immediately understandable. However, with no sibling tools mentioned, it cannot demonstrate differentiation from alternatives, which prevents a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, prerequisites, or contextual constraints. It simply states what the tool does without any usage context or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev1.0.0
    • First observedpushover_send_message

TDQS

B3.1/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to confuse it with. The single tool's purpose is clearly defined and distinct by default.

Naming Consistency5/5

The single tool name 'pushover_send_message' follows a consistent verb_noun pattern, and with only one tool, there is no inconsistency to evaluate. The naming is clear and predictable.

Tool Count2/5

A single tool is too few for a server named 'MCP-Pushover Bridge', which implies a bridge to the Pushover service. While sending messages is a core function, typical notification services might include additional operations like checking message status or managing user settings, making this feel thin and under-scoped.

Completeness2/5

The tool surface is severely incomplete for a Pushover bridge. It only covers sending messages, missing obvious operations such as checking message delivery status, retrieving user information, or handling priority settings, which are common in notification APIs and could lead to agent failures in broader workflows.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • A
    license
    B
    quality
    D
    maintenance
    Enables AI assistants to send push notifications through the kweenkl service. Allows users to receive contextual notifications from their AI when tasks are complete or important events occur.
    1
    17
    MIT
  • A
    license
    A
    quality
    C
    maintenance
    Enables AI assistants to send push notifications and interactive alerts to iPhone and Mac devices via the BotBell app. It allows AI to receive user replies and manage notification bots for tasks like alerts, reminders, and remote approvals.
    2
    19
    1
    MIT
  • A
    license
    B
    quality
    A
    maintenance
    Enables AI assistants to send push notifications to WeChat, email, and other channels via PushPlus, supporting multiple message formats and channels.
    85
    193
    4
    MIT

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pyang2045/mcp-pushover'

If you have feedback or need assistance with the MCP directory API, please join our Discord server