The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Semamerge listing page.
An MCP (Model Context Protocol) server that detects semantic merge conflicts between Git branches using AST-level analysis.
When two branches change code in ways that Git merges cleanly but are functionally incompatible, SemaMerge catches it before the merge breaks your app.
| Conflict Type | Example |
|---|---|
| Type signature change | Branch A changes getUser() return type, Branch B calls getUser().address |
| Removed/renamed export | Branch A removes export function validate(), Branch B adds import { validate } |
| Parameter change | Branch A adds required param to function, Branch B calls with old signature |
| Interface/contract break | Branch A adds required field to interface, Branch B implements without it |
| Enum/constant change | Branch A removes Status.PENDING, Branch B uses Status.PENDING |
| Import path change | Branch A moves file, Branch B imports from old path |
Or install globally:
Or clone and build from source:
check_merge_safetyQuick pre-merge check. Returns a risk score (safe/warning/danger).
analyze_branchesDeep analysis with per-file breakdown of all semantic conflicts.
list_semantic_changesLists all semantic changes on a branch (functions, exports, types, etc.).
analyze_file_pairDeep-dive into a specific file's semantic diff between two branches.
Add to your VS Code settings.json:
Add to claude_desktop_config.json:
.ts, .tsx, .js, .jsx, .mjs, .cjs)git showMIT