plan_stack_from_spec — Stackcut MCP Tool

plan_stack_from_spec (plan stack from spec) 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 plan_stack_from_spec from your client

Claude Code Stackcut plan_stack_from_spec run in your project directory
Claude Desktop Stackcut plan_stack_from_spec ~/Library/Application Support/Claude/claude_desktop_config.json
Cursor Stackcut plan_stack_from_spec ~/.cursor/mcp.json
VS Code Stackcut plan_stack_from_spec .vscode/mcp.json
Zed Stackcut plan_stack_from_spec ~/.config/zed/settings.json
Windsurf Stackcut plan_stack_from_spec ~/.codeium/windsurf/mcp_config.json
Cline Stackcut plan_stack_from_spec ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
Gemini CLI Stackcut plan_stack_from_spec ~/.gemini/settings.json
Grok Stackcut plan_stack_from_spec .mcp.json (in your project root)
ChatGPT Stackcut plan_stack_from_spec Settings → Connectors → Advanced → Developer mode
Claude.ai Stackcut plan_stack_from_spec Settings → Connectors → Add custom connector
LangChain Stackcut plan_stack_from_spec pip install langchain-mcp-adapters

Fastest route

claude mcp add --transport http stackcut https://stackcut.io/mcp

Other 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
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.

Stackcut MCP server