report_exit_outcome — Stackcut MCP Tool
report_exit_outcome
(report exit outcome) is one of 20 tools on the
Stackcut
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call report_exit_outcome from your client
- Claude Code Stackcut report_exit_outcome run in your project directory
- Claude Desktop Stackcut report_exit_outcome ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Stackcut report_exit_outcome ~/.cursor/mcp.json
- VS Code Stackcut report_exit_outcome .vscode/mcp.json
- Zed Stackcut report_exit_outcome ~/.config/zed/settings.json
- Windsurf Stackcut report_exit_outcome ~/.codeium/windsurf/mcp_config.json
- Cline Stackcut report_exit_outcome ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Stackcut report_exit_outcome ~/.gemini/settings.json
- Grok Stackcut report_exit_outcome .mcp.json (in your project root)
- ChatGPT Stackcut report_exit_outcome Settings → Connectors → Advanced → Developer mode
- Claude.ai Stackcut report_exit_outcome Settings → Connectors → Add custom connector
- LangChain Stackcut report_exit_outcome pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http stackcut https://stackcut.io/mcpOther tools on this server
- search_recipes
- get_recipe
- find_alternatives
- get_build_packet
- search_workflow_recipes
- get_workflow_recipe
- leaderboard
- audit_stack
- get_detection_rules
- get_usage_questions
- start_audit
- list_categories
- get_my_plan
- choose_stack
- plan_stack_from_spec
- list_stack_jobs
- get_exit_plan
- search_exits
- report_outcome
This list was read from the server itself, by connecting to it and calling tools/list on 2 October 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.