Log inSubmit server
Quilt logo

Quilt

by wkoverfield

Tracks per-line agent ownership in one Git checkout and creates ordinary commits containing only each agent’s changes.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Quilt

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "wkoverfield-quilt": {
      "command": "npx",
      "args": [
        "-y",
        "@quilt-dev/cli"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

The install command installed and started the server, which then stopped for configuration (such as an API key) that our sandbox does not have — expected for servers that connect to your account.

npx -y @quilt-dev/cli

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 2d ago.

Overview

wkoverfield/quilt MCP server coordinates multiple AI coding sessions in one shared Git checkout by tracking which actor changed each line. It uses capture hooks for attribution, symbol-level claims for collision prevention, and Quilt commands to preview and commit only an agent’s own changes. Reach for it when separate agents need to share one install, build, or dev environment without merging unrelated uncommitted work. Git remains the source of truth, while Quilt stores local coordination data in a removable `.quilt/` directory.

Use cases

  • Coordinate several coding agents in one checkout
  • Prevent agents from overwriting claimed symbols
  • Commit only one agent’s lines from a shared working tree
  • Inspect ownership and blocked work across active agents

Key features

  • Per-line edit attribution
  • Symbol-level claims
  • Collision prevention before writes
  • Agent-specific Git commits
  • Local fleet monitoring
  • Git commit provenance

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

6/7 checks healthy over the last 79d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 3d ago via OSV.dev · @quilt-dev/cli (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars7Stargazers on the source repository.
npm downloads685Package downloads in the last 30 days.
Last commit6d agoMost recent push to the default branch.
Install checkRunsOur sandbox started it; it then asked for an API key or config.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Quilt works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Quilt

wkoverfield/quilt is an MCP server that connects AI coding sessions to a shared Git checkout and exposes claim and collision-prevention tools. It tracks edits by actor, blocks writes into claimed code, and supports per-agent commits through Quilt’s command-line workflow. Git remains the source of truth, with coordination state stored locally in `.quilt/`.

Install the CLI with `npm install -g @quilt-dev/cli`, then run `quilt setup` in the repository. Setup wires the capture hooks and can add the optional MCP tools. Run `quilt doctor` afterward to verify that the repository is connected and edits are being captured.

It denies writes into code claimed by another actor before any bytes change. Agents can claim individual symbols or whole files, and a denial includes the holder’s stated intent and lease information. If uncommitted lines are overwritten, Quilt snapshots the affected version.

Run `quilt commit --mine -m "message"` after reviewing `quilt preview --mine`. Quilt reconstructs the current actor’s lines and creates an ordinary Git commit containing those changes, even when other actors have uncommitted edits in the same file.

Yes, it supports Claude Code sessions and can optionally enable the Quilt MCP server for a project. Capture hooks attribute edits automatically, while the MCP tools add claim and collision-prevention capabilities. The command-line workflow remains available whether or not the optional MCP tools are enabled.

Related MCP servers

All in Version Control All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewQuilt AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/wkoverfield-quilt?style=directory)](https://allmcps.com/mcp/wkoverfield-quilt)
HTML Embed
<a href="https://allmcps.com/mcp/wkoverfield-quilt"><img src="https://allmcps.com/api/badge/wkoverfield-quilt?style=directory" alt="Quilt on AllMCPs" /></a>