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