wait_for_event — Kivel MCP Tool
wait_for_event
(wait for event) is one of 66 tools on the
Kivel
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call wait_for_event from your client
- Claude Code Kivel wait_for_event run in your project directory
- Claude Desktop Kivel wait_for_event ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Kivel wait_for_event ~/.cursor/mcp.json
- VS Code Kivel wait_for_event .vscode/mcp.json
- Zed Kivel wait_for_event ~/.config/zed/settings.json
- Windsurf Kivel wait_for_event ~/.codeium/windsurf/mcp_config.json
- Cline Kivel wait_for_event ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Kivel wait_for_event ~/.gemini/settings.json
- Grok Kivel wait_for_event .mcp.json (in your project root)
- ChatGPT Kivel wait_for_event Settings → Connectors → Advanced → Developer mode
- Claude.ai Kivel wait_for_event Settings → Connectors → Add custom connector
- LangChain Kivel wait_for_event pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http kivel https://kivel.io/mcpOther tools on this server
- create_test_wallet
- wallet_balance
- wallet_pay
- list_wallet_transactions
- create_test_paywall
- create_test_checkout
- complete_test_checkout
- save_credential
- list_credentials
- reveal_credential
- generate_password
- add_authenticator
- get_totp_code
- list_authenticators
- delete_authenticator
- get_email_attachment
- create_oauth_provider
- create_phone_number
- list_phone_numbers
- release_phone_number
- list_sms
- wait_for_sms
- call_mock_api
- create_webhook_inbox
- inspect_webhook_inbox
- wait_for_webhook
- set_webhook_response
- delete_webhook_inbox
- create_email_inbox
- wait_for_email
- list_emails
- list_email_threads
- get_email_thread
- email_draft
- email_inbox_rules
- send_email
- start_login
- start_trial
- finish_login
- ask_human
- wait_for_approval
- create_monitor
- accept_dns_changes
- list_monitors
- delete_monitor
- memory_set
- memory_get
- memory_list
- memory_delete
- create_mock_api
- inspect_mock_api
- delete_mock_api
- upload_temporary_file
- inspect_temporary_file
- delete_temporary_file
- download_temporary_file
- run_tool
- ping_monitor
- inspect_monitor
- pause_monitor
- workspace_status
- resource_request
- describe_tool
- search_tools
- list_tools
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 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.