# ChangeAtlas [Health: Active]

**Category:** 🔄 Version Control  
**Repository:** https://github.com/robyroro/mcp-changeatlas  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/changeatlas

## Description
Local Git change impact and related test discovery with inspectable import paths

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "changeatlas": {
    "command": "uvx",
    "args": ["mcp-changeatlas"]
  }
}
```

## Documentation

## What ChangeAtlas does

ChangeAtlas MCP server helps developers inspect the likely impact of local Git changes. It reads a repository on the same machine, compares the working tree with a selected Git commit, and identifies nearby modules and tests connected through static imports. Each suggested result includes the file path and the import chain that led to it, so you can review the basis for the suggestion.

The project belongs in the 💻 Developer Tools category for workflows that need repository-aware change review before a commit. It is intended to narrow the set of files and tests a developer should inspect. It does not determine whether a change is safe, prove that a test covers a behavior, or replace running the project’s test suite.

## How it works

The server indexes tracked Python, JavaScript, and TypeScript files. Python imports are read from the standard-library AST, while relative JavaScript and TypeScript imports, exports, and `require` links are located statically. For a changed file, ChangeAtlas follows reverse import relationships toward dependent modules and tests to a selected depth.

`analyze_changes` compares staged and unstaged working-tree changes with a Git commit. An option can include untracked file names. Paths are resolved against the configured repository root, and paths outside that root are rejected. The implementation does not run project code, test commands, package managers, or Git hooks. File and result limits are fixed.

## Setup and configuration

ChangeAtlas MCP server requires Python 3.11 or newer and Git. Install the package with `pip install mcp-changeatlas`, then configure an MCP client to launch `mcp-changeatlas` with `--root`, the exact repository path, and `serve`.

A typical stdio configuration passes these arguments to the command:

```json
{
  "command": "mcp-changeatlas",
  "args": ["--root", "/path/to/repo", "serve"]
}
```

The repository root is selected by the person running the server and cannot be changed through a tool call. The package also provides command-line forms for viewing an overview, comparing changes, tracing a file, and finding tests.

## Tools and capabilities

The four MCP tools are:

- `repository_overview`: provides an overview of the configured repository.
- `analyze_changes`: examines changes relative to a Git commit.
- `trace_file`: traces related files for a specified path.
- `find_tests`: searches for related tests for a specified path.

Results can show the chain of imports behind each suggestion. This makes the output inspectable rather than presenting an unexplained list of paths.

## Limitations and notes

The ChangeAtlas MCP server resolves local Python imports and relative JavaScript/TypeScript imports only. It does not follow runtime imports, package aliases, monorepo path mappings, or non-code dependencies. Deleted and unsupported files appear under `unindexed_changes`, and incomplete analysis is marked as such.

A suggested test represents an import path, not a coverage claim. The Docker image is intended for directory build checks and a self-contained demonstration; it analyzes the snapshot inside the image. To inspect active local work, install the package locally and point `--root` at the repository.

_Full upstream README: https://allmcps.com/mcp/changeatlas/readme_