Metadata-Version: 2.4
Name: rosentic-mcp
Version: 0.1.1
Summary: MCP server for Rosentic — deterministic cross-branch conflict detection for AI coding agents
Project-URL: Homepage, https://rosentic.com
Project-URL: Repository, https://github.com/Rosentic/rosentic-engine
Project-URL: Issues, https://github.com/Rosentic/rosentic-engine/issues
Author-email: Rosentic <hello@rosentic.com>
License-Expression: MIT
License-File: LICENSE
Keywords: ai-agents,code-review,git,mcp,merge-conflicts,tree-sitter
Classifier: Development Status :: 4 - Beta
Classifier: Intended Audience :: Developers
Classifier: Topic :: Software Development :: Quality Assurance
Classifier: Topic :: Software Development :: Version Control :: Git
Requires-Python: >=3.11
Requires-Dist: fastmcp>=3.1.0
Description-Content-Type: text/markdown

# Rosentic MCP Server

CI checks each PR against main. It doesn't check open PRs against each other.

Rosentic does. Install one package. Your coding agent checks for cross-branch conflicts before you merge.

One agent changes a function signature. Another agent still calls the old version. Both pass CI. Git merges the text cleanly. Main breaks.

Rosentic compares every open PR against every other open PR. Deterministic static analysis. No LLM. 12 languages. Code never leaves your machine.

## Install

```bash
pip install rosentic-mcp
```

## Configure

### Claude Code

Add to `~/.claude.json`:

```json
{
  "mcpServers": {
    "rosentic": {
      "command": "rosentic-mcp"
    }
  }
}
```

### Cursor / VS Code

Add to MCP settings:

```json
{
  "rosentic": {
    "command": "rosentic-mcp"
  }
}
```

## Tools

### `check_conflicts`

Scan a git repo for cross-branch conflicts affecting your current branch.

**Parameters:**
- `repo_path` (required) — path to local git repository
- `branch` — branch to check (defaults to current branch)
- `base` — base branch to compare against (defaults to `main`)
- `format` — `"summary"` (natural language) or `"json"` (structured findings)

**Example response:**
> Rosentic found 4 unique conflict(s) for feature/auth-refactor: 2 UNSAFE, 2 WARNING. Layer breakdown: 3 L1 signature, 1 L2 route. Most critical: createUser() in src/auth/users.ts — changed from 2 to 3 required params. Recommendation: inspect the UNSAFE findings first and update the stale branch before merging.

### `explain_conflict`

Get detailed explanation of a specific finding, including affected branches, consumer locations, and remediation steps.

**Parameters:**
- `repo_path` (required) — path to local git repository
- `finding_id` (required) — ID from a previous `check_conflicts` result

### `list_branches`

List local branches sorted by most recent commit date.

**Parameters:**
- `repo_path` (required) — path to local git repository

## What it detects

| Layer | What | Example |
|-------|------|---------|
| L1 | Function signature mismatches | Branch A adds required param, Branch B still calls with old arity |
| L2 | HTTP route contract breaks | Route path or method changes, consumers still call old endpoint |
| L3 | Schema incompatibilities | Proto field removed, GraphQL type changed, OpenAPI contract broken |

## How it works

- **Deterministic** — no LLM in the scan path. Tree-sitter AST parsing + evidence-gated verdicts.
- **Fast** — scans 30 branches in under 30 seconds for most repos.
- **Evidence-based** — every finding includes proof: which symbol changed, where it's called, why it's linked.

## Requirements

- Python 3.11+
- Git repository with branches to scan
- Works on macOS, Linux, Windows (WSL)

## Links

- [Website](https://rosentic.com)
- [GitHub](https://github.com/Rosentic/rosentic-engine)
- [GitHub Action](https://github.com/Rosentic/rosentic-engine#github-action)

<!-- mcp-name: io.github.Rosentic/rosentic -->
