Pushary
Server Details
An MCP connector that lets your AI agents ask you questions, request permission approvals, and send alerts as push notifications to your phone and mac notch, so you can unblock and approve your agents from anywhere.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- Pushary
TDQS
Scored across 6 tools
The core flows are separable: ask_user sends a question, wait_for_answer only polls by correlationId, cancel_question only retracts, send_notification pushes results, schedule_reminder handles reminders. The main soft spots are ask_user vs propose_scope (both send a blocking 48s question, one specialized for scope contracts) and send_notification's legacy context.askQuestion field, which description explicitly redirects to ask_user. Clear enough that an agent can choose, but the question-sending pair requires reading descriptions carefully.
All six tools use a consistent snake_case verb_noun pattern (ask_user, cancel_question, propose_scope, schedule_reminder, send_notification, wait_for_answer). Verbs are distinct and meaningful, no camelCase mixing or vague names.
Six tools is well-scoped for a question/handoff/notification service: ask, wait, cancel, propose scope, notify, remind. Nothing feels padded or thin; each tool maps to a distinct user-facing capability.
The question lifecycle is fully covered (ask -> wait -> answer/cancel) and reminders cover create/list/get/cancel via parameters, plus outbound notifications. Minor gaps: no way to list or inspect outstanding questions other than polling a known correlationId, and no listing/history or cancellation for sent notifications. These are workaroundable, not blocking.
Publisher details
- Operator
- https://ralphnex.com
- Operator website
- https://pushary.com
- Vendor relationship
- Unknown
- Documentation
- https://pushary.com/docs
- Privacy policy
- Not provided
- Trust center
- Unknown
- Restrictions
- Unknown
Available Tools
6 toolsask_userAsk User a Question; May Call or Ring Their Phone If UnansweredADestructiveInspect
Ask for an unresolved decision or missing input. Prefer this over an in-app question when the user requests Pushary or mobile contact, is away, or work is unattended. Use it when the user asks you to call, phone or ring them if you get stuck or blocked. Supports confirm, select and input. Delivery follows account policy. When the reply includes phoneCall, Pushary may phone the person who can answer if the question is still unanswered, and records their answer; without phoneCall no call is planned. 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 does not cancel the question. Returns state, answer, delivery and handoff fields; answerUrl is optional. Sends a real question; it does not authorize other actions.
Inputs: question (required), cwd, env, tags, +36 more. Returns: env, held, hint, mode, +27 more
cancel_questionCancel Pending QuestionADestructiveIdempotentInspect
Retract 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, and so does a question from a session the user stopped: stop, and do not act on it. Does not retract an answer already recorded.
Inputs: correlationId (required), handoff. Returns: hint, status, cancelled, askHandoff, +3 more
propose_scopePropose Run ScopeADestructiveInspect
Request 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.
Inputs: doneWhen (required), sessionId (required), promises, agentName, +4 more. Returns: note, value, status, answered, +8 more
schedule_reminderSchedule a Personal Reminder to Remind Them LaterADestructiveInspect
Schedule, 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
Inputs: at, env, body, title, +7 more. Returns: hint, pending, warning, delivery, +3 more
send_notificationSend Push NotificationADestructiveInspect
Send 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
Inputs: body (required), title (required), env, url, +9 more. Returns: env, hint, sent, status, +8 more
wait_for_answerWait for User AnswerARead-onlyIdempotentInspect
Read 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.
Inputs: correlationId (required), timeoutMs. Returns: hint, note, value, status, +5 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Push notifications for AI agents - send instant iPhone notifications from any MCP client.
Connect any AI agent to 1,000+ apps and 27,000+ actions through one remote MCP server (OAuth).
MCP connector that lets ChatGPT list, search, and run your Apple Shortcuts via a local Mac agent
Let your AI agents ask you for decisions and get your answers back, from your phone or the web.
Related MCP Servers
- AlicenseAqualityBmaintenanceAn MCP server that enables AI agents to pause and request human approval or information via Slack, Telegram, or macOS dialogs before proceeding with actions.29 PyPI15Apache 2.0
- AlicenseCqualityBmaintenanceMCP server for AI agents to send notifications, copy to clipboard, request confirmations, and collect text input from users across their devices.1035 npmApache 2.0
- AlicenseBqualityDmaintenancePushinator MCP lets you send push notifications to your devices from your LLM-powered workflows.1MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables any MCP-compatible AI agent to ask humans questions in real time via a mobile-friendly PWA with push notifications, operating local-first without third-party services.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.