respond_to_next_request — Openhook MCP Tool
respond_to_next_request
(respond to next request) 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 respond_to_next_request from your client
- Claude Code Openhook respond_to_next_request run in your project directory
- Claude Desktop Openhook respond_to_next_request ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Openhook respond_to_next_request ~/.cursor/mcp.json
- VS Code Openhook respond_to_next_request .vscode/mcp.json
- Zed Openhook respond_to_next_request ~/.config/zed/settings.json
- Windsurf Openhook respond_to_next_request ~/.codeium/windsurf/mcp_config.json
- Cline Openhook respond_to_next_request ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Openhook respond_to_next_request ~/.gemini/settings.json
- Grok Openhook respond_to_next_request .mcp.json (in your project root)
- ChatGPT Openhook respond_to_next_request Settings → Connectors → Advanced → Developer mode
- Claude.ai Openhook respond_to_next_request Settings → Connectors → Add custom connector
- LangChain Openhook respond_to_next_request 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
- wait_for_email
- send_requests
- extract_links_from_request
- generate_oob_payloads
- check_for_callbacks
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.