Plans the calendar, writes the posts for each network, schedules them and reads what people are saying back.
Built for: The marketer who posts on four networks, answers the replies, and has to report which of it worked.
The button opens the checkout, where the 4 servers and 4 skills are listed one by one. Every member is free, so the checkout lists them and asks for no card.
The reason to buy a stack rather than five listings: each line below needs more than one member connected at the same time.
Plan a month of posts, adapt each one to X, Bluesky and the other networks Postiz connects, and queue them in Postiz.
Search Reddit and X for mentions of the product and summarise what people are asking about.
Reply on Bluesky or X from a draft a person approves, with the X server kept read-only until then.
Pull post analytics and write the monthly report with what to post more and less of.
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 Postiz API — integrations, posts, uploads and analytics across the networks Postiz connects — with writes and deletes switched off until you enable them.
The X API v2 with a policy switch: start in read-only, then allow engagement or publishing when you choose.
Bluesky over the AT Protocol: posts, threads, replies, search, notifications and lists.
Browses subreddits, searches Reddit and reads posts and comments, read-only, for what people say where you do not post.
X post copy and threads written for the network, not a LinkedIn post cut short.
An editorial calendar with cadence, topics and a distribution workflow, so posting is planned rather than remembered.
Anthropic's marketing skill for adapting one message to each platform, audience and length.
Reads channel metrics and says what is working and what to stop — the report after the posting.
Every member is free, so the monthly figure is $0 whatever you do with the stack: nothing here is billed by the call, and only adding a paid member could change it.
| Part | What you are paying for | Monthly, as quoted |
|---|---|---|
| Postiz | Free | — |
| X AI | Free | — |
| Atproto | Free | — |
| Reddit Mcp Buddy | Free | — |
| Skills | ||
| Twitter/X Posts | Free · context cost only | — |
| Content Calendar | Free · context cost only | — |
| Draft Content | Free · context cost only | — |
| Performance Analytics | Free · context cost only | — |
| Everything above | $0 of servers plus $0 of skills, the same in a quiet month and a busy one | $0/mo |
Subscriptions at their monthly plan price; one-off licences spread over 12 months.
Install only these and the bill is nothing: 4 servers and 4 skills, and all 5 tools.
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.
The spend cap is one figure for the whole account, set in your dashboard and checked when an order is placed. On the call path what stops a retry loop is the plan's call allowance and its rate limit, and a refused call is never billed.
The steps below come before the install lines: what to decide and scope before connecting anything, in the order it matters. The lines themselves follow, part by part, for the client you pick.
npx mcprush@latest stack add social-desk writes all 4 servers into Claude Code’s config in one go — or run the lines below one by one. The 4 skills are not included — add them with lines 05–08.
POSTIZ_URL — Base URL of your Postiz instance, e.g. http://localhost:5000 or https://postiz.example.comPOSTIZ_API_KEY — API key from Postiz Settings → Public APISet them where you start Claude Code — export POSTIZ_URL=… in your shell profile on macOS and Linux, setx POSTIZ_URL "…" on Windows, then open a new terminal. Claude Code reads them at start; the config keeps only the names.
# 01 · Postiz
claude mcp add --scope user --env 'POSTIZ_URL=${POSTIZ_URL}' --env 'POSTIZ_API_KEY=${POSTIZ_API_KEY}' --transport stdio postiz-mcp '--' npx -y postiz-mcp
# 02 · X AI
claude mcp add --scope user x-ai-mcp '--' npx -y x-mcp-ai
# 03 · Atproto
claude mcp add --scope user atproto-mcp '--' npx -y atproto-mcp
# 04 · Reddit Mcp Buddy
claude mcp add --scope user reddit-mcp-buddy '--' npx -y reddit-mcp-buddy
# 05 · Twitter/X Posts
npx mcprush@latest skill add kostja94/twitter-x-posts
# 06 · Content Calendar
npx mcprush@latest skill add tonone-ai/content-calendar
# 07 · Draft Content
npx mcprush@latest skill add anthropics/draft-content
# 08 · Performance Analytics
npx mcprush@latest skill add anthropics/performance-analyticsnpx).Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither.Nothing is connected until you approve it in Claude Code. mcprush is not in the path and meters nothing here.
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 |
|---|---|---|
| Atproto | not imported | not recorded |
| Postiz | not imported | not recorded |
| X AI | 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 3 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.
The maintainer lists no alternatives for this stack.
Written by the maintainer, kept on the page rather than in a support thread.
It does not run ads or buy promotion. Paid campaigns stay in the ad platforms.
Reddit is read-only here. The desk reads the conversation; posting there is a person's call and account.
It will not automate engagement farming — mass follows, likes or replies. The servers can do it; your accounts would pay for it.
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.
Tools to inspect code changes, run checks and prepare a pull request review.
Tools to investigate a bug report and work toward a reproducible test case.
Tools to investigate alerts, check recent changes and follow the runbook.