2 #merge-conflicts MCP Servers & Clients
Every MCP server and client below is tagged #merge-conflicts — install one to give Claude, Cursor, VS Code, or any other MCP-compatible client access to merge-conflicts tools.
すべて
Semamerge
vineethwilson15
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
Rosentic
Rosentic
Deterministic cross-branch conflict detection for AI coding agents. Scans your git repo for function signature mismatches, HTTP route conflicts, and schema breaks across branches using tree-sitter AST analysis. Catches the merge failures that CI misses because tests only run on o
Frequently asked questions
What is a #merge-conflicts MCP server?
- An MCP server tagged #merge-conflicts implements the Model Context Protocol so AI assistants like Claude, Cursor, and VS Code can access merge-conflicts-related tools, data, or APIs.
How many #merge-conflicts MCP servers and clients are there?
- mcp.so currently lists 2 MCP servers and clients tagged #merge-conflicts.
How do I install a #merge-conflicts MCP server?
- Open any server below and copy its install snippet into Claude Desktop, Cursor, VS Code, or another MCP client's configuration — remote servers need no separate download.