wait_for_next_action — Klarefi MCP Tool
wait_for_next_action
(wait for next action) is one of 20 tools on the
Klarefi
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call wait_for_next_action from your client
- Claude Code Klarefi wait_for_next_action run in your project directory
- Claude Desktop Klarefi wait_for_next_action ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Klarefi wait_for_next_action ~/.cursor/mcp.json
- VS Code Klarefi wait_for_next_action .vscode/mcp.json
- Zed Klarefi wait_for_next_action ~/.config/zed/settings.json
- Windsurf Klarefi wait_for_next_action ~/.codeium/windsurf/mcp_config.json
- Cline Klarefi wait_for_next_action ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Klarefi wait_for_next_action ~/.gemini/settings.json
- Grok Klarefi wait_for_next_action .mcp.json (in your project root)
- ChatGPT Klarefi wait_for_next_action Settings → Connectors → Advanced → Developer mode
- Claude.ai Klarefi wait_for_next_action Settings → Connectors → Add custom connector
- LangChain Klarefi wait_for_next_action pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://www.klarefi.com/mcpOther tools on this server
- create_connector_from_openapi
- create_connector
- delete_connector
- create_intake_session
- get_case
- list_operator_queue
- get_case_workspace
- get_case_package
- submit_case_review
- get_review_command
- list_workflows
- save_workflow_draft
- open_intake
- get_intake_state
- answer_question
- answer_fields
- upload_document
- submit_intake
- save_intake_draft
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.