Rosentic

io.github.RosenticPublished by GitHub account Rosenticv0.1.1Updated Oct 24, 2026

Deterministic cross-branch conflict detection for AI coding agents

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

A local MCP server that lets an AI coding agent detect cross-branch merge conflicts in a git repository using deterministic AST analysis.

What you can do
Scan a repository's branch heads for cross-branch contract conflicts such as broken function signatures, HTTP route mismatches and schema changes across many languages, with results reported as findings rather than AI review opinions. Explain a specific conflict finding and what to do about it. List active branches so the agent can choose which ones to scan. Runs locally against the git repository, with no code leaving the machine.
When to use it
Useful before pushing, opening a pull request or merging, when several branches change shared functions, API routes or schemas and you want to know whether one branch will break another after merge. Complements per-file security or code review tools rather than replacing them.
Requirements
A local Python environment with the rosentic-mcp package installed from PyPI, plus an MCP-capable editor configured to launch the rosentic-mcp command over stdio. It operates on a local git repository with the branches to compare. No accounts, API keys or environment variables are declared.
Before you install
It reads the local git repository and branch heads to perform its analysis, so it should be pointed only at repositories you are comfortable having scanned. It reports conflicts but does not modify code; acting on its findings, such as changing signatures or routes, is left to the agent or user.

Installation

In SourceWeft

  1. Open Rosentic in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Rosentic - Cross-Branch Merge Safety

Rosentic checks whether your active branches are compatible with each other before merge. It detects broken function signatures, HTTP route conflicts, and schema mismatches across 15+ languages using deterministic AST analysis.

This is not AI code review. Rosentic finds structural contract conflicts that would cause runtime failures after merge - the kind of breaks that tests don't catch because they only run on one branch at a time.

Install

bash
pip install rosentic-mcp

Then add to your editor's MCP config:

json
{  "mcpServers": {    "rosentic": {      "command": "rosentic-mcp",      "args": [],      "env": {}    }  }}

Works with Cursor, Claude Code, Cline, Windsurf, and any editor that supports MCP.

What it does

Rosentic gives your AI coding agent three MCP tools:

ToolPurpose
check_conflictsScan a repo for cross-branch contract conflicts
explain_conflictExplain a specific finding and what to do about it
list_branchesList active branches so the agent can choose what to scan

Example conflicts Rosentic catches

  • Branch A adds a required parameter to createOrder(). Branch B calls createOrder() with the old signature. Both pass CI. Merge breaks production.
  • Branch A changes POST /api/users to require email in the request body. Branch B's frontend still sends the old payload.
  • Branch A removes a field from a GraphQL type that Branch B's query depends on.

How it works

Before you push, open a PR, or merge, your agent runs a cross-branch compatibility check. It calls check_conflicts, which scans your repo's branch heads using tree-sitter AST parsing and reports any conflicts.

No code leaves your machine. The scan runs locally against your git repo.

Compared to Semgrep Guardian

Semgrep Guardian checks each file for security vulnerabilities and code issues. Rosentic checks whether your branches are compatible with each other. They solve different problems and work well together:

  • Semgrep Guardian: "Is this code safe and correct on its own?"
  • Rosentic: "Will this branch break other branches when merged?"

Links

Source: README.md at commit a30c458

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.