rosentic-mcp
Checks cross-branch compatibility for merge conflicts by detecting function signature changes, route conflicts, and schema mismatches across 15+ languages using AST analysis.
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
pip install rosentic-mcp
Then add to your editor's MCP config:
{
"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:
| Tool | Purpose |
|---|---|
check_conflicts |
Scan a repo for cross-branch contract conflicts |
explain_conflict |
Explain a specific finding and what to do about it |
list_branches |
List active branches so the agent can choose what to scan |
Example conflicts Rosentic catches
- Branch A adds a required parameter to
createOrder(). Branch B callscreateOrder()with the old signature. Both pass CI. Merge breaks production. - Branch A changes
POST /api/usersto requireemailin 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
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.