Skip to content
GitHub MCP RegistryListed

Pushary: human-in-the-loop for AI agents

Part ofPusharylisted on 5 directories

Human-in-the-loop for AI agents: ask a person and get approvals or answers by push notification.

First seen 31 Oct 2026. Evidence as of 7 Nov 2026.

6
Tools
From an anonymous probe
1
Source listings
Each with its own history
12
Recorded changes
Since first seen

Tools

ToolDescriptionBehaviour
ask_userRequest an unresolved decision or missing input from the user through Pushary. Supports confirm, select and input questions. Delivery and waiting follow the account policy; a call waits at most 48 seconds and may return immediately. Returns the question state, answer when available, delivery information and handoff fields. answerUrl is optional. A pending question remains answerable after a poll ends. Sends a real question; it does not grant permission for other actions.Destructive
cancel_questionRetract a pending question that is no longer needed or is moving to the current client. Returns cancelled:true only when a pending question was removed. False may mean it was already answered, expired, missing or unavailable. An unavailable state includes handoffAction:stop because cancellation could not safely inspect or fence the question. Does not retract an answer already recorded.Destructive
propose_scopeRequest agreement on an unresolved or user-requested boundary for this session. Sends a real scope question and returns ratified, answered, contract and enforcement information. Only supported hooks can enforce file paths on path-bearing tool calls; promises are recorded but not enforced. Empty enforces means no automatic boundary checking. A contract never overrides host permissions or authorizes a separate action. The call waits at most 48 seconds; a pending proposal remains answerable after the call returns.Destructive
schedule_reminderSchedule, list, retrieve or cancel a personal Pushary reminder for the authenticated user. Scheduled reminders can arrive after the agent exits. One-time only; up to 30 days away, 25 pending per user/site. Scheduling requires body and either inMinutes or at with an explicit UTC offset. requestId identifies one schedule across retries. reminderId retrieves its outcome; no arguments lists pending reminders; cancelReminderId cancels a pending reminder. Returns the scheduled time, state and any delivery warning. Delivery respects stop/mute and active membership. Does not schedule agent work or customer campaigns. API reference: https://pushary.com/docs/agents/reference/tools#schedule_reminderDestructive
send_notificationSend a notification to connected devices for a requested update or a meaningful unattended result, such as a finished task. Delivery follows the account policy and optional recipient filters. context adds a detail page. context.askQuestion is kept for older clients; ask questions with ask_user. Returns web/mobile delivery counts and a warning when no delivery channel is connected. Sends real notifications. API reference: https://pushary.com/docs/agents/reference/tools#send_notificationDestructive
wait_for_answerRead the answer or current state of an existing Pushary question by its correlationId. Waits up to timeoutMs, capped at 48 seconds; a poll that ends with status pending is not an answer, so keep waiting. Returns answered, the answer when available, status and handoff information. Only pending is a live unanswered question; cancelled, expired, missing and unavailable are terminal states. Does not send another question.Read-only

Change history

  1. wait_for_answer: input schema changed
  2. wait_for_answer: description changed (+"48 seconds; a poll that ends with status pending is not an answer, so keep waiting." -"55 seconds.")
  3. propose_scope: input schema changed
  4. propose_scope: description changed (+"48" -"55")
  5. ask_user: input schema changed
  6. ask_user: description changed (+"48" -"55")
  7. wait_for_answer: input schema changed
  8. send_notification: input schema changed
  9. propose_scope: input schema changed
  10. cancel_question: input schema changed
  11. ask_user: input schema changed
  12. Listed (GitHub registry)
Source listings
SourceListingFirst seenLast seenVersions
GitHub MCP Registryio.github.Pushary/pushary31 Oct 20266 Nov 20261