The keyword and competitive data the brief is argued from, rather than the writer's guess about what people search for.
Content and SEO desk
Researches the keyword, writes the piece, publishes it, and audits what the page actually ships.
Built for: The one-person content team who owns the calendar, the CMS and the search rankings at the same time.
The button opens the checkout, where 7 servers and 6 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.
What your agent can do with this
The reason to buy a stack rather than five listings: each line below needs more than one member connected at the same time.
- 01
Research keywords and search intent through Semrush and Ahrefs before the brief is written rather than after.
- 02
Publish to WordPress or Contentful from the same session that produced the draft.
- 03
Run a technical SEO audit against Search Console history and a first-party crawl, and list what is worth fixing.
- 04
Generate the images a post needs and check that the page is not shipping them four times too large.
The assembly, part by part
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 backlink and ranking side of the same question, for the pieces that are trying to win a term somebody already owns.
Posts, pages, media and custom types over the WordPress REST API — where most of this writing is actually published.
The structured CMS half, for teams whose site is a front end over content models rather than a blog.
Generates the header and inline images from the post's own text, so the visual is not a stock photograph chosen at the last minute.
Audits the published page's images — oversized files, wrong formats, natural against rendered size — which is a ranking factor and a bandwidth bill at once.
Merges Search Console history with a first-party crawl into one technical audit, which is the closest thing here to a full picture.
Turns the raw keyword data into intent and priority, which is the step that decides whether the piece was worth writing.
Repurposes the post into a captioned video, because the same research now has to appear on three surfaces instead of one.
The newsletter and lifecycle sends that carry the piece to the audience already subscribed, written to the same brief.
For content teams sitting on a storefront: the dead and duplicate products that quietly compete with the pages you are trying to rank.
For the long piece that has to stand up to scrutiny — a real survey with real citations, rather than five links found while drafting.
Checks what the published page does in a browser: the rendered markup, the redirect, the thing the CMS preview did not show.
What it costs, and on what assumption
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 |
|---|---|---|
| Semrush | Free | — |
| Ahrefs | Free | — |
| Wordpress | Free | — |
| Contentful | Free | — |
| Imagegen | Free | — |
| Imagedimensions | from $14/mo | $14/mo |
| Seo Audit Console | Free | — |
| Skills | ||
| Keyword Research | $49 · $4.08/mo over 12 months | $4.08/mo |
| Super Video Maker | Free · context cost only | — |
| email-sequences | $59 · $4.92/mo over 12 months | $4.92/mo |
| Shopify Catalog Cleanup | $19 · $1.58/mo over 12 months | $1.58/mo |
| Literature Survey | $39 · $3.25/mo over 12 months | $3.25/mo |
| Browser Automation with playwright-cli | Free · context cost only | — |
| Everything above | $14 of servers plus $14 of skills, the same in a quiet month and a busy one | $28/mo |
Subscriptions at their monthly plan price; one-off licences spread over 12 months. One-off purchases in this stack total $166 — Keyword Research $49, email-sequences $59, Shopify Catalog Cleanup $19, Literature Survey $39 — 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: 6 servers and 2 skills, 50 of the 51 tools.
Left out, and what goes with it:
- Imagedimensions · from $14/moAudits the published page's images — oversized files, wrong formats, natural against rendered size — which is a ranking factor and a bandwidth bill at once.
- Keyword Research · $49Turns the raw keyword data into intent and priority, which is the step that decides whether the piece was worth writing.
- email-sequences · $59The newsletter and lifecycle sends that carry the piece to the audience already subscribed, written to the same brief.
- Shopify Catalog Cleanup · $19For content teams sitting on a storefront: the dead and duplicate products that quietly compete with the pages you are trying to rank.
- Literature Survey · $39For the long piece that has to stand up to scrutiny — a real survey with real citations, rather than five links found while drafting.
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.
Setting it up, in order
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 content-seoNothing in this stack installs from one command today: 13 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.
- 7 members have not declared what credential they need — check each one’s own page before you start.
- What this stack can write is not recorded — 4 members of 7 have no imported tool surface. Section 05 says what is known before you approve anything.
- 7 members can run on your own machine instead of ours, if you would rather they did.
What the whole stack can reach
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 |
|---|---|---|
| Seo Audit Console | imported | 1 |
| Ahrefs | not imported | not recorded |
| Contentful | not imported | not recorded |
| Semrush | not imported | not recorded |
| Wordpress | 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 7 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.
Sensible swaps
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 without an SEO subscription still gets meta tags, robots, sitemaps and keyword basics from the open toolkit, and gives up competitive data to do it.
Same job, different content platform — take the one your site already renders from and drop the other.
Where this stack stops
Written by the maintainer, kept on the page rather than in a support thread.
It cannot rank a page. Everything here shortens the loop between writing and measuring; the ranking still belongs to the search engine.
It does not run your ad spend. This desk is organic — the paid side is a different budget and a different stack.
Nothing here approves publication. A draft goes live because a person said so, and the CMS credentials should reflect that.
Who keeps this current
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.
Stacks that share parts with this one
Browser QA desk
Drives the real interface, keeps the end-to-end suite current, and checks the things a screenshot does not show.
Design-to-code desk
Reads the Figma file, builds the component, and ships the page without redrawing the design in CSS by eye.
Pull-request desk
Reads the branch, runs it in a throwaway sandbox, and leaves the review on the merge request before a human opens it.