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