release-evidence-pack-mcp
Provides tools to inspect Git working-tree changes from a base revision and combine them with test summaries into release evidence packs.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@release-evidence-pack-mcp build a release evidence pack for the checkout service against main"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Release Evidence Pack MCP
A read-only Model Context Protocol server that converts local Git changes and JUnit XML reports into traceable release evidence, risk findings, and a rollback checklist.
Why
Release decisions often rely on scattered screenshots, chat messages, CI logs, and assumptions. This server creates a reproducible evidence pack without deploying, modifying the repository, or uploading source code.
Related MCP server: mcp-policy-guardian
Tools
inspect_release_changes
Inspect a working-tree diff from a base revision and flag high-risk surfaces such as destructive SQL and source changes without test evidence.
summarize_test_reports
Summarize JUnit XML totals while excluding testcase logs and captured output.
build_release_evidence_pack
Combine Git changes and test summaries into structured JSON plus a Markdown decision pack with findings and rollback checks.
Install
npm install
npm run buildNode.js 20 or later is required.
Configure
Set RELEASE_EVIDENCE_ALLOWED_ROOTS to one or more repository roots. Separate paths with ; on Windows or : on Linux/macOS. The current directory is the only allowed root when the variable is absent.
{
"mcpServers": {
"release-evidence-pack": {
"command": "node",
"args": ["/absolute/path/release-evidence-pack-mcp/dist/index.js"],
"env": {
"RELEASE_EVIDENCE_ALLOWED_ROOTS": "/absolute/path/repositories"
}
}
}
}Example
build_release_evidence_pack({
"repositoryRoot": "/workspace/service",
"baseRef": "origin/main",
"reportFiles": ["target/surefire-reports/TEST-api.xml"]
})Paired Skill
skills/release-readiness-review turns MCP findings into a strict GO, CONDITIONAL GO, or NO-GO decision with evidence inventory, release gates, owners, and rollback steps.
Security Model
Read-only Git and file inspection.
No network calls or deployment actions.
No shell interpolation; Git is invoked with an argument array.
Repository access restricted to configured roots.
Report paths cannot escape the repository root.
Testcase logs and captured output are not returned.
Development
npm test
npm run build
npm pack --dry-runLicense
MIT
Available Tools
3 toolsbuild_release_evidence_packBuild release evidence packARead-onlyIdempotent
Combine Git changes and JUnit reports into a risk decision, findings, and rollback checklist.
Inputs: repositoryRoot (required), baseRef, reportFiles.
inspect_release_changesInspect release changesARead-onlyIdempotent
Inspect a local Git diff and classify release risk without changing the repository.
Inputs: repositoryRoot (required), baseRef.
summarize_test_reportsSummarize test reportsARead-onlyIdempotent
Summarize local JUnit XML reports without returning testcase logs or captured output.
Inputs: reportFiles (required), repositoryRoot (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool has a clearly distinct responsibility: one inspects Git changes, one summarizes test reports, one combines them into a final pack. No overlap or ambiguity in purpose.
All tool names follow a consistent verb_noun snake_case pattern (inspect_release_changes, summarize_test_reports, build_release_evidence_pack), making the set predictable and easy to navigate.
Three tools is well-scoped for the server's specific purpose of generating a release evidence pack. Each tool earns its place and there is no redundancy or bloat.
The tool set covers the entire workflow from inspecting changes and summarizing reports to building the final evidence pack. There are no obvious gaps or dead ends for the stated domain.
Maintenance
Related MCP Connectors
Read-only release evidence for coding agents: findings, deliveries, source and runtime data.
A Model Context Protocol (MCP) application for automated GitHub PR analysis and issue management.…
A MCP server built for developers enabling Git based project management with project and personal…
The Cortex MCP server provides read-only access to real-time engineering context from the Cortex developer portal, allowing AI coding assistants to answer natural language questions about your organization's catalog (microservices, libraries, domains, teams, infrastructure), scorecards (engineering standards and best practices), initiatives (goals and deadlines), and Engineering Intelligence metrics. It includes tools for querying documentation, tracking personal entities, and accessing AI-assisted insights across the entire Cortex ecosystem.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that provides read-only access to GitHub repositories, enabling AI assistants to perform code reviews without write permissions.MIT
- FlicenseAqualityDmaintenanceA deterministic, network-free MCP server for validating repository release hygiene and version alignment in local projects. It enables automated repository health checks and generates standardized release checklists based on project state.1-
- AlicenseBqualityCmaintenanceA Model Context Protocol server for GitBook that enables reading content and driving a change-request write workflow.8918 npmMIT
- AlicenseAqualityDmaintenanceA local-first, model-neutral MCP server for collecting and normalizing change-scoped release evidence. It provides deterministic Git change summaries, evidence collection, and review bundles for agent review.74 npmApache 2.0