Pushover for AI agents

Pushover delivers real-time notifications to a person's devices through a simple API integration. Developers and sysadmins use it to get alerted about scripts, servers, and monitoring events. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

Connect Pushover See the 29 actions ↓

CommunicationAPI keyMCP + RESTpushover.net

AUDIT LOG · PUSHOVERPOLICY: acme-support

09:41:07 · claude · u_8f2read

pushover.get_app_token

Get Application Token✓ allowed · 212ms

09:41:08 · claude · u_8f2read

pushover.get_app_limits

Get App Limits✓ allowed · 164ms

09:41:09 · claude · u_8f2write

pushover.send_message

Send Message✓ approved · approved by user

09:41:12 · claude · u_8f2destructive

pushover.cancel_retries_by_tag

Cancel Retries by Tag✕ blocked · policy: deny

EVERY PUSHOVER CALL, ON THE RECORD

01 · USE CASES

What agents do in Pushover.

Send a message notification

Send an alert message to a user's devices when a monitored event happens.

Check receipt status read-only

Look up whether an emergency-priority message has been acknowledged yet.

Cancel retries with approval

Stop retrying a message's delivery only after confirming the issue is resolved.

02 · ACTIONS

29 Pushover actions, graded by risk.

Every Pushover action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

Look things up. Allowed by default.

pushover.get_app_token
Get Application Token
pushover.get_app_limits
Get App Limits
pushover.get_app_icon_image
Get Application Icon Image
pushover.get_receipt_status
Get Receipt Status
pushover.get_team_api_token
Get Team API Token
pushover.validate_user_or_group
Validate User or Group

write

Create and change things. Allow, or ask the user first.

pushover.send_message
Send Message
pushover.group_get
Get Group Details
pushover.group_list
List Delivery Groups
pushover.client_login
Pushover Client Login
pushover.group_create
Create Group
pushover.group_rename
Rename Delivery Group
pushover.glances_update
Glances Update
pushover.group_add_user
Add User to Group
pushover.license_assign
Assign License
pushover.teams_add_user
Add Team User
pushover.group_enable_user
Group Enable User
pushover.subscription_flow
Subscription Flow
pushover.store_team_api_token
Store Team API Token
pushover.client_fetch_messages
Fetch Pending Messages
pushover.license_check_credits
Check License Credits
pushover.client_register_device
Register Open Client Device

+ 1 MORE

destructive

Delete, cancel or archive. Ask first, or deny outright.

pushover.cancel_retries_by_tag
Cancel Retries by Tag
pushover.cancel_receipt_retries
Cancel Receipt Retries
pushover.group_remove_user
Remove User from Group
pushover.teams_remove_user
Remove User from Team
pushover.group_disable_user
Disable Group User
pushover.client_ack_delete_up_to_id
Client Acknowledge Delete Up To ID

03 · HOW IT WORKS

Pushover in three steps.

01Your users connect PushoverThey add their Pushover api key on Arc0 Connect, under your brand. It goes straight into the vault.
02You set the rulesReads run, writes like “send Message” can wait for the user, and “cancel Retries by Tag” can be denied outright.
03Any agent can actYour agent calls Pushover through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.

POLICY.TS

await arc0.policies.set('pushover', {
  read: 'allow',
  write: 'ask',        // send_message
  destructive: 'deny',  // cancel_retries_by_tag
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2

04 · AUTH AND DATA

How Pushover connects.

Users add their Pushover api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

The same Pushover connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH: API key
CREDENTIALS: Per-tenant encrypted vault
MODEL SEES: Results only, never credentials
AUDIT LOG: Every call, on every plan

05 · WORKS WITH

Use Pushover from any agent.

Claude

ChatGPT

Cursor

Codex

VS Code

OpenAI Agents SDK

Claude Agent SDK

Vercel AI SDK

Mastra

LangGraph

06 · RELATED

More communication apps.

Slack168 actions

Microsoft Teams174 actions

Android Texter11 actions

Dialpad192 actions

ALL COMMUNICATION APPS →

07 · FAQ

Pushover and Arc0, answered.

Q01

Can I use Pushover with Claude, ChatGPT or Cursor?

Yes. Connect Pushover to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Pushover actions you allow.

Q02

How do users connect Pushover?

Users add their Pushover api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

Q03

Which Pushover actions can my agent take?

29 in total: 6 read, 17 write and 6 destructive, such as “send Message”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in Pushover?

Yes. Actions like “cancel Retries by Tag” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.

Q05

Can my own backend call Pushover too?

Yes. The same Pushover connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug Pushover into your agent.

Your users connect Pushover once, under your brand. Your agent gets 29 actions behind your policies, with every call on the record.

Connect Pushover Browse all apps →

Free to build · MCP + REST · Audit log on every plan