Semamerge

Name: Semamerge
Author: vineethwilson15

@vineethwilson15

About Semamerge

MCP server that detects semantic (non-textual) merge conflicts between Git branches using AST-level analysis. Catches incompatible changes that Git merges cleanly but break at runtime — like signature changes, removed exports, interface breaks, and cross-file dependency conflicts

#git #merge-conflicts #ast #code-analysis #typescript #tree-sitter #semantic-analysis

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "semamerge": {
      "command": "npx",
      "args": [
        "-y",
        "semamerge"
      ]
    }
  }
}

Tools

Quick pre-merge safety check. Analyzes two branches for semantic conflicts that Git would miss (signature changes, removed exports, parameter mismatches, etc.). Returns a risk score: safe/warning/danger.

Deep semantic analysis between two branches. Returns a detailed per-file report of all semantic changes and conflicts, including cross-file dependency issues.

Lists all semantic changes on a branch (function additions/removals, export changes, type changes, etc.) relative to a base. Useful for understanding what semantically changed.

Deep-dive semantic diff of a single file between two branches. Shows exactly what each branch changed and where conflicts arise.

Overview

What is Semamerge?

Semamerge is a tool that detects semantic merge conflicts across branches, including type signature changes, removed exports, parameter changes, interface breaks, enum/constant changes, and cross-file dependency breaks. It is aimed at developers who want to identify breaking changes before merging branches.

How to use Semamerge?

Install with npm install -g semamerge. Use the provided CLI tools: check_merge_safety for a quick risk score, analyze_branches for deep per-file analysis, list_semantic_changes to list all semantic changes on a branch, and analyze_file_pair for a single-file deep dive between two branches.