Answers where the cloud bill went, prices a change before it ships, and turns the waste it finds into a list somebody can act on.
Built for: The engineer asked by finance why the bill went up, who has the console open and no time to learn another cost tool.
The button opens the checkout, where the 5 servers and 3 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.
Break last month's spend down by service, account and region, and point at the line that grew.
Price a proposed change before it is applied — an AWS calculator estimate with a link, or a like-for-like comparison across four clouds.
Run the standard FOCUS analyses over your billing export and keep the SQL that produced each number.
Turn the waste it finds into a spreadsheet of rightsizing and reservation candidates with the saving next to each.
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.
A local-first FinOps server: spend by service, account and region across AWS, Azure and GCP, and a cost preflight for a proposed change. Credentials stay on your machine.
Queries a FOCUS billing export with DuckDB, with predefined analyses — so the numbers come from your own bill, in the open billing format the major clouds export.
Builds an AWS Pricing Calculator estimate and returns a shareable calculator link, which is what a proposal is checked against.
Compares compute, storage, egress and managed Kubernetes prices across AWS, Azure, GCP and OCI, and says how fresh its price data is.
FinOps reference material and waste playbooks served as tools, for the question after "how much" — what to do about it.
Rightsizing, tagging, reservations and cost governance across clouds, as a procedure rather than a list of tips.
AWS-specific workflows: unused resources, Reserved Instance and Spot opportunities, storage and network costs, anomalies.
Anthropic's spreadsheet skill, for the workbook the finance team actually reads — with formulas, not pasted numbers.
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 |
|---|---|---|
| Nable | Free | — |
| Focus | Free | — |
| Aws Calculator | Free | — |
| Cloud Cost | Free | — |
| Cloud FinOps Skill & | Free | — |
| Skills | ||
| Cloud Cost Optimization | Free · context cost only | — |
| AWS Cost Optimization & FinOps | Free · context cost only | — |
| XLSX creation, editing, and analysis | 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: 5 servers and 3 skills, and all 252 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 cloud-cost writes all 5 servers into Claude Code’s config in one go — or run the lines below one by one. The 3 skills are not included — add them with lines 06–08.
# 01 · Nable
claude mcp add --scope user nable-mcp '--' uvx finops-mcp
# 02 · Focus
claude mcp add --scope user focus-mcp '--' uvx focus-mcp
# 03 · Aws Calculator
claude mcp add --scope user aws-calculator-mcp '--' npx -y aws-calculator-mcp
# 04 · Cloud Cost
claude mcp add --scope user cloud-cost-mcp '--' npx -y cloud-cost-mcp
# 05 · Cloud FinOps Skill &
claude mcp add --scope user cloud-finops-skill-mcp '--' uvx cloud-finops-mcp
# 06 · Cloud Cost Optimization
npx mcprush@latest skill add wshobson/cloud-cost-optimization
# 07 · AWS Cost Optimization & FinOps
npx mcprush@latest skill add ahmedasmar/aws-cost-optimization-finops
# 08 · XLSX creation, editing, and analysis
npx mcprush@latest skill add anthropics/xlsx-creation-editing-and-analysisnpx).uvx, docs.astral.sh/uv).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 | Share of the write surface | Write tools |
|---|---|---|
| Nable | 39 | |
| Aws Calculator | 4 | |
| Focus | 1 |
A stack's blast radius is the union of its members, not the worst of them. The 44 write-capable tools are the ones worth an argument in a review; the 208 read-only ones are worth a glance at what they can read.
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 change anything in your accounts. Stopping an instance or buying a reservation is a decision made in the console by someone with that authority.
List prices are not your prices. Discounts, credits and private pricing appear only in your own bill, which is why the FOCUS export is here.
Cost data arrives late — billing exports lag by hours to days — so this desk explains last week well and this morning poorly.
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.