answer_fields — Klarefi MCP Tool
answer_fields
(answer fields) 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 answer_fields from your client
- Claude Code Klarefi answer_fields run in your project directory
- Claude Desktop Klarefi answer_fields ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Klarefi answer_fields ~/.cursor/mcp.json
- VS Code Klarefi answer_fields .vscode/mcp.json
- Zed Klarefi answer_fields ~/.config/zed/settings.json
- Windsurf Klarefi answer_fields ~/.codeium/windsurf/mcp_config.json
- Cline Klarefi answer_fields ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Klarefi answer_fields ~/.gemini/settings.json
- Grok Klarefi answer_fields .mcp.json (in your project root)
- ChatGPT Klarefi answer_fields Settings → Connectors → Advanced → Developer mode
- Claude.ai Klarefi answer_fields Settings → Connectors → Add custom connector
- LangChain Klarefi answer_fields 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
- upload_document
- submit_intake
- save_intake_draft
- wait_for_next_action
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.