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