pingwa
Server Details
Zero-setup WhatsApp notifications + human-in-the-loop for AI agents — text 'join', send in 60s.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- grzgrzgrz3/pingwa-client
- GitHub Stars
- 1
- Server Listing
- pingwa
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 8 tools
Each tool has a distinct role: notify is fire-and-forget, ask blocks for a reply, check_replies pulls inbound/late answers, and the schedule trio is clearly split into create/list/cancel. The only mild overlap is ask vs notify (both push WhatsApp messages, and notify's ack/escalate options bring it close to ask's interaction model), but the blocking-vs-nonblocking distinction in the descriptions resolves it.
All names are snake_case and mostly follow verb_noun (check_replies, check_status, list_schedules, cancel_schedule). The deviations are the bare verbs ask, notify, schedule and upgrade, where the create counterpart to list_schedules/cancel_schedule is just 'schedule' rather than create_schedule — minor but noticeable.
Eight tools is well-scoped: four cover outbound/inbound messaging, three cover scheduling lifecycle, two cover account state and billing. Nothing appears redundant and no obvious sub-operation is crammed into a mega-tool.
The core loop (send, ask, receive, schedule, account status) is fully covered with lifecycle support for schedules (register/list/cancel). Gaps are minor: no update/reschedule operation (cancel-and-recreate is the workaround), no tool to inspect or manage team members/policies that escalate refers to, and ask cannot attach an image while notify can.
Available Tools
8 toolsaskAInspect
Ask the human a question on WhatsApp and BLOCK until they reply (or timeout).
`text` is the question. `buttons` (optional, up to 3) render as tappable reply
buttons; omit them to invite a free-text answer the human types on their phone —
use this to let the human steer you mid-task. `timeout` is seconds to wait
(max 90). Returns the human's reply (free text and/or the chosen option). On
timeout, returns a note — the question was delivered and the answer is still
retrievable via `check_replies`. `to` (optional): "me" (default), "team" or a list
of team member names or ids; to a group, the first answer wins and names who.
`mode` (optional, a group): "first" (default) or "all" (every recipient's answer).
`escalate` (optional, mode "first"): while nobody answers, ask the next people: up
to 3 steps {"to": "team" or [member names/ids], "after_s": seconds after the send,
>= 60, each >= 60 after the previous}, or a policy name (POST /v1/team/policies).
The first answer stops it; it goes on after `timeout`.
Inputs: text (required), to, mode, buttons, +2 more. Returns: result
cancel_scheduleAInspect
Delete one scheduled message by name or id. It will not run again.
Inputs: name (required). Returns: result
check_repliesAInspect
Pull inbound WhatsApp messages the human sent to pingwa (out-of-band
instructions, or late answers to an ask). since is a cursor from a previous
call (pass it back to get only newer messages); wait long-polls up to that many
seconds for something to arrive. Returns the messages and a new cursor.
Inputs: wait, since. Returns: result
check_statusAInspect
Show the pingwa account's plan, remaining monthly quota, and whether the free 24h WhatsApp reply window is currently open.
Inputs: no named parameters. Returns: result
list_schedulesAInspect
List the account's scheduled messages: name, id, when, next run (local time), paused or done. Read-only.
Inputs: no named parameters. Returns: result
notifyAInspect
Send a WhatsApp notification to the account owner's own phone.
`text` is the message (1-1024 chars). `image_url` (optional) is a public https
image link — a screenshot, chart or diff — delivered as an image with `text` as
the caption when the user's 24h window is open (otherwise text only). Returns a
confirmation with the queued message id; raises an actionable error on quota/auth.
`to` (optional): "me" (default), "team" (the owner plus every active team member)
or a list of team member names or ids (and "me"); one message per recipient.
`ack` (optional): an "On it" button on each copy inside the 24h window; to a team
the first tap wins and the others are told who took it (read it via
`check_replies`).
`escalate` (optional, with `ack`): while nobody taps, send on to the next people:
up to 3 steps {"to": "team" or [member names/ids], "after_s": seconds after the
send, >= 60, each >= 60 after the previous}, or a policy name (POST
/v1/team/policies). The first tap stops it.
`actions` (optional): buttons under the alert, up to 3: an action id (one of the
number's actions), "ack" (the "On it" button, instead of `ack`), "snooze" (mutes
`topic` for 1h) or {"snooze": minutes}. A tap runs the action with `ref` as its
context. `topic` (optional): what the alert is about (letters, digits, . _ : / -),
needed by a snooze; while snoozed, sends with it are suppressed. `ref` (optional):
your own string (an incident id), sent back with an action's run.
Inputs: text (required), to, ack, ref, +4 more. Returns: result
scheduleAInspect
Register a WhatsApp message to the account owner's own phone at a later time:
once (at), every every_s seconds, or on a cron schedule (give exactly one).
You cannot send it later yourself; tell the human the registered local time this
returns. A scheduled message usually arrives outside the 24h window, so it is
sent as a template and counts toward the monthly quota. The human can list and
cancel from WhatsApp too: schedules, cancel <name>.
Inputs: text (required), at, cron, name, +3 more. Returns: result
upgradeAInspect
Get a link to upgrade the account to Pro (raises the monthly quota).
Returns a Stripe Checkout URL for the human to open and pay — no pingwa
password needed, the card is handled by Stripe. If the account is already
on a paid plan, returns a billing-portal URL to switch tier, change Team
seats or cancel instead. Also lists every way forward with its price,
cheapest first: a one-time message pack for a low-volume number, Team
seats, the next plan.
Inputs: no named parameters. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Give your AI agents a WhatsApp number and a voice: they message you and call you.
Human approvals, notifications, inbound webhooks, wake-ups for headless agents. Free trial: /try
Read-only WhatsApp MCP for your AI agent: it reads the chats you choose. Try the public demo.
Messaging infrastructure for AI agents across iMessage, WhatsApp, Telegram and SMS.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceHuman-in-the-loop approvals and notifications for AI agents via WhatsApp. Enables Cursor, Claude Code, and autonomous AI agents to reach users away from their computers.112 npmISC
- AlicenseAqualityCmaintenanceEnables AI agents to request human decisions and send notifications through chat platforms like Slack and WhatsApp, with ephemeral in-memory pending requests and no central backend.2MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to send WhatsApp notifications to their owner and read the owner's replies through a local gateway, without requiring the Meta Business API.MIT
- AlicenseAqualityCmaintenanceEnables AI agents to send WhatsApp notifications to verified team members, ask for human approval before risky actions, and wait for or check decisions. It also supports Claude Code permission prompts on WhatsApp, with safe handling of retries, expirations, and concurrent answers.31,064 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.