Mmcp.market

Quilt MCP server

by wkoverfield·io.github.wkoverfield/quilt·v0.6.2

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

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

full report

Adoption
Growing

6 stars107 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, 2 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_minewrite action

    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.5 · 2026-09-19 · 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 4 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

Install directly

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

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, Claude Desktop or Cursor 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 4 days ago (2026-09-16). The latest release is v0.6.2.
What can I use instead of Quilt?
Servers from other publishers that do the same job: GitPin MCP server, Gitwand MCP server and Palinode MCP server. Compare all Quilt alternatives.

Alternatives to Quilt

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

All Quilt alternatives →
  • GitPin
    Prove and verify multi-repo claims at Git HEAD: path, line, full SHA, no index.
    A
  • Gitwand
    Auto-resolves Git merge conflicts so agents only touch the complex hunks.
    A
  • Palinode
    Inspectable, correctable project memory in git-versioned Markdown for AI agents.
    C
  • Srclight
    Deep code indexing for AI agents. FTS5 + embeddings + call graphs + git intelligence. Fully local.
    A
  • Contentrain
    Git-native content governance for AI agents — 27 deterministic MCP tools over stdio and HTTP.
    A

More from wkoverfield