# wkoverfield/quilt [Health: Active]

**Category:** 🔄 Version Control  
**Repository:** https://github.com/wkoverfield/quilt  
**GitHub Stars:** 7  
**npm Downloads (last month):** 685  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/wkoverfield-quilt

## Description
Line-level authorship for a shared Git checkout, so multiple AI coding agents work in one repo and each commits only its own lines. Symbol-level claims prevent collisions and every commit is an ordinary Git commit.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "quilt": {
    "command": "npx",
    "args": ["-y","@quilt-dev/cli"]
  }
}
```

## Documentation

## What wkoverfield/quilt MCP server does

wkoverfield/quilt MCP server supports multiple AI agents, humans, or bots editing one working tree at the same time. It records which actor wrote each line and reconstructs that actor’s changes when a commit is made. The result is an ordinary Git commit containing only the selected actor’s lines, including cases where multiple actors changed the same file or hunk.

The shared-checkout model avoids maintaining a separate install, build cache, dev server, and environment for every agent. Quilt also addresses contention: an actor can claim a symbol such as `utils.js#formatPrice` instead of reserving an entire file. Writes into code claimed by another actor are denied before bytes change, with the holder’s stated intent and lease information shown to the blocked actor.

## How it works

Capture hooks observe edits at the tool boundary and associate them with an agent session. Sessions receive automatic identities when they run through Claude Code or an MCP connection. An explicit identity can be supplied with `QUILT_ACTOR`, or a command can use `quilt --as` when the shell identity must be selected directly.

Claims provide coordination before editing. Quilt supports symbol claims for ten languages through tree-sitter and uses whole-file claims where symbol parsing is unavailable. It can warn when a claimed symbol depends on a function another actor is changing. If an actor overwrites another actor’s uncommitted lines, Quilt snapshots the affected version so the earlier work is not silently discarded.

The `.quilt/` directory contains local state and can be deleted without changing repository files. Quilt does not call an LLM, start agents, or replace Git. Commit provenance is written into the Git commit, while prompt correlation remains local to the Quilt UI.

## Setup and configuration

Install the CLI globally with `npm install -g @quilt-dev/cli`, then run `quilt setup` from the repository. Setup wires the capture hooks and can add the optional MCP tools. `quilt doctor` checks that the wiring is active and that edits are being captured.

Agents can start from the same repository after setup without per-terminal configuration. To use a stable actor name, launch a session with `QUILT_ACTOR=auth-agent`. For shared-shell operations, `quilt --as auth-agent commit --mine ...` makes the intended committer explicit. `quilt config author.email you@example.com` sets the Git email separately from the actor name.

## Tools and capabilities

- `quilt status` shows ownership information.
- `quilt preview --mine` displays the patch the current actor would commit.
- `quilt commit --mine -m "..."` creates a commit containing that actor’s lines.
- `quilt claim` reserves files or symbols with an optional intent.
- `quilt provenance HEAD` reports actor, session, file, hunk, and tree information.
- `quilt fleet --watch` provides a terminal view of actors, claims, and blocked work.
- `quilt ui` opens a local, read-only dashboard at `127.0.0.1`.

The MCP portion supplies claim and collision-prevention tools; the command-line workflow handles setup, inspection, previewing, and commits.

## Limitations and notes

Quilt is designed for a shared Git checkout, not as an agent runtime or language model interface. It does not spawn agents or invoke an LLM. Symbol claims depend on supported parsing; other files use whole-file claims. A denied claim requires coordination with the current holder, waiting for its lease to lapse or for its commit to release the claim. All coordination state is local under `.quilt/`, although commit provenance is retained in Git history.

_Full upstream README: https://allmcps.com/mcp/wkoverfield-quilt/readme_