How do I install the release mcp server?

This profile does not contain a verified copy-paste launch configuration. Follow the current project documentation to confirm the runtime, entry point, transport and authentication before registering it in your client.

SSyncDev

Start a project

Release MCP Server

MCP server that aggregates CI failures, cross-references flakiness history, and generates go/no-go release recommendations

Local serverstdioGo

What is the Release MCP Server?

MCP server that aggregates CI failures, cross-references flakiness history, and generates go/no-go release recommendations

What it actually does

MCP server that aggregates test failures, cross-references flakiness history, and outputs a GO / CONDITIONAL_GO / NO_GO / INVESTIGATE release decision — so your AI agent can triage a broken CI run in seconds instead of asking you to read 3000 lines of logs.

More MCP options

Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.

Maintainer setup documentation.

Recorded tools

Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.

Tool	What it does
aggregate_suite_failures	Groups failures by normalized error signature, deduplicates repeated errors, categorizes as assertion / timeout / network / crash. Pass customInfraPatterns for cloud-specific errors.
cross_reference_flakiness	Scores each failure against your flakiness history: KNOWN FLAKY, MILDLY FLAKY, or NO HISTORY.
correlate_code_changes	Matches changed files against failing tests. Works standalone or with pre-computed affected test lists from [ast-impact-mapper-mcp](https://www.npmjs.com/package/ast-impact-mapper-mcp).
generate_release_recommendation	The final step. Outputs a risk-weighted verdict with confidence score and full breakdown. Supports format: "markdown" for GitHub PR comments and Slack.
detect_temporal_failure_patterns	Analyzes historical failures with timestamps to identify chronometric artifacts — failures that only appear at the same UTC hour, weekday, day of month, or during DST transitions. When a pattern is found, the failure is
analyze_rollback_readiness	Scans a repository for versioned migration files (Flyway V*.sql, Prisma migration.sql, Liquibase XML/YAML) and classifies each operation as additive (rollback safe) or destructive (forward-fix only).

How to install the Release MCP Server

{
  "mcpServers": {
    "release-readiness-triage": {
      "command": "npx",
      "args": [
        "-y",
        "release-readiness-triage-mcp"
      ]
    }
  }
}

From the project documentation. Replace placeholders and example paths before connecting.

Example prompts to try

“Use Release to aggregate suite failures.”
“Use Release to cross reference flakiness.”
“Use Release to correlate code changes.”

Frequently asked questions

MCP server that aggregates CI failures, cross-references flakiness history, and generates go/no-go release recommendations Confirm the tools offered by your installed version in the connected client. Tool availability and permissions depend on the server and account configuration.