LabscoMCP early access ↗
costory-ioMCP SERVER · OFFICIAL PROJECT

Costory

Ask why last week's cloud bill jumped, against billing data that is already normalised and allocated.

by costory-io ↗Cloud Resources & Infrastructure as Code✓ Official

LABSCO SUMMARY

The allocation happens before the question, not during it.

Feeding raw billing lines into a prompt does not work, and the shared and untagged cost is exactly the part that needs explaining. Costory allocates from real usage metrics first, so the assistant is querying numbers that already add up rather than reasoning its way toward them.

What it is

The FinOps skills that sit on top of Costory's hosted MCP server. Costory normalises AWS, GCP, Azure, Snowflake, Datadog, OpenAI and Anthropic billing into one schema, allocates shared and untagged cost from real usage metrics, and correlates spend with deploy events and incidents.

What you get

  • Orientation — get_context, search, get, suggest_groupby, suggest_usage_metrics and suggest_actions discover the dimensions, dashboards and the right way to slice a question
  • Query — query, list_metrics and list_virtual_dimensions cover cost, usage, metric, formula and budget questions with period-over-period comparison
  • Allocation — create_virtual_dimension_draft, update_virtual_dimension_draft, preview_virtual_dimension_draft, publish_virtual_dimension and virtual_dimension_overlap_matrix build custom cost axes from ordered CEL rules
  • Reporting — create_report, update_report, preview_report_widget, run_report_now, create_dashboard and update_dashboard produce scheduled Slack, Teams and email reports plus dashboards built from chat
  • Alerting and events — create_alert, preview_alert, list_alerts, create_event, update_event
  • Skills that encode the workflow instead of leaving the assistant to rediscover it: query, virtual-dimensions, dashboards, reports and recipes
  • Recipes cover budget-versus-actual dashboards, EC2 spike alerts, prod-versus-R&D splits, untagged coverage, marketplace spend, provider credits, namespace cost, compute drilldowns and period-change explanation

Requirements

Nothing to install: add https://app-api.costory.io/mcp as a custom connector in Claude Desktop, Claude Code, Cursor or VS Code and complete the OAuth login in the browser — no IAM credentials, no Docker, no local server. Clients without native remote MCP can proxy it with mcp-remote. You need a Costory workspace with billing data connected; a 15-day trial is available. Write tools act only inside your own workspace, and query scoping follows the calling user's workspace role.

Setup effort

One command — claude plugin marketplace add costory-io/costory-finops-mcp-skills && claude plugin install costory@costory

See installation options