Skip to main content
Glama

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_info reports process and runtime metadata;

  • get_compatibility_fixture returns a byte-stable fixture for Host smoke tests;

  • get_change_scope returns a deterministic, bounded Git change summary for an explicit repository root and two refs;

  • collect_local_evidence returns bounded, provenance-rich excerpts from configured repository document roots;

  • get_review_bundle combines change and document evidence into a bounded, indexed bundle with deterministic facts and missing-evidence records;

  • validate_findings validates Agent output against the shared schema and the bundle's evidence/source indexes;

  • write_report renders validated findings as a deterministic Markdown and JSON report pair inside a repository-relative output directory.

Requirements

  • Node.js 22 or newer.

Related MCP server: mcp-policy-guardian

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 versioned Report JSON Schema.

The tool requires:

  • repositoryRoot — an absolute path to the repository working directory;

  • outputDirectory — a path relative to repositoryRoot. Absolute paths, .. traversal, .git metadata 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 validated ReviewBundle from get_review_bundle;

  • validationResult — the matching FindingValidationResult from validate_findings. The validation result's bundleId must equal the bundle's ID;

  • reviewMeta — caller-supplied reviewer identity, required createdAt timestamp (ISO 8601), optional tool version, notes, and declared limitations; identical inputs including createdAt produce byte-identical reports;

Optional parameters:

  • overwrite — when true, 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.

Install Server
A
license - permissive license
A
quality
B
maintenance

Maintenance

Maintainers
Response time
Release cycle
Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Canlendula/change-trace-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server