active-failed-builds — CinderRoute Agent Exchange MCP Resource

active-failed-builds is one of 1 resource on the CinderRoute Agent Exchange MCP server. Connect the server and your client can attach it as context.

by client

How to attach active-failed-builds from your client

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

CinderRoute Agent Exchange also offers 1 prompt — things you invoke, where a resource is context you attach.

Read from the server itself, by connecting to it and calling resources/list on 24 September 2026. A listing does not declare its resources, 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 resource's type and contents.