Jon's Pushover MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PUSHOVER_USER_KEY | Yes | User key from https://pushover.net | |
| PUSHOVER_API_TOKEN | Yes | Application API token from https://pushover.net/apps |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_notificationA | Send a push notification via Pushover. Args: message: The notification message body (required). title: Title shown at top of notification. Defaults to app name. url: URL to include (tappable in notification). url_title: Label for the URL instead of showing raw URL. priority: Priority level from -2 (silent) to 2 (emergency). Default 0. sound: Notification sound name. See Pushover docs for available sounds. Returns: Dictionary with 'status' (1 for success) and 'request' (UUID string). Raises: ValueError: If priority is out of range or sound is invalid. PushoverError: If Pushover API returns an error or credentials are missing. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool 'send_notification' has a clear, singular purpose that is distinct by default.
The single tool name 'send_notification' follows a clear verb_noun pattern, and with only one tool, consistency is inherently perfect as there are no other names to compare against.
A single tool is too few for most server purposes, as it limits functionality and suggests a thin or incomplete surface. For a notification service, basic operations like listing or managing notifications might be expected, but only sending is provided.
The server's domain appears to be Pushover notifications, but it only offers a send operation. There are significant gaps, such as no ability to retrieve, update, delete, or list notifications, which could cause agent failures in broader workflows.