Documented
Costory's FinOps agent, in Claude Code
claude mcp add --transport http costory https://app-api.costory.io/mcp, then /mcp → Authenticate
Why use Claude Code for FinOps
Claude Code is already where many engineers ask questions. With Costory's MCP server, those questions can be answered with your real cost data: spend from every provider, normalized and allocated to teams and features, with the deploys and metrics that explain changes.
Set up Costory in Claude Code
Run in your terminal:
Then run /mcp inside Claude Code and select Authenticate to log in with your Costory account.
Full instructions: MCP setup guide.
If something goes wrong in Claude Code
If Claude Code reports that the server “does not support dynamic client registration”, check that the config uses the native HTTP transport (type "http") with the Costory URL.
If you see “Not authenticated”, your session expired: run /mcp and select Authenticate again.
You can also declare Costory in the project .mcp.json so everyone on the repository gets the same server.
Source: the MCP setup guide.
What you can do
Investigate why spend moved, by team, service and environment.
Compare periods and see the deploys, incidents or provider events in the same window.
Create alerts, scheduled Slack reports (for example in #finops) and dashboards from the conversation.
Build and preview Virtual Dimensions to allocate spend when tagging is incomplete.
Example prompts
“Why did our cloud cost go up last week?”
“What does our OpenAI usage cost per feature this month?”
“Alert me if EC2 rises more than 10% vs the trailing 7 days.”
“Send a weekly report of the platform team's spend to #finops.”
FAQ
Is the Costory MCP server free to use with Claude Code?
The MCP server is included in Costory plans (from €250/month, billed annually, 30-day free trial).
Do I need to run anything locally?
No. Costory is a hosted remote MCP server with OAuth. Your client connects directly to https://app-api.costory.io/mcp; no local proxy or Node.js is needed.
Can the assistant change my cloud resources?
No. Costory has no write access to your cloud accounts.
Context layer
Your assistant starts from your Context layer: how cost is allocated, who owns what, which metrics explain it, and what past investigations concluded.
Set up Costory with one prompt
Set up Costory for my company. Create my account, add Costory MCP, connect my cloud/LLM billing export with Terraform, then suggest the first three things to do.
The Costory MCP is hosted and requires a Costory account. The setup prompt creates one for you.
Playbooks
Playbooks you can run with Claude Code
What the Costory agent can watch, investigate and report on for you, with this in the loop.
All playbooks
Costory notices
Every Monday at 9:00, for each team.
Weekly showback per team, posted in each team's Slack channel
Every engineering team gets its own weekly cost report in its own Slack channel, scoped to the services it owns.
See the playbook
Costory notices
Daily, as Datadog usage and the EKS bill refresh.
Dynamic cost reallocation for EKS using Datadog usage
Split shared EKS cluster costs across teams in proportion to what each team's workloads actually use, measured in Datadog.
See the playbook
Costory notices
A service runs well below its capacity for 30 days.
Rightsizing recommendations grounded in real usage
The agent compares what you pay for compute with what services actually use in CloudWatch or Datadog, then recommends instance sizes to the owning team, with the deploy history attached.
See the playbook
Costory notices
Coverage drops, or the steady on-demand baseline grows.
Savings Plans and Reserved Instances coverage review
The agent watches covered versus uncovered spend and utilization, and recommends where additional commitments could make sense as your steady baseline grows.
See the playbook
Costory notices
A feature's model cost per request rises, or a new model ships.
Choose LLM models and routing based on cost per feature
The agent tracks per-model spend for each AI feature across OpenAI, Anthropic, Bedrock and Vertex AI, and recommends where a cheaper model or a routing change could fit.
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
Connect in under 30 minutes. Get your first optimization recommendation the next day.
30-day free trial. Copilot, €250/month, or Copilot Pro, €1,000/month, billed annually.
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