Writes the migration, proves it on a branch, and says what it will do to the table before it touches the real one.
Built for: Whoever has to add a column to a table that is too large to lock, and would like the rollback written at the same time.
The button opens the checkout, where 4 servers and 5 skills are listed one by one with what each does to the bill — free, already yours, monthly or a one-off licence. Nothing is charged until you confirm it there, in Stripe’s own card frame on that page rather than a redirect, and each paid member keeps its own budget cap.
The reason to buy a stack rather than five listings: each line below needs more than one member connected at the same time.
Open a Neon branch, run the migration there, and throw the branch away when the answer is no.
Read the current schema and row counts against a read-only Postgres connection before proposing an index.
Check the migration against zero-downtime rules — the lock it takes, the backfill it needs, the rollback it must have.
Read a CSV, Parquet or SQLite file with DuckDB when the change starts as a one-off load rather than as a schema edit.
What each part contributes, and why it was picked over the obvious alternative. Prices and permissions are read from the listings, so nothing here can disagree with the catalogue.
The read-only view of the live schema — sizes, indexes, row counts — which is what an honest migration plan is written against.
Neon's own server manages branches and runs migrations on them, so the rehearsal happens on a copy that can be deleted.
Shows which saved questions read the table you are about to change, which is the report that breaks the morning after a rename.
The migration is a merge request like any other, and this is where it lands for review.
The general rules: expand-then-contract, backfill in batches, and a rollback written at the same time as the change.
Index design, partial and partitioned indexes, and EXPLAIN ANALYZE as the proof rather than the intuition.
Django migration rules written for a large storefront — the concrete version of don't lock the table, for teams on that stack.
Reads CSV, Parquet, Excel or SQLite in place, which is how most one-off loads start before they become a schema change.
A worked set of conventions for authoring migrations in a real repository, useful as the template when yours has none written down.
Every member is a subscription or a licence bought once, so the monthly figure is a price rather than an estimate: what moves it is adding or dropping a member, not how hard the stack is worked. The one assumption is that a one-off licence is spread over a year so it can sit in the same column as a subscription.
| Part | What you are paying for | Monthly, as quoted |
|---|---|---|
| Postgres | Free | — |
| Neon (official) | Free | — |
| Metabase | Free | — |
| Gitlab | Free | — |
| Skills | ||
| Database Migration Patterns | Free · context cost only | — |
| Postgresql Indexing | $59 · $4.92/mo over 12 months | $4.92/mo |
| Saleor Migrations | $39 · $3.25/mo over 12 months | $3.25/mo |
| DuckDB Read File | $12 · $1.00/mo over 12 months | $1.00/mo |
| n8n Migration Guidelines | Free · context cost only | — |
| Everything above | $0 of servers plus $9.00 of skills, the same in a quiet month and a busy one | $9.00/mo |
Subscriptions at their monthly plan price; one-off licences spread over 12 months. One-off purchases in this stack total $110 — Postgresql Indexing $59, Saleor Migrations $39, DuckDB Read File $12 — paid once and spread here so they sit in the same column as a subscription. Everything arrives on one mcprush invoice, taken by Stripe from the card on your account, not one per publisher — mcprush.com is the merchant of record and each publisher is paid out of it.
Install only these and the bill is nothing: 4 servers and 2 skills.
Left out, and what goes with it:
Nothing in this stack carries a call allowance, so nothing here can run out before the month does. The bill is decided when you install it, not when you use it.
Budget caps are set per install and enforced at the gateway, so a retry loop is refused at the cap rather than left to run through an allowance overnight.
One step per part, in the order they are useful: connect what the work reads before what it writes, and install the skills that decide how the work is done last. Each step is a command you can read before you run it.
npx mcprush@latest stack add schema-changeNothing in this stack installs from one command today: 9 members are either paid, run from its own source, or a skill with its own command — the steps above name each one. Nothing is connected until you approve it.
Installed together, these tool surfaces add up. It is the first thing a security reviewer asks for, so what has been counted — and what nobody has counted yet — is on the page rather than in a PDF.
| Member | Tool surface | Write tools |
|---|---|---|
| Gitlab | not imported | not recorded |
| Metabase | not imported | not recorded |
| Neon (official) | not imported | not recorded |
| Postgres | not imported | not recorded |
A stack's blast radius is the union of its members, not the worst of them. That union cannot be taken here, because 4 members of 4 have no imported tool surface — so the figure a review asks for is missing rather than low, and a member marked not imported is one nobody has counted rather than one that cannot write.
A stack is a default, not a verdict. These are the substitutions the maintainer would make, and what each one costs or saves.
A team whose Postgres is a Supabase project works against it from Supabase own side, and gives up the disposable branch that made the rehearsal free.
A team without a BI tool still needs somewhere to put the before-and-after counts; the Sheets server takes them, with pivots and charts, at no licence cost.
Written by the maintainer, kept on the page rather than in a support thread.
It cannot run a migration against production. The branch is where this desk works; promoting it is a human action with a human's credentials.
The Postgres member is read-only by design, so it can measure a table and never alter one.
It does not own your deployment order. A migration that must land before the code, or after it, is a release decision this stack can describe but not sequence.
A stack has an owner: whoever keeps it re-checks the combination when a member changes, and the members themselves are published by the people named on each row.
Designs the endpoint, wires the auth and the payment, and reviews the shape before it is public and permanent.
Reviews the code, the identities and the exposure of one service, and writes down what it found rather than a score.
Answers the funnel question with the query it ran, the caveat attached, and the readout already written.