Open-source B2B and marketplace ecommerce; new stores include an MCP server for AI agents.
Runs in the cloud★ 15,812BSD-3-ClauseUpdated 8 days ago
Install
Quilt
Overview
Description from the maker (original English)
Track which AI agent wrote which lines in a shared Git checkout; each commits only its own lines.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Online shops & payments
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- The registry lists no key to fill in.
You need
- npmNode.js installed (for the npx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"quilt": {
"command": "npx",
"args": [
"-y",
"@quilt-dev/cli",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add quilt -- npx -y @quilt-dev/cli mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"quilt": {
"command": "npx",
"args": [
"-y",
"@quilt-dev/cli",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"quilt": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@quilt-dev/cli",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account wkoverfield, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Online shops & paymentsi
- More stars than 0% of the other 1753 servers in this category
- Published to the registry more recently than 58% of the other 1753 servers in this category
- Basic checks equal to or better than 100% of the other 1753 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Quilt safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.6.3) reached the registry 23 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: Spree Commerce: open-source B2B and marketplace ecommerce, Stripe MCP, MCP Cn Commerce
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Stripe MCP
by stripe
Stripe’s official server lets AI view and manage customers, products, payments and invoices. Connect to Stripe’s cloud and sign in with OAuth.
Runs in the cloud★ 2,043MITUpdated 12 months ago
Install
MCP Cn Commerce
by TonyWang-hub
8 read-only MCP platform entries; support is operation-specific; merchant live acceptance pending
Runs on your computer★ 96MITUpdated 28 days ago
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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/cliquilt 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", theirwork 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
- One shared checkout. Model humans, agents, and bots as actors editing one working tree, no worktree per agent.
- Line-level attribution.
commit --minecommits only your lines, even when they share a hunk with another actor's. - Symbol-level claims. Reserve
utils.js#formatPrice, not the whole file, so agents editing different functions never contend. Ten languages via tree-sitter; whole-file claims for the rest. - Collision prevention. A write into code another agent has claimed is denied, with the holder's stated intent, before any bytes change.
- Push-awareness. Claim a symbol that depends on a function another actor is changing, and Quilt warns you at claim time.
- Detect and preserve. If one actor overwrites another's uncommitted lines, Quilt snapshots the victim's version so nothing is silently lost.
Every commit Quilt produces is an ordinary Git commit. It trusts Git and never rewrites it, and all state lives locally under .quilt/. No account, no daemon.
Quickstart
quilt setup # wire Quilt into the repo (capture hooks + optional MCP tools)quilt doctor # confirm it's wired and capture is flowing
That's it. Agents are named automatically: each Claude Code session or MCP connection gets its own id, so parallel agents are told apart with no setup.
4 terminals, one repo
The whole flow, from a git repo to four agents working at once:
cd your-repoquilt setup # once, ~5 seconds claude # terminal 1 claude # terminal 2 claude # terminal 3 claude # terminal 4
Start sessions from a directory that holds several repos? Run quilt setup there instead: it wires the workspace root and every repo inside, and each edit is captured into the repo its file belongs to.
Nothing else. No QUILT_ACTOR, no per-terminal ceremony, nothing to approve: the capture hooks attribute every edit to its session automatically. Watch it live with quilt fleet, and when a session's work is ready, ask it to run quilt commit --mine -m "...". Each commit contains exactly that session's lines, even where two sessions touched the same file. (Claude Code will also offer to enable the optional quilt MCP server for the project; approving it adds the claim/prevention tools, but the hooks protect you either way.)
Watch the fleet
quilt ui opens the same picture in your browser, live: who wrote what (per-actor line counts per file), active claims, who's blocked on whom, and anything that needs a human. Local-only (127.0.0.1), read-only, one command.
Prefer the terminal? quilt fleet --watch is the same view as text.
Set an explicit id when you want one that is stable across sessions:
QUILT_ACTOR=auth-agent claude # this agent's edits are attributed to auth-agentThen each agent commits only its own lines:
quilt status # who owns whatquilt preview --mine # exact patch that would be committed quilt commit --mine -m "fix auth redirect" quilt provenance HEAD # actor, session, files, hunks, tree
Quilt writes that provenance into the Git commit itself, so it survives normal pushes and fresh clones. Prompt correlation stays local in quilt ui; it is not published into Git history.
In a shared shell, make the committer explicit (quilt --as auth-agent commit --mine ...). Quilt refuses a checkout-global session identity when the dirty tree shows another actor. If a deploy provider requires a recognized Git email, set one once while keeping actor names distinct:
quilt config author.email you@example.comquilt fleet shows the whole picture: every actor, their claims, and anything that needs a human. See docs/reference.md for the full command list.
Why not worktrees?
A worktree per agent is the usual answer, and for fully independent tasks it works. But every worktree is another environment to build (another install, another build cache, another dev server) and isolation just moves the collision to merge time. Those costs grow with the number of agents; the whole point of a shared checkout is paying for the environment once.
| Run fewer agents | Worktree per agent | Quilt | |
|---|---|---|---|
| Parallelism | capped low | high | high |
| Setup per agent | none | full install/build/env × N | none (one checkout) |
| See each other's in-flight work | n/a | no | yes |
| Collisions | avoided by hand | surface at merge | prevented, or surfaced live |
| Clean per-agent commits | n/a | after a merge | yes |
Worktrees isolate; they don't coordinate. When agents work the same code at the same time, you usually want them to see each other and account for each other as they go. That is what Quilt does. The two aren't mutually exclusive: worktrees for independent, long-running work, Quilt for agents in the same code at once.
Using it with agents
quilt setup wires the capture hooks and a shared MCP server. On Claude Code the hooks let agents use the built-in Edit and Write tools normally while Quilt records each change's author and blocks a write into code another agent holds, with no protocol for the agent to follow and no setup: each session is named automatically, or carries its own QUILT_ACTOR for a stable id. For other runtimes, the same capture and prevention is available as MCP tools, with each connection named automatically the same way.
See docs/orchestrators.md for Codex, Cursor, Aider, and the difference between process-per-agent and many-agents-in-one-process setups.
Docs
- docs/orchestrators.md: running a fleet of agents.
- docs/reference.md: the full command list, how attribution works, and the
.quilt/state layout. - bench/: the scenario ladder Quilt is tested against, run with and without Quilt on the same metrics.
Telemetry
One anonymous heartbeat per day: quilt version, OS, Node major, random local id. Nothing else unless you opt in at quilt setup, and never code, paths, repo or actor names. quilt telemetry off, QUILT_TELEMETRY=0, or DO_NOT_TRACK=1 silences everything. Details: docs/reference.md.
Contributing
Contributions are welcome. See CONTRIBUTING.md.
License
MIT