Release MCP Server

MCP server that aggregates CI failures, cross-references flakiness history, and generates go/no-go release recommendations. The release mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 6 defined tools rather than through you.

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.

Its toolset

Everything the assistant can do here goes through one of these:

• aggregate_suite_failures — Groups failures by normalized error signature, deduplicates repeated errors, categorizes as assertion / timeout / network / crash. Pass
• 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
• 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
• 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
• 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

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Release's toolset — aggregate_suite_failures, cross_reference_flakiness, correlate_code_changes and 3 more — is a fair guide to whether it matches your workflow. It is maintained by vola-trebla; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the release mcp server does with a few real requests.