wait_for_ack — PingRoom MCP Tool
wait_for_ack
(wait for ack) is one of 42 tools on the
PingRoom
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call wait_for_ack from your client
- Claude Code PingRoom wait_for_ack run in your project directory
- Claude Desktop PingRoom wait_for_ack ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor PingRoom wait_for_ack ~/.cursor/mcp.json
- VS Code PingRoom wait_for_ack .vscode/mcp.json
- Zed PingRoom wait_for_ack ~/.config/zed/settings.json
- Windsurf PingRoom wait_for_ack ~/.codeium/windsurf/mcp_config.json
- Cline PingRoom wait_for_ack ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI PingRoom wait_for_ack ~/.gemini/settings.json
- Grok PingRoom wait_for_ack .mcp.json (in your project root)
- ChatGPT PingRoom wait_for_ack Settings → Connectors → Advanced → Developer mode
- Claude.ai PingRoom wait_for_ack Settings → Connectors → Add custom connector
- LangChain PingRoom wait_for_ack pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http pingroom https://api.pingroom.io/api/agent/mcp
Other tools on this server
- connection_info
- disconnect
- redeem_code
- list_rooms
- list_quick_actions
- trigger_quick_action
- broadcast
- live_status
- get_live_status
- list_room_icons
- list_notifications
- get_notification
- wait_for_notification
- request_approval
- wait_for_approval
- get_approval
- ask_question
- wait_for_answer
- get_question
- list_questions
- cancel_question
- activate_agent_inbox
- create_handoff
- wait_for_handoff
- get_handoff
- list_handoffs
- upload_attachment
- get_attachment
- delete_attachment
- get_room
- create_room
- create_public_room
- join_room
- list_webhooks
- create_webhook
- update_webhook
- delete_webhook
- update_quick_action
- update_quick_actions
- set_avatar
- rotate_handle
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.