← Plugin catalog
Productivity

PingRoom

Mindzone Technologies LLC v1.0.0

Ask people via push

Create a free account to save this plugin.

From the developer

Not specified in the available declarations: capabilities, limitations, pricing & account requirements.

Onboarding example

Hand off the launch-checklist task to my phone, wait for my acknowledgment, then continue.
Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 17, 2026. Package observed Nov 17, 2026.

View package source →

Description

From the marketplace listing

AI agents silently stall when they need a human, leaving approvals, questions, and handoffs buried in chat. PingRoom pushes the request to the right person’s phone and sends the response back so work can continue.

Language: English · Automatically detected from descriptions.

Matches for “ping”

Exact text from the indicated source. A mention alone does not establish support for your task.

Plugin name

PingRoom

Publisher description

AI agents silently stall when they need a human, leaving approvals, questions, and handoffs buried in chat. PingRoom pushes the request to the right person’s phone and sends the response back so work can continue.

What changed

Files & skills

File archives

Plugin package4 files · 10.6 KBBrowse files →
Skill instructions
pingroom-mcp11.2 KB

View saved version →

---
name: pingroom-mcp
description: >-
  Reach a human through PingRoom — the event platform whose MCP connector this
  session has. Use this skill whenever the task involves notifying, alerting, or
  pinging a person; sending them a file, report, markdown, zip, image, or
  location; sharing a tappable link to their phone; asking a human a question
  and blocking on the answer; requesting an approve/deny decision before acting;
  handing a decision off to your authorizing human; or showing live progress on
  their lock screen while long work runs. Trigger it even when the user doesn't
  say "PingRoom" — phrases like "let me know when it's done", "send this to my
  phone", "ask me before deploying", "ping the team", "notify me", "send me the
  report", or "show progress on my lock screen" all mean this skill. Also use it
  when writing scripts or CI that must alert a person, and for managing PingRoom
  rooms, webhooks, or quick actions via the CLI.
---

# PingRoom: reach a human, get a real answer

PingRoom turns "the agent finished / needs input" into an event on a person's
phone: a push they feel, a card on their lock screen, a question they answer
with one tap. You reach it over MCP (`mcp__pingroom__*` tools); a paired
`pingroom` CLI may also be available for what MCP doesn't carry.

Read `references/tools.md` for the full 27-tool schema reference when you need
exact parameters. This file teaches you which tool to reach for and the rules
that make the difference between "sent" and "landed".

## The one rule that matters

**A successful send proves PingRoom accepted delivery work — not that a person
received, saw, or acted.** Never report "I notified them" as "they know".
When the task needs a human to actually respond, use a primitive that closes
the loop, then block on its wait tool:

| You need | Send with | Block with | Resolved states |
|---|---|---|---|
| Someone to see + confirm | `broadcast` with `requires_ack: true` | `wait_for_ack` | acked / expired |
| A choice among 2–4 options | `ask_question` | `wait_for_answer` | answered / expired / cancelled |
| Permission before acting | `request_approval` | `wait_for_approval` | approved / denied / expired |
| Your authorizing human, privately | `create_handoff` | `wait_for_handoff` | acked or answered / expired |

Pending, timeout, enqueued, and delivery states are **not** answers. If a wait
expires, say so plainly and do not proceed as if consent was given.

## Picking a room

Call `list_rooms` first (cache the result for the conversation). Rules:

- Personal rooms (`type: "personal"`) refuse `broadcast` — use
  `trigger_quick_action` there.
- Public rooms allow 160-char messages; private rooms 120. Titles cap at 40.
- Sends into single-member rooms are refused (`validation_failed`) — a ping
  needs a recipient other than the sender.
- If the user names a room ambiguously, match on name case-insensitively; when
  several match, ask which one rather than guessing.

## Recipes

### Plain ping
`broadcast { invite_code, message, title?, action_icon? }`. Keep the message an
event, not prose: *what happened, what to do, is it done*. Set a `title` only
when the room name alone wouldn't orient the reader.

### Urgent / must-be-confirmed
- `is_urgent: true` breaks through Focus/Do Not Disturb. Delivery-only — it
  asks nothing of the recipient. Reserve it for genuinely time-sensitive events
  or it trains people to ignore it.
- `requires_ack: true` keeps the ping open with a lock-screen Acknowledge
  button until one eligible recipient confirms. Add `ack_timeout_seconds`
  (60–86400) when the confirmation is only useful for a while, then
  `wait_for_ack { notification_id }`.
- The two compose: urgent+ack is "wake them and hold the door".

### Location ping
Put a location in `data.location` — the app renders a tappable map:

```json
{ "invite_code": "…", "message": "Meet here at 6",
  "data": { "location": { "latitude": 48.8584, "longitude": 2.2945,
            "label": "Eiffel Tow

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package author
Mindzone Technologies LLC

Package observed Nov 17, 2026.

Technical details
First seen
Sep 30, 2026 · 22:02 UTC
Last seen
Nov 17, 2026 · 18:00 UTC
Collection status
Collected

plugin_asdk_app_6a916657d9ec8191a3fa18146408479c

Download plugin data (JSON)

Plugin details: served from cache. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.