Changelog Update
🎯 What is it?
Dust now supports Costory as a remote MCP (Model Context Protocol) server. This means your Dust agents can connect directly to Costory to query cloud costs, compare spending across periods, and generate reports or alerts — all without leaving Dust.
💡 Why is it useful?
FinOps questions — "What changed in our cloud spend this month?", "Which service drove the cost spike?" — typically require jumping between billing dashboards, pulling exports, and chasing down the right person. With this integration, agents can answer those questions in seconds, directly in Dust. Engineering and Ops teams no longer need to dig through dashboards manually or wait for a FinOps review cycle.
⚙️ How does it work?
Costory is connected to Dust as a remote MCP server, authenticated via OAuth. Once connected, any agent in your workspace can call Costory's tools to fetch, analyze, and compare cloud spending data — and surface that information in reports, alerts, or conversational responses.
✨ Concrete Use Cases
Here's how you could use it:
-
Cloud cost monitoring agent: Ask "What were our top 5 cost drivers last week compared to the week before?" and get an instant, structured breakdown — no dashboard required.
-
Automated cost alerts: Build an agent that runs on a schedule, detects unusual spend variations in Costory, and posts a summary directly to Slack or your incident channel.
📈 Benefits for you
-
FinOps questions get answered in seconds, not hours
-
Engineering and Ops teams stay unblocked — no more chasing billing dashboards
-
Agents can combine Costory data with other sources in Dust (docs, runbooks, Slack threads) to provide richer, more actionable context
🚀 How to access it?
Available now to all workspaces using Costory. To connect:
-
Go to Spaces → Tools in your Dust workspace
-
Click Add Tools and search for Costory
-
Authenticate via OAuth — no feature flag or special configuration needed
Once connected, add Costory tools to any of your agents and start querying cloud spend directly from Dust.