Aggregates CI failures, cross-references flakiness history, and outputs GO/NO_GO release verdicts.
Use this profile to copy client config, check auth requirements, review tools and resources, and compare related MCP servers before adding it to an AI client.
Get practical integration notes and launch examples for MCP servers like release-readiness-triage-mcp.
npx -y release-readiness-triage-mcpAdd this server entry to the mcpServers object in your Claude Desktop config, then restart the app.
{
"mcpServers": {
"io-github-vola-trebla-release-readiness-triage-mcp": {
"command": "npx",
"args": [
"-y",
"release-readiness-triage-mcp"
]
}
}
}~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonNo remote HTTP endpoint is advertised. Use the package or stdio setup shown in Install.
release-readiness-triage-mcp is an MCP server for Aggregates CI failures, cross-references flakiness history, and outputs GO/NO_GO release verdicts.. It supports STDIO transport.
Use the generated config in Install. This server runs with npx -y release-readiness-triage-mcp; add any required environment variables before starting your client.
Choose the Claude Desktop tab in Install and copy the config for npx -y release-readiness-triage-mcp. Add required environment variables before starting Claude Desktop.
Choose the Claude Code tab in Install and copy the config for npx -y release-readiness-triage-mcp. Add required environment variables before starting Claude Code.
Choose the Codex tab in Install and copy the config for npx -y release-readiness-triage-mcp. Add required environment variables before starting Codex.
Choose the Cursor or VS Code tab in Install and copy the config for npx -y release-readiness-triage-mcp. Add required environment variables before starting Cursor or VS Code.
release-readiness-triage-mcp uses STDIO transport. Use the package or command config in Install.
release-readiness-triage-mcp inventory is listed when the MCP endpoint exposes tools, resources, or prompts. Some servers require auth first.
release-readiness-triage-mcp does not advertise a verified auth requirement. If discovery fails, it may still need provider login, an API key, a bearer token, or a session header.
| Package | Registry | Version | Inputs |
|---|---|---|---|
release-readiness-triage-mcpstdio | npm | 0.2.0 | None advertised |