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