Pushover MCP integration for AI agents.
Connect AI agents to Pushover through 29 structured actions, including check license credits, add group user, ack delete messages up to id, and client login.…
- ACTION CONTRACTS
- 29
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Pushover integration exposes
The Pushover Agent App exposes 29 provider-backed actions for communication work. Its current contract lets an authorized agent check available pushover team license credits, add one user to a pushover delivery group, and acknowledge and delete pushover open client messages up to an id. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Pushover account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Pushover capabilities.
Showing 12 of 29 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
check_license_creditsREADCheck available Pushover Team license credits.
add_group_userWRITEAdd one user to a Pushover delivery group.
ack_delete_messages_up_to_idHIGH IMPACTAcknowledge and delete Pushover Open Client messages up to an ID.
client_loginREVIEWLog in to the Pushover Open Client API.
add_team_userWRITEAdd a user to a Pushover Team.
assign_licenseWRITEAssign a Pushover license through the Team API.
cancel_receipt_retriesHIGH IMPACTCancel retries for one emergency notification receipt.
cancel_retries_by_tagHIGH IMPACTCancel emergency notification retries by tag.
create_groupWRITECreate a Pushover delivery group.
disable_group_userHIGH IMPACTDisable one user in a Pushover delivery group.
enable_group_userREVIEWEnable one user in a Pushover delivery group.
fetch_client_messagesREVIEWFetch messages from the Pushover Open Client message queue.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Check License Credits
Check available Pushover Team license credits. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
check_license_creditsControl Add Group User
Add one user to a Pushover delivery group. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
add_group_userVerify with Add Group User
Add one user to a Pushover delivery group. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
add_group_userSAFETY BOUNDARY
Operate Pushover with explicit limits
- Authorize Pushover with API key and grant only the provider access required by the selected actions.
- 13 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `ack_delete_messages_up_to_id`, `cancel_receipt_retries`, and `cancel_retries_by_tag` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Pushover rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Pushover task completed successfully.
CONNECTION MODEL
API key
Pushover application API token sent as the token parameter for application, message, group, and glance requests.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 8
- WRITE SIGNALS
- 7
- HIGH IMPACT
- 6
- REVIEW SIGNALS
- 8
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Pushover.