wait_for_email — Openhook MCP Tool
wait_for_email
(wait for email) is one of 29 tools on the
Openhook
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call wait_for_email from your client
- Claude Code Openhook wait_for_email run in your project directory
- Claude Desktop Openhook wait_for_email ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Openhook wait_for_email ~/.cursor/mcp.json
- VS Code Openhook wait_for_email .vscode/mcp.json
- Zed Openhook wait_for_email ~/.config/zed/settings.json
- Windsurf Openhook wait_for_email ~/.codeium/windsurf/mcp_config.json
- Cline Openhook wait_for_email ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Openhook wait_for_email ~/.gemini/settings.json
- Grok Openhook wait_for_email .mcp.json (in your project root)
- ChatGPT Openhook wait_for_email Settings → Connectors → Advanced → Developer mode
- Claude.ai Openhook wait_for_email Settings → Connectors → Add custom connector
- LangChain Openhook wait_for_email pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http openhook-inbox https://openhook.dev/mcp
Other tools on this server
- server_status
- create_webhook
- get_hosted_inboxes
- access_hosted_inbox
- configure_webhook
- get_webhook_info
- get_webhook_email
- register_github_webhook
- register_stripe_webhook
- register_linear_webhook
- unregister_webhook
- delete_webhook
- rotate_webhook_token
- get_webhook_requests
- get_webhook_activity
- search_requests
- get_request
- update_request
- download_request_file
- delete_request
- delete_all_requests
- export_webhook_data
- wait_for_request
- send_requests
- extract_links_from_request
- generate_oob_payloads
- check_for_callbacks
- respond_to_next_request
This list was read from the server itself, by connecting to it and calling tools/list on 14 October 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.