Back to Browse

Semamerge MCP Server

Developer ToolsUse Caution4.8MCP RegistryLocal
Free

Server data from the Official MCP Registry

Detects semantic merge conflicts between Git branches using AST-level analysis

About

Detects semantic merge conflicts between Git branches using AST-level analysis

Security Report

4.8
Use Caution4.8High Risk

SemaMerge is a well-structured MCP server for detecting semantic merge conflicts in Git repositories. The codebase demonstrates solid engineering practices with proper input validation, sensible error handling, and appropriate permission scoping. No critical security vulnerabilities or malicious patterns were detected. Minor code quality observations exist but do not materially impact security posture. Supply chain analysis found 2 known vulnerabilities in dependencies (1 critical, 1 high severity). Package verification found 1 issue.

5 files analyzed · 7 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

file_system

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

Shell Command Execution

Runs commands on your machine. Be cautious — only use if you trust this plugin.

env_vars

Check that this permission is expected for this type of plugin.

How to Install

Add this to your MCP configuration file:

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

Documentation

View on GitHub

From the project's GitHub README.

SemaMerge

npm version License: MIT semamerge MCP server

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.

What It Detects

Conflict TypeExample
Type signature changeBranch A changes getUser() return type, Branch B calls getUser().address
Removed/renamed exportBranch A removes export function validate(), Branch B adds import { validate }
Parameter changeBranch A adds required param to function, Branch B calls with old signature
Interface/contract breakBranch A adds required field to interface, Branch B implements without it
Enum/constant changeBranch A removes Status.PENDING, Branch B uses Status.PENDING
Import path changeBranch A moves file, Branch B imports from old path

Installation

npx semamerge

Or install globally:

npm install -g semamerge

Or clone and build from source:

git clone https://github.com/vineethwilson15/semamerge.git
cd semamerge
npm install
npm run build

MCP Tools

check_merge_safety

Quick pre-merge check. Returns a risk score (safe/warning/danger).

{
  "repoPath": "/path/to/repo",
  "sourceBranch": "feature-x",
  "targetBranch": "main"
}

analyze_branches

Deep analysis with per-file breakdown of all semantic conflicts.

{
  "repoPath": "/path/to/repo",
  "branchA": "feature-x",
  "branchB": "feature-y",
  "baseBranch": "main"
}

list_semantic_changes

Lists all semantic changes on a branch (functions, exports, types, etc.).

{
  "repoPath": "/path/to/repo",
  "branch": "feature-x",
  "baseBranch": "main"
}

analyze_file_pair

Deep-dive into a specific file's semantic diff between two branches.

{
  "repoPath": "/path/to/repo",
  "filePath": "src/utils.ts",
  "branchA": "feature-x",
  "branchB": "main"
}

Configuration

VS Code (Copilot)

Add to your VS Code settings.json:

{
  "mcp": {
    "servers": {
      "semamerge": {
        "command": "node",
        "args": ["/path/to/semamerge/dist/index.js"]
      }
    }
  }
}

Claude Desktop

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "semamerge": {
      "command": "node",
      "args": ["/path/to/semamerge/dist/index.js"]
    }
  }
}

Supported Languages

  • TypeScript / JavaScript (.ts, .tsx, .js, .jsx, .mjs, .cjs)
  • Python support planned

How It Works

  1. Git layer — Reads file content from branches without checkout using git show
  2. AST parsing — Parses source code with tree-sitter (WASM) into syntax trees
  3. Semantic extraction — Walks ASTs to extract function signatures, types, exports, imports, enums
  4. Three-way comparison — Computes semantic diffs from common ancestor to each branch
  5. Conflict detection — Cross-references changes to find incompatibilities

Development

npm run build    # Compile TypeScript
npm run dev      # Watch mode
npm test         # Run tests

License

MIT

Reviews

No reviews yet

Be the first to review this server!