io.github.grzgrzgrz3Published by GitHub account grzgrzgrz3v0.4.1Updated Oct 24, 2026
Zero-setup WhatsApp notifications + human-in-the-loop for AI agents — text 'join', send in 60s.
Sends WhatsApp notifications to your own phone and lets an agent ask you questions there, blocking until you reply.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.grzgrzgrz3%2Fpingwa/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"pingwa": {
"type": "http",
"url": "https://pingwa.dev/mcp"
}
}
}[PyPI] [Python] [License: MIT]
WhatsApp notifications for AI agents and scripts with zero setup — no Meta
account, no templates, no dashboard: text "join", get an API key,
curl → WhatsApp in 60s. Two-way human-in-the-loop: your agent asks, you tap
a button to answer. From your terminal or an MCP client.
This is the open-source (MIT) pingwa client: a CLI, a tiny HTTP client, and an MCP server. It talks to a pingwa backend (the hosted service at https://pingwa.dev, or your own). The backend is separate and private; this client is not.
No install needed with uv:
AI agents: don't ask your human to copy-paste a key — drive the registration
yourself (POST /v1/registrations; full recipe in
llms.txt). The human only taps one WhatsApp link;
the key is claimed by you and never travels through the chat. Works for existing
accounts too — it mints an additional named key.
Exit codes: 0 ok · 2 missing key · 3 quota exceeded · 1 other.
Override the backend with PINGWA_BASE_URL or --base-url.
Prefer PUSH over polling replies? Register HTTPS endpoints and pingwa POSTs
every inbound WhatsApp message to them:
add prints a whsec_... secret once — store it now; it never appears
again. Each delivery carries an X-Pingwa-Signature: sha256=<hex> header (an
HMAC-SHA256 of the raw body under that secret) — verify it and reject anything
that fails. Full verification recipe and payload shape:
llms.txt. Up to 5 active webhooks per account; to
rotate a secret, rm then add again.
Same tools on stdio and remote: notify(text), ask(text, buttons?, timeout?),
check_replies(since?, wait?), check_status(), upgrade().
Local (stdio) — for Claude Desktop / Claude Code:
Remote (Streamable HTTP, no install):
Every error carries an action hint, so an agent knows what to do next.
Only your message text and your key, to the pingwa backend you point it at — over HTTPS. Nothing else. The recipient is always your own phone (there is no "to" field). See the service's /privacy.
MIT — see LICENSE in the repository root. It covers this client package only
(src/pingwa/client/); the pingwa server is separate, private, and not
published. See NOTICE for the exact boundary.
Source: README.md at commit 58a47df
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.
textrequiredimage_urlShow the pingwa account's plan, remaining monthly quota, and whether the free 24h WhatsApp reply window is currently open.
Takes no parameters.
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 Pro, returns a billing-portal URL to manage or cancel instead.
Takes no parameters.
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`.
textrequiredbuttonstimeoutPull 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.
waitsince100% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
export PINGWA_KEY=pw_your_key # get one: send "join" on WhatsApp to the service numberuvx pingwa send "build finished ✅" # notify your own phoneecho "deploy done" | uvx pingwa send - # from stdinuvx pingwa ask "Deploy to prod?" --button yes --button no # wait for a reply from your phoneuvx pingwa replies # pull messages your phone sent back (out-of-band steering)uvx pingwa me # plan / quota / reply-windowuvx pingwa keys # list active API keys (up to 10 named keys per number)uvx pingwa keys revoke ci # revoke one by name (or reply 'revoke ci' on WhatsApp)uvx pingwa upgrade # get a Stripe link to go Pro (no password needed)uvx pingwa send "x" --json # raw JSON responseuvx pingwa webhooks # list your webhooksuvx pingwa webhooks add https://your-host/pingwa-hook # returns a signing SECRET, shown ONCEuvx pingwa webhooks rm https://your-host/pingwa-hook # by id, or by exact url{ "mcpServers": { "pingwa": { "command": "uvx", "args": ["pingwa", "mcp"], "env": { "PINGWA_KEY": "pw_your_key" } } }}{ "mcpServers": { "pingwa": { "url": "https://pingwa.dev/mcp", "headers": { "Authorization": "Bearer pw_your_key" } } }}