Pushary: human-in-the-loop for AI agents
io.github.Pushary/pusharyVersion 1.5.2Human-in-the-loop for AI agents: ask a person and get approvals or answers by push notification.
Status
Responds106 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:41 UTC
- Latency
- 106 ms
- Remotes responding
- 1 of 2
- Sign-in
- API key
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 21:12 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://pushary.com/api/mcp/mcpResponds106 msNo sign-in
Claude Code
claude mcp add --transport http pushary https://pushary.com/api/mcp/mcp --header 'Authorization: Bearer <YOUR_TOKEN>'Replace <YOUR_TOKEN> before running.
Claude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: pushary
Remote MCP server URL: https://pushary.com/api/mcp/mcp
This server expects the header Authorization.Cursor
{
"mcpServers": {
"pushary": {
"url": "https://pushary.com/api/mcp/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}Replace <YOUR_TOKEN> before running.
VS Code
code --add-mcp '{"name":"pushary","type":"http","url":"https://pushary.com/api/mcp/mcp","headers":{"Authorization":"Bearer <YOUR_TOKEN>"}}'Replace <YOUR_TOKEN> before running.
SSE
https://pushary.com/api/mcp/sseNot checkedUses SSEUses SSE (legacy), not checked
Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
6 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
ask_userRequest an unresolved decision or missing input from the user through Pushary, which reaches their phone, Mac or Slack. Use it when the user asks you to call, phone or ring them if you get stuck or blocked: ask the question here. Supports confirm, select and input questions. Delivery follows the account policy. When the reply includes phoneCall, Pushary may phone the person who can answer if the question is still unanswered, and records what they say as the answer; without phoneCall no call is planned. One ask_user request waits at most 48 seconds and may return at once. While the reply is pending and has no handoffAction, keep waiting with wait_for_answer and the same correlationId: a poll ending is no reason to give up, cancel or ask again. Returns the question state, answer when available, delivery information and handoff fields. answerUrl is optional. Sends a real question; it does not grant permission for other actions. | Yes | No | No | Yes |
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. | Yes | No | Yes | No |
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. | Yes | No | No | Yes |
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_reminder | Yes | No | No | Yes |
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_notification | Yes | No | No | Yes |
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. | No | Yes | Yes | No |
Details
- Registry status
- Active
- Published
- Oct 25, 2026
- Updated
- Oct 25, 2026
- Website
- https://pushary.com/?utm_source=mcp-registry&utm_medium=integration-directory (opens in a new tab)
- Categories (suggested)
- CommunicationSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared