Change Trace MCP
A 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.
README
Change Trace MCP
Change Trace MCP is a local-first, model-neutral MCP server for collecting and normalizing change-scoped release evidence. The user's existing Agent makes semantic judgments; this package keeps evidence preparation deterministic and reviewable.
M1 Host and cloud-runner compatibility and the M2 deterministic evidence core are complete. M3 Agent review-contract work is in progress. The currently exposed MCP tools are:
get_server_inforeports process and runtime metadata;get_compatibility_fixturereturns a byte-stable fixture for Host smoke tests;get_change_scopereturns a deterministic, bounded Git change summary for an explicit repository root and two refs;collect_local_evidencereturns bounded, provenance-rich excerpts from configured repository document roots;get_review_bundlecombines change and document evidence into a bounded, indexed bundle with deterministic facts and missing-evidence records;validate_findingsvalidates Agent output against the shared schema and the bundle's evidence/source indexes;write_reportrenders validated findings as a deterministic Markdown and JSON report pair inside a repository-relative output directory.
Requirements
- Node.js 22 or newer.
Local development
npm install
npm run check
npm test
Run the stdio server from a local checkout:
npm run build
node dist/cli.js
The server reserves stdout for MCP JSON-RPC messages. Structured operational logs are emitted to stderr.
write_report usage
write_report accepts a validated ReviewBundle, a FindingValidationResult,
reviewer metadata, and a repository-relative output path. It renders a
deterministic Markdown report and a structured JSON report as a pair of files:
<reportName>.md— human-readable Markdown with safe code fences, escaped HTML, and bounded structure;<reportName>.json— machine-readable report conforming to the versionedReportJSON Schema.
The tool requires:
repositoryRoot— an absolute path to the repository working directory;outputDirectory— a path relative torepositoryRoot. Absolute paths,..traversal,.gitmetadata paths, and symlink escapes are rejected;reportName— a safe basename ([A-Za-z0-9][A-Za-z0-9._-]{0,127}) that determines the output filenames;bundle— a validatedReviewBundlefromget_review_bundle;validationResult— the matchingFindingValidationResultfromvalidate_findings. The validation result'sbundleIdmust equal the bundle's ID;reviewMeta— caller-supplied reviewer identity, requiredcreatedAttimestamp (ISO 8601), optional tool version, notes, and declared limitations; identical inputs includingcreatedAtproduce byte-identical reports;
Optional parameters:
overwrite— whentrue, existing report files are replaced. The default (false) refuses the write if either report file exists;maxReportSizeBytes— an output size bound. The default is 10 MiB; the absolute hard maximum is 100 MiB. The write fails instead of silently truncating findings.
The tool returns a structured result with reportId, absolute paths to the
written files, and their byte sizes. Error responses are bounded and do not
expose report content.
Example MCP call flow:
get_change_scope → collect_local_evidence → get_review_bundle →
validate_findings → write_report
Contribution workflow
This repository uses a coordinator/worker model with isolated worktrees,
tracked task assignments, and coordinator-owned Roadmap and release decisions.
See docs/CONTRIBUTING_WORKFLOW.md before
starting delegated implementation work.
Versioned schemas
The package exports strict Zod schemas and deterministic Draft 2020-12 JSON
Schema documents for EvidenceItem, ChangeScope, LocalEvidenceCollection,
ReviewBundle, Finding, FindingValidationResult, and Report:
import {
evidenceItemSchema,
exportCoreJsonSchemas,
} from "change-trace-mcp";
const evidence = evidenceItemSchema.parse(input);
const jsonSchemas = exportCoreJsonSchemas();
Host-specific setup and the current compatibility matrix live in
docs/smoke-tests/.
See docs/ROADMAP.md for milestone scope and
docs/PROJECT_DECISIONS.md for accepted product
and architecture decisions.
License
Apache-2.0. See LICENSE.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.