Reads the ticket, finds whether it is a bug or a billing question, and drafts the reply in your own voice.
Built for: The support lead who spends half of every ticket deciding which team it belongs to.
The button opens the checkout, where 8 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.
Search and update tickets and Help Center articles in Zendesk or Freshdesk, end to end.
Check whether the customer's error is a known issue in Sentry before promising them a fix.
Answer a billing question from Stripe's own revenue and subscription data rather than from a guess.
Draft the reply and strip the tells that make a support answer read as machine-written.
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.
Searches, drafts and updates tickets and Help Center articles — the whole loop rather than a read-only view of the queue.
The same ticket work for teams on Freshdesk, over stdio or streamable HTTP.
The half of support that never became a ticket, read with scope-gated access rather than a full mailbox token.
The community channel where problems appear before they are reported, across guilds and with the tools to answer there.
Tells support whether the customer's error is known, how often it happens and which release it started in.
The internal knowledge base the answer is supposed to come from, so replies converge instead of each agent inventing one.
Keeps what was established about a customer across tickets, which is what stops the fourth reply from asking the first question again.
Revenue, subscriptions, refunds and churn from Stripe, so a billing question is answered from the account rather than escalated.
Deliverability and authentication done properly, because the support reply that lands in spam is indistinguishable from the one nobody sent.
The lookup for SSO and identity questions — the exact field, endpoint or environment variable — instead of a guess about somebody else's dashboard.
Generates the payment link when the answer to the ticket is that something needs paying for, without handing the desk a live key.
Removes the patterns that make a reply read as generated, which matters more in support than anywhere else on this site.
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 |
|---|---|---|
| Zendesk | Free | — |
| Freshdesk | Free | — |
| Gmail | from $15/mo | $15/mo |
| Discord | Free | — |
| Sentry | Free | — |
| Notion | Free | — |
| Memory (official) | Free | — |
| Stripe Analytics | Free | — |
| Skills | ||
| email-best-practices | $24 · $2.00/mo over 12 months | $2.00/mo |
| WorkOS | $59 · $4.92/mo over 12 months | $4.92/mo |
| Payment | Free · context cost only | — |
| Stop Slop | $29 · $2.42/mo over 12 months | $2.42/mo |
| Everything above | $15 of servers plus $9.00 of skills, the same in a quiet month and a busy one | $24/mo |
Subscriptions at their monthly plan price; one-off licences spread over 12 months. One-off purchases in this stack total $112 — email-best-practices $24, WorkOS $59, Stop Slop $29 — 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: 7 servers and 1 skill.
Left out, and what goes with it:
Gmail at from $15/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 support-deskNothing in this stack installs from one command today: 12 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 |
|---|---|---|
| Discord | not imported | not recorded |
| Freshdesk | not imported | not recorded |
| Gmail | not imported | not recorded |
| Memory (official) | not imported | not recorded |
| Notion | not imported | not recorded |
| Sentry | not imported | not recorded |
| Stripe Analytics | not imported | not recorded |
| Zendesk | 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 8 members of 8 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.
Where the internal knowledge base is a Confluence space, the answers come from there and support stops keeping a second copy.
Where support arrives by SMS rather than in a community channel, the messaging server replaces the chat one and the reply path stays a single tool.
Written by the maintainer, kept on the page rather than in a support thread.
It cannot issue a refund. The billing member here reads revenue, customers and churn; moving money is outside it, deliberately.
It does not close tickets on its own. Drafts and findings come out; sending a reply to a customer is a person's decision.
It is not the account system. Identity questions are looked up, not changed — a password or an SSO setting is fixed in the tool that owns 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.
One place for the notes, the tasks, the calendar and the inbox, with a memory that survives the session.
Turns a bug report into a reproduction that fails, before anybody writes a line of the fix.
Answers the page: what fired, what changed, what the runbook says, and what to tell the channel.