Drives the real interface, keeps the end-to-end suite current, and checks the things a screenshot does not show.
Built for: The team whose test suite is three releases behind the interface it is supposed to be testing.
The button opens the checkout, where 5 servers and 4 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.
Walk a user flow in a real browser and report where it stops, with the screenshot and the console attached.
Write and maintain versioned Playwright specs, and update the ones that a UI change has just invalidated.
Audit the accessibility tree of a page and list what a screen reader will and will not find.
Catch the images shipped at four times their rendered size, which is the cheapest performance bug there is.
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.
Scripted browser automation for the flows you already know the steps of — the backbone of a regression pass.
For the exploratory half: an agent that finds its own way through a page you have not scripted yet.
Accessibility analysis of the page as rendered, so the audit is about the live DOM rather than about the components in the repository.
Audits every image on a page — natural against rendered size, formats, oversized files — which is a whole class of defect nobody files by hand.
Where the specs live and where the failures get reported; a QA desk with no way back into the repository just produces screenshots.
Authors and maintains versioned Playwright specs in TypeScript, which is the difference between a suite and a folder of scripts.
The interactive half — driving a local application, verifying behaviour, capturing what happened when it broke.
Captures the full DevTools-protocol trace and bisects it, for the failure that only happens in the run you were not watching.
Reads what changed in the interface and finds the tests that change with it, which is the work that otherwise never gets done.
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 |
|---|---|---|
| Puppeteer | Free | — |
| Browser Use | Free | — |
| A11y Tools | Free | — |
| Imagedimensions | from $14/mo | $14/mo |
| Gitlab | Free | — |
| Skills | ||
| Playwright E2E Testing | Free · context cost only | — |
| Web Application Testing | Free · context cost only | — |
| Browser Trace | Free · context cost only | — |
| UI4 Convert Tests | $15 · $1.25/mo over 12 months | $1.25/mo |
| Everything above | $14 of servers plus $1.00 of skills, the same in a quiet month and a busy one | $15/mo |
Subscriptions at their monthly plan price; one-off licences spread over 12 months. One-off purchases in this stack total $15 — UI4 Convert Tests $15 — 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 3 skills, 0 of the 1 tools.
Left out, and what goes with it:
Imagedimensions at from $14/mo. Each of those plans states the calls it includes in a month, and running past one never arrives as a larger invoice: the gateway refuses the call over the allowance and returns an MCP error naming the plan. The figure above is what the stack costs in a busy month as well as a quiet one — what a heavy month changes is which plan you need, not what this one bills.
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 browser-qaNothing 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 |
|---|---|---|
| A11y Tools | not imported | not recorded |
| Browser Use | not imported | not recorded |
| Gitlab | not imported | not recorded |
| Puppeteer | 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 5 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.
When the work is inspecting a page's own devtools rather than clicking through it, the Brave DevTools server is the closer fit.
A team that wants security, performance and accessibility from one scan rather than accessibility alone takes the broader scanner and reads less detail on each.
Written by the maintainer, kept on the page rather than in a support thread.
It cannot certify accessibility. The audit finds machine-checkable failures; the rest of WCAG needs a person and an assistive technology.
It does not run your CI. Specs are authored and debugged here; scheduling them is the pipeline's job.
Anything behind a CAPTCHA or a real payment stops the desk. That is the boundary of automation, not a configuration to change.
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.
Reads the branch, runs it in a throwaway sandbox, and leaves the review on the merge request before a human opens it.
Turns a bug report into a reproduction that fails, before anybody writes a line of the fix.
Writes the migration, proves it on a branch, and says what it will do to the table before it touches the real one.