MCP.Market

Semamerge MCP server

by vineethwilson15·io.github.vineethwilson15/semamerge·v0.1.2

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

B82/100grade B
What users say
No reviews yet
Be the first
Safety scan
B82/100

full report

Adoption
New

0 stars49 downloads/wk

Reviews

Write one

Nobody has reviewed Semamerge yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Semamerge tools (4)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • analyze_branches

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

  • analyze_file_pair

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

  • check_merge_safety

    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.

  • list_semantic_changes

    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.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan25 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 155 days ago8/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 82/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Semamerge compares

Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
82/100
higher than 60% of 1,119 Developer tools servers
Tools
4
the typical Developer tools server has 7
Tools that change things
0%
typical: 5%. Fewer write tools means less an agent can break
Downloads a week
49
more than 37% of 436 Developer tools servers with a package

What its tools let an agent do: 4 read

Install Semamerge in Claude Code, Cursor or VS Code

Runs npx -y semamerge on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add semamerge -- npx -y semamerge
Add to Cursor

What the publisher says

From the Semamerge repository's README, as published. We do not edit it. Read it on GitHub

SemaMerge

<!-- mcp-name: io.github.vineethwilson15/semamerge -->

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

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

checkmergesafety

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"
}

listsemanticchanges

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

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

analyzefilepair

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 claudedesktopconfig.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

Nothing above is checked by us. What we check is on the safety report.

Semamerge: common questions

Is Semamerge MCP server safe?
Mostly: it is graded B (82/100). Read the Semamerge safety report
How do I install Semamerge?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Semamerge need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Semamerge maintained?
The last commit was 193 days ago (2026-04-25). The latest release is v0.1.2.
What can I use instead of Semamerge?
Servers from other publishers that do the same job: Gitwand MCP server, Obsidian Everywhere MCP server and Mergetrain MCP server.
How does Semamerge compare with other Developer tools MCP servers?
safety score 82/100 (higher than 60% of 1,119 Developer tools servers); tools 4 (the typical Developer tools server has 7); tools that change things 0% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Semamerge

Same job from other publishers: the closest match first, then the best rated.

  • Gitwand
    Auto-resolves Git merge conflicts so agents only touch the complex hunks.
    A
  • Obsidian Everywhere
    Graph context, semantic search, guarded edits, and reviewable Git for local Obsidian vaults.
    A
  • Mergetrain
    Queue parallel-agent worktree branches, test together, serialize and recover Git pushes.
    A
  • slivingdoc
    Durable context for agents and people: shared notes with Git-style merges, no silent overwrites.
    B
  • GitLab MCP Server
    GitLab MCP server for projects, merge requests, issues, pipelines, wiki, releases, and more.
    B