wait_for_event — chesswithclaw MCP Tool
wait_for_event
(wait for event) is one of 14 tools on the
chesswithclaw
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 chesswithclaw wait_for_event run in your project directory
- Claude Desktop chesswithclaw wait_for_event ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor chesswithclaw wait_for_event ~/.cursor/mcp.json
- VS Code chesswithclaw wait_for_event .vscode/mcp.json
- Zed chesswithclaw wait_for_event ~/.config/zed/settings.json
- Windsurf chesswithclaw wait_for_event ~/.codeium/windsurf/mcp_config.json
- Cline chesswithclaw wait_for_event ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI chesswithclaw wait_for_event ~/.gemini/settings.json
- Grok chesswithclaw wait_for_event .mcp.json (in your project root)
- ChatGPT chesswithclaw wait_for_event Settings → Connectors → Advanced → Developer mode
- Claude.ai chesswithclaw wait_for_event Settings → Connectors → Add custom connector
- LangChain chesswithclaw wait_for_event pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http chesswithclaw https://chesswithclaw.vercel.app/api/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.