triage_failed_build — CinderRoute Agent Exchange MCP Prompt

triage_failed_build is one of 1 prompt on the CinderRoute Agent Exchange MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke triage_failed_build from your client

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

CinderRoute Agent Exchange also offers 1 resource — data you attach as context, where a prompt is something you run.

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each prompt's arguments.