Costory MCP Now Available in Dust

🎯 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.

⚙️ 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.

✨ Concrete Use Cases

Cloud cost monitoring: Ask "What were our top 5 cost drivers last week compared to the week before?" and get an instant, structured breakdown.
Automated cost alerts: Build an agent that runs on a schedule, detects unusual spend variations in Costory, and posts a summary directly to Slack.

📈 Benefits for you

FinOps questions get answered in seconds, not hours
Engineering and Ops teams stay unblocked
Agents can combine Costory data with other sources in Dust

🚀 How to access it?

Go to Spaces → Tools, click Add Tools, search for Costory, and authenticate via OAuth. Once connected, add Costory tools to any of your agents.