Can I use Pushover as a CLI?

Yes. KosmoKrator exposes a Pushover CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Pushover through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Pushover tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Pushover credentials stored?

Pushover credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Pushover MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

notifications

Pushover CLI for AI Agents

Use the Pushover CLI from KosmoKrator to call Pushover tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.

3 functions 2 read 1 write API key auth

Submit Pushover feedback View package source

Pushover CLI Setup

Pushover can be configured headlessly with `kosmokrator integrations:configure pushover`.

# Install KosmoKrator first if it is not available on PATH.
curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash

# Configure and verify this integration.
kosmokrator integrations:configure pushover --set api_key="$PUSHOVER_API_KEY" --set user_key="$PUSHOVER_USER_KEY" --enable --read allow --write ask --json
kosmokrator integrations:doctor pushover --json
kosmokrator integrations:status --json

Credentials

Authentication type: API key api_key. Configure credentials once, then use the same stored profile from scripts, coding CLIs, Lua code mode, and the MCP gateway.

Key	Env var	Type	Required	Label
`api_key`	`PUSHOVER_API_KEY`	Secret `secret`	yes	Application API Key
`user_key`	`PUSHOVER_USER_KEY`	Secret `secret`	yes	User Key

Call Pushover Headlessly

Use the generic call form when another coding CLI or script needs a stable universal interface.

kosmo integrations:call pushover.pushover_send_message '{
  "message": "example_message",
  "title": "example_title",
  "priority": 1,
  "url": "example_url",
  "url_title": "example_url_title",
  "sound": "example_sound",
  "device": "example_device",
  "timestamp": 1
}' --json

Use the provider shortcut form for shorter human-facing commands.

kosmo integrations:pushover pushover_send_message '{
  "message": "example_message",
  "title": "example_title",
  "priority": 1,
  "url": "example_url",
  "url_title": "example_url_title",
  "sound": "example_sound",
  "device": "example_device",
  "timestamp": 1
}' --json

Agent Discovery Commands

These commands return structured output for coding agents that need to inspect capabilities before choosing a function.

kosmo integrations:docs pushover --json
kosmo integrations:docs pushover.pushover_send_message --json
kosmo integrations:schema pushover.pushover_send_message --json
kosmo integrations:search "Pushover" --json
kosmo integrations:list --json

All CLI Functions

Every function below can be called headlessly. The generic form is stable across all integrations; the provider shortcut is shorter but specific to Pushover.

`pushover.pushover_send_message`

Write write

Send a push notification via Pushover. Supports message, title, priority levels, and optional URL/sound attachments.

Parameters: message, title, priority, url, url_title, sound, device, timestamp, expire, retry

Generic CLI call

kosmo integrations:call pushover.pushover_send_message '{"message":"example_message","title":"example_title","priority":1,"url":"example_url","url_title":"example_url_title","sound":"example_sound","device":"example_device","timestamp":1}' --json

Provider shortcut

kosmo integrations:pushover pushover_send_message '{"message":"example_message","title":"example_title","priority":1,"url":"example_url","url_title":"example_url_title","sound":"example_sound","device":"example_device","timestamp":1}' --json

`pushover.pushover_list_sounds`

Read read

List available notification sounds in Pushover. Use sound names with the send_message tool.

Parameters: none

Generic CLI call

kosmo integrations:call pushover.pushover_list_sounds '{}' --json

Provider shortcut

kosmo integrations:pushover pushover_list_sounds '{}' --json

`pushover.pushover_get_current_user`

Read read

Validate the Pushover user credentials and retrieve account information.

Parameters: none

Generic CLI call

kosmo integrations:call pushover.pushover_get_current_user '{}' --json

Provider shortcut

kosmo integrations:pushover pushover_get_current_user '{}' --json

Function Schemas

Use these parameter tables when building CLI payloads without calling integrations:schema first.

`pushover.pushover_send_message`

Send a push notification via Pushover. Supports message, title, priority levels, and optional URL/sound attachments.

Operation: Write write
Schema command: kosmo integrations:schema pushover.pushover_send_message --json

Parameter	Type	Required	Description
`message`	string	yes	The notification message body.
`title`	string	no	Optional title for the notification.
`priority`	integer	no	Message priority: -2 = no notification/alert, -1 = quiet notification, 0 = normal (default), 1 = high priority (bypasses quiet hours), 2 = emergency (requires acknowledgment).
`url`	string	no	A supplementary URL to include with the notification.
`url_title`	string	no	Title for the supplementary URL.
`sound`	string	no	Notification sound name (e.g., "pushover", "bike", "echo"). Use the list_sounds tool to see available options.
`device`	string	no	Specific device name to send to. Omit to send to all devices.
`timestamp`	integer	no	Unix timestamp to schedule the message delivery.
`expire`	integer	no	Seconds until emergency-priority (2) messages expire (max 10800).
`retry`	integer	no	Seconds between retries for emergency-priority (2) messages (min 30).

`pushover.pushover_list_sounds`

List available notification sounds in Pushover. Use sound names with the send_message tool.

Operation: Read read
Schema command: kosmo integrations:schema pushover.pushover_list_sounds --json

Parameter	Type	Required	Description
No parameters.

`pushover.pushover_get_current_user`

Validate the Pushover user credentials and retrieve account information.

Operation: Read read
Schema command: kosmo integrations:schema pushover.pushover_get_current_user --json

Parameter	Type	Required	Description
No parameters.

Permissions

Headless calls still follow the integration read/write permission policy. Configure read/write defaults with integrations:configure. Add --force only for trusted automation that should bypass that policy.