Cost context in your terminal with Claude Code
Connect the Costory MCP to Claude Code so the agent checks what a service costs, how it changed and who owns it before you ship a change.
Runs in
Claude Code · Cursor · VS Code
First optimization recommendation
The next day
ROI
Pays for itself with the first recommendation you act on
Claude Code
>
What does the service in this repository cost per month by environment, and how did that change over the last 90 days?
⎿
… +24 lines (ctrl+o to expand)
⎿
… +16 lines (ctrl+o to expand)
●
search-indexer costs €6,400/month: prod €5,100, staging €900, dev €400. Up 21% in 90 days, mostly in prod since replicas went from 6 to 9 on Aug 20.
●
I can save this query as a view, so the team can follow search-indexer cost by environment. Should I save it?
>
Yes, save it as a view.
●
View saved. You can open it in Costory.
>
Try "write a test for main.py"
? for shortcuts
You decide
The developer weighs cost before merging.
Playbook
What the agent does
From what Costory notices to what you decide. Costory suggests the next step in conversation, and you decide whether to go ahead.
Costory notices
A developer is about to change a service.
Costory investigates
01
Add the server
claude mcp add --transport http costory https://app-api.costory.io/mcp
02
Authenticate
OAuth with your Costory account.
03
Ask while you work
The cost of the service you're changing, by environment.
04
Use skills
FinOps skills add guided workflows.
Costory suggests
I can save this query as a view, so the team can follow search-indexer cost by environment. Should I save it?
Where you see it
Claude Code
You decide
The developer weighs cost before merging.
Why it matters
Developers rarely open the FinOps dashboard. If cost is one question away in the tool they already use, they check it.
Who it’s for
Developers, platform engineers
Where it runs
Claude Code · Cursor · VS Code
What you get
What lands in front of your team
Cost in the terminal
No context switch.
Owner-aware
Answers come with team and environment.
Guided skills
Ready-made workflows for common tasks.
Sources and assistants
What it connects
Data sources
Example prompts
Or drive it yourself
Check
What does the service in this repository cost per month by environment, and how did that change over the last 90 days?
Before a change
This change doubles the worker replicas. What does the worker deployment cost today?
FAQ
Questions about this playbook
Which agents and assistants work with Costory?
Claude, Claude Code, Cursor, VS Code with GitHub Copilot and Dust connect to the hosted Costory MCP server with OAuth.
How long does this playbook take to set up?
Connecting your billing data and the Costory MCP takes under 30 minutes with Terraform or CloudFormation. The playbook itself takes minutes: pick the scope, the trigger and the Slack channel. The first billing data lands the next day, and the agent starts from there.
Can we adjust what the agent does?
Yes. You choose the trigger, the scope (team, service, environment), the channel and the format, and you can pause or change it at any time.
Does Costory change anything in our cloud accounts?
No. Costory reads billing exports and the metrics you connect, and has no write access to your cloud. Actions it takes create Costory objects only: alerts, reports, dashboards and events. Your team stays in control of every change.
Step-by-step guide in the Costory docs
Related playbooks
Run these alongside it
Costory notices
A deploy is followed by a cost change on the same service.
Cost impact of every deploy, from GitHub events
Capture deploys, PR merges and releases from GitHub or your CI/CD pipeline, and see which ones changed cost.
See the playbook
Costory notices
Monthly, or when a team's AI coding spend jumps.
Cursor and Claude Code spend per developer
Track AI coding tool spend per user and per model, from Cursor and the Anthropic Claude Code connector, next to the rest of your cloud.
See the playbook
Costory notices
Spend on a team, service or account deviates from its baseline.
Investigate a cost spike and find the deploy behind it
When spend moves, the agent finds the deploy, team and service behind it, checks incidents and provider events from the same window, and posts the likely cause.
See the playbook
Put this playbook on call
Included in every plan, from €250/month. 30-day free trial: connect in under 30 minutes, get your first optimization recommendation the next day.
First optimization recommendation
The next day
ROI
Pays for itself with the first recommendation you act on
Setup
About 30 minutes
Data residency
EU
Access
Read-only on your cloud