MCP.Market

Quilt MCP server

by wkoverfield·io.github.wkoverfield/quilt·v0.6.3·6 stars
No reviews yet

Track which AI agent wrote which lines in a shared Git checkout; each commits only its own lines.

A92/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
Growing

6 stars149 downloads/wk

Reviews

Write one

Nobody has reviewed Quilt yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Quilt tools (12, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • claim

    Reserve files BEFORE you edit them — a claim placed before editing is also what BINDS your external edits to your actor id, so claim whole files first as the default. Use a bare path for a whole file, a trailing slash for a whole directory (e.g. convex/_generated/ — right for codegen output), or `path#symbol` (e.g. utils.js#formatPrice) to reserve one function so others can edit other parts of the

  • commit_mine

    Commit ONLY your owned hunks as an ordinary git commit, leaving every other actor's changes untouched in the working tree. This is how each agent lands its own work in a shared checkout without sweeping up anyone else's. The committed files' claims auto-release, so no separate release call is needed. Preview it first with preview_mine.

  • escalate

    Flag a collision you CANNOT reconcile (e.g. two opposed intents on the same line) for a human. Use this instead of forcing a change through when a denied claim's holderIntent conflicts with yours. It shows up under 'Needs you' until resolved.

  • get_conflicts

    Show overlapping/shared changes and collisions that were caught.

  • get_my_changes

    List the changes YOU own in the working tree: the files and hunks attributed to your actor id, with per-file added/removed line counts. The 'what have I done so far' view, scoped to just you. Review your own work with it before committing — use get_status for who-owns-what across all actors, or preview_mine for the exact patch commit_mine would produce.

  • get_status

    Show who owns which working-tree changes, plus caught collisions and active claims. Call before editing and before committing.

  • preview_mine

    Show the exact patch commit_mine would create right now: only your owned hunks as a unified diff, plus the files, whole-file additions, and added/removed line totals. A dry run, nothing is written. Review it before commit_mine to confirm you are committing your lines and nothing else.

  • quilt_edit

    Edit a file through Quilt instead of your raw editor. Replaces the unique `old_string` with `new_string` and records WHO authored the change at the moment of the edit — so attribution is exact even when several agents share this checkout, with no claims or reconcile guesswork. Pass `why` (your ticket/task). Prefer this over a plain file edit when coordinating a fleet.

  • quilt_writewrite action

    Create or overwrite a whole file through Quilt instead of your raw editor, recording YOU as the author of its contents at write time, so attribution is exact even when several agents share this checkout, with no claims or reconcile guesswork. Use this for new files; use quilt_edit to change part of an existing one. Pass `why` (your ticket/task). If another agent holds this path, the write is denie

  • release

    Release your claims on the given paths. Omit `paths` to release ALL of yours; an empty array releases none.

  • resolve

    Mark a collision as sewn/handled after you reconciled it — closes its 'Needs you' flag and records the audit trail. Use after you've merged or adapted so the work accounts for both intents.

  • start_session

    Register an actor and start a session in this repo, pinning this server to that identity. Optional: if several agents share one server, skip this and pass `actor` on each call instead.

Public scan report

scanner v0.1.10 · 2026-10-14 · same rubric, same numbers if you re-run it

no findings
  • Code scan33 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Quilt compares

Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 90% of 1,119 Developer tools servers
Tools
12
the typical Developer tools server has 7
Tools that change things
8%
typical: 5%. Fewer write tools means less an agent can break
GitHub stars
6
more than 80% of 855 Developer tools servers
Downloads a week
149
more than 66% of 436 Developer tools servers with a package

What its tools let an agent do: 10 read · 1 change · 1 run or deploy

Release history: 2 versions in the registry since 2026-09-10, latest 2026-10-14, typically one every 34 days.

Install Quilt in Claude Code, Cursor or VS Code

Runs npx -y @quilt-dev/cli on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add quilt -- npx -y @quilt-dev/cli
Add to Cursor

What the publisher says

From the Quilt repository's README, as published. We do not edit it. Read it on GitHub

Quilt

<!-- mcp-name: io.github.wkoverfield/quilt -->

Quilt is a command-line tool that tracks which agent wrote which lines in a shared Git checkout, so multiple AI coding agents can work in one repo at once and each commits only its own changes.

It captures every edit at the tool boundary, keeps a per-line record of who wrote what, and reconstructs each agent's own changes at commit time. Git stays the source of truth. Quilt never calls an LLM or spawns agents, and its state lives in a .quilt/ sidecar you can delete without touching your repo.

npm install -g @quilt-dev/cli
quilt setup     # capture hooks wired; claim enforcement via Claude hooks or MCP

The problem

You want your agents in ONE checkout: one node_modules, one build, one dev server, one environment to keep working, not a worktree per agent, each with its own install and its own drift. But on a shared checkout, plain git bites even when agents work on completely different things: the first git commit -am sweeps everyone else's uncommitted files into one blob, codegen and lockfile churn get credited to whoever committed last, and two agents occasionally do land on the same line, where one silently overwrites the other. None of that requires agents to be working on the same task. It's just what a shared checkout does by default.

Quilt makes the shared checkout safe. Every agent commits exactly its own lines and nothing else: disjoint work stays disjoint all the way into history, with no ceremony. And when two agents genuinely want the same code, that becomes a coordinated handoff instead of a silent loss. It holds as you add agents.

./examples/fleet.sh runs seven agents against one checkout. The two endings:

WITHOUT quilt   1 commit for 7 agents — six got "nothing to commit", their
                work swept into the first agent's blob. a7 silently
                overwrote a1's change to getUser. a1's work is gone.

WITH quilt      6 clean commits, one per agent, each exactly its own lines.
                a7's write into a1's claimed function was denied before any
                bytes changed, with a1's stated intent in the denial.

When two agents want the same file

Fanning out on disjoint files is the easy case. The real test is contention. A denied claim isn't a dead end. It carries the holder's stated intent and when their lease lapses:

$ QUILT_ACTOR=builder-flows quilt claim deals.js flows.js --intent "wire flows to deals"
  ✗ denied  deals.js (held by builder-friction)
      builder-friction is: friction pass: rename + archive flags
      their claim lapses 2026-07-04T22:12:05Z unless renewed
  ✓ claimed flows.js

So the blocked agent builds its granted files while it waits, re-claims after the holder's commit auto-releases, and layers its change on top of the landed one. Two clean commits, both changes in the file, nothing lost. ./examples/contention.sh runs the whole sequence on the real machinery.

What it does

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Quilt: common questions

Is Quilt MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the Quilt safety report
How do I install Quilt?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Quilt need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Quilt maintained?
The last commit was 21 days ago (2026-10-14). The latest release is v0.6.3.
What can I use instead of Quilt?
Servers from other publishers that do the same job: Git MCP server, slivingdoc MCP server and Pare Git MCP server. Compare all Quilt alternatives.
How does Quilt compare with other Developer tools MCP servers?
safety score 92/100 (higher than 90% of 1,119 Developer tools servers); tools 12 (the typical Developer tools server has 7); tools that change things 8% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Quilt

Same job from other publishers: the closest match first, then the best rated.

All Quilt alternatives →
  • Git
    Comprehensive Git MCP server enabling native git tools including clone, commit, worktree, & more.
    A
  • slivingdoc
    Durable context for agents and people: shared notes with Git-style merges, no silent overwrites.
    B
  • Pare Git
    Pare Git ג€” Structured git operations (status, log, diff, branch, commit, push) as typed JSON.
    More from Dave-London →
    A
  • Repowise
    Codebase intelligence for AI coding agents — graph, git history, docs, decisions, code health.
    B
  • Gitwand
    Auto-resolves Git merge conflicts so agents only touch the complex hunks.
    A

More from wkoverfield →