wait_for_webhook — WebhookTest.net MCP Tool
wait_for_webhook
(wait for webhook) is one of 8 tools on the
WebhookTest.net
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call wait_for_webhook from your client
- Claude Code WebhookTest.net wait_for_webhook run in your project directory
- Claude Desktop WebhookTest.net wait_for_webhook ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor WebhookTest.net wait_for_webhook ~/.cursor/mcp.json
- VS Code WebhookTest.net wait_for_webhook .vscode/mcp.json
- Zed WebhookTest.net wait_for_webhook ~/.config/zed/settings.json
- Windsurf WebhookTest.net wait_for_webhook ~/.codeium/windsurf/mcp_config.json
- Cline WebhookTest.net wait_for_webhook ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI WebhookTest.net wait_for_webhook ~/.gemini/settings.json
- Grok WebhookTest.net wait_for_webhook .mcp.json (in your project root)
- ChatGPT WebhookTest.net wait_for_webhook Settings → Connectors → Advanced → Developer mode
- Claude.ai WebhookTest.net wait_for_webhook Settings → Connectors → Add custom connector
- LangChain WebhookTest.net wait_for_webhook pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http webhook-tester https://webhooktest.net/mcpOther tools on this server
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.