Change Trace MCP
Click on "Install 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., "@Change Trace MCPget change scope for /repo from main to feature"
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.
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.
Related MCP server: mcp-policy-guardian
Local development
npm install
npm run check
npm testRun the stdio server from a local checkout:
npm run build
node dist/cli.jsThe 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_reportContribution 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.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Tools
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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