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