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