MCP.so
登录
S

Semamerge

@vineethwilson15

关于 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

基本信息

分类

其他

传输方式

stdio

发布者

vineethwilson15

提交者

Vineeth Wilson

配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

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

工具

4

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.

概览

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.

Key features of Semamerge

  • Detects type signature changes between branches
  • Identifies removed or renamed exports
  • Catches parameter changes in function calls
  • Flags interface/contract breaks
  • Alerts on enum/constant member changes
  • Detects cross-file import/export dependency breaks

Use cases of Semamerge

  • Pre-merge safety check before integrating feature branches
  • Reviewing all semantic changes on a branch before review
  • Deep-diving into a specific file’s conflict between two branches
  • Analyzing cross-file dependency breaks that standard diff tools miss

FAQ from Semamerge

What conflicts does Semamerge detect

评论

其他 分类下的更多 MCP 服务器