Skip to content

Pushover

Updated View as Markdown

Validate a selected Pushover recipient. Send one bounded Pushover notification.

Example workflows

Copy a prompt into your connected AI client after connecting this integration. Choose resources you can access and review the supported command before running it.

Validate a selected Pushover recipient

Help me with this task in Pushover: Validate a selected Pushover recipient. Ask me to choose the destination and provide the content and any required resource IDs. Show the exact proposed change for my review, then perform it only after I approve. Return the created or updated resource ID and link when supplied. If the result is uncertain, inspect it before attempting the same change again.

Explore this command: pushover.recipient.validate

Send one bounded Pushover notification

Help me with this task in Pushover: Send one bounded Pushover notification. Ask me to choose the destination and provide the content and any required resource IDs. Show the exact proposed change for my review, then perform it only after I approve. Return the created or updated resource ID and link when supplied. If the result is uncertain, inspect it before attempting the same change again.

Explore this command: pushover.messages.send

What you can do (2)

What you can do

Available commands: 2 (0 read, 2 write). Enable only the commands your application needs.

Command Effect
Validate a selected Pushover recipient — pushover.recipient.validate Write
Send one bounded Pushover notification — pushover.messages.send Write

Connect and use

Connect and use

This connection uses your provider account.

Connect this integration, enter your provider credentials, choose commands and save. Complete provider authorization if prompted.

Get your provider credentials

Follow these steps for Pushover, then enter the issued values in the connection form below.

  1. Create a Pushover application at pushover.net/apps/build to obtain an application API token. Copy your recipient User Key from the Pushover dashboard, or an authorized delivery-group key, and store the two values in separate fields here. Validate the recipient first, then send one notification. Notifications consume the application quota and require an eligible recipient account/device. Emergency/repeating priority 2 is excluded; this integration never polls or retries delivery.

Official credential setup

Where to enter credentials

In the integration page, sign in, choose your workspace and open Connect. If a Credentials choice is shown, select Use my credentials. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.

Connection field Requirement
Application API token Required
Recipient user/group key Required

Open API keys and create a Tooluse.net key for the enabled commands.

Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.

Configure Claude Code, Codex or Cursor once

Permissions and results

If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net's existing permissions. Disabling a connection or revoking a key immediately prevents new calls.

Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.

Your connection's daily allowance and key permissions also apply. Adding a connection does not make a provider request.

Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.

Call from your client

Use the shared MCP configuration. Refresh your client's tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.

Configure Claude Code, Codex or Cursor once

Discover your enabled tools

List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.

curl 'https://api.tooluse.net/v1/tools' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY"

Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.

HTTP call

curl 'https://api.tooluse.net/v1/tool-calls' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: replace-with-a-new-call-id' \
  --data '{
  "type": "tool_use",
  "id": "toolu_example",
  "name": "svc_FROM_YOUR_TOOL_LIST",
  "input": {
    "body": {}
  }
}'

Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.

Commands

Validate a selected Pushover recipient — pushover.recipient.validate

Validate a selected Pushover recipient

This operation can change provider data. Review the input before allowing an agent to call it.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter Type Required in parent Description Constraints
body object Required additionalProperties: false

Full JSON Schema

Full JSON Schema

Example input

{
  "body": {}
}

At most 1 provider requests per invocation; timeout: 30 seconds.

Send one bounded Pushover notification — pushover.messages.send

Send one bounded Pushover notification

This operation can change provider data. Review the input before allowing an agent to call it.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter Type Required in parent Description Constraints
body object Required additionalProperties: false
body.message string Required minLength: 1; maxLength: 1024
body.title string Optional maxLength: 250
body.priority integer Optional minimum: -2; maximum: 1
body.url string Optional format: "uri"
body.url_title string Optional maxLength: 100

Full JSON Schema

Full JSON Schema

Example input

{
  "body": {
    "message": "Example notification",
    "title": "tooluse.net",
    "priority": 0
  }
}

At most 1 provider requests per invocation; timeout: 30 seconds.

Errors

Check the key's expiry, revocation, workspace and allowed operations.

Reuse the same idempotency key only for the same request.

The connection or provider limit has been reached. Check the receipt before retrying.

Test the connection

Open the integration's commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client's tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.

Official provider documentation

Type to search…

↑↓ navigate↵ selectEsc close