Costory FinOps MCP

Costory FinOps MCP: the FinOps harness for platform teams, in Claude, Cursor or any MCP client

Costory is built by data engineers. Every bill (AWS, Google Cloud, Azure, Oracle Cloud, Snowflake, Databricks, Datadog, OpenAI, Anthropic and more) is normalized into one model on BigQuery and joined with your context: telemetry, CI, dbt, product events and business metrics. One model for every provider is what keeps the price flat. See supported providers.

How Costory works, in five ideas: https://docs.costory.io/get-started/concepts

One person curious about cost? Ask Claude and DIY. A whole org that needs the same number? Use Costory.

Why platform teams use it

1. Allocation that holds in a large org. Enrichments are YAML lookup files you keep in git: one stable key, such as a component, fills team, cost center or product columns. Entries are dated, so a reorg never rewrites last quarter, and shared costs can be split by real usage. Reviewed in a PR, published through the API or Terraform.
2. Everything included, at a flat price. Unlimited users and data sources, every skill and the MCP in every plan. Starter from $300/month. Pay more only when you use more. Never a % of your bill. App usage (queries, reports, alerts) and Ask Costory have a fair use. You see it in the app, get a warning at 70%, and nothing is ever cut off. Starter fits 80% of our customers. Fair use per plan: Standard (Starter), 3x (Team), 6x (Business), 10x+ (Custom). Above the limit: slowed, never cut off. Agents connected through the MCP use no Ask Costory credits. 30-day free trial, no credit card.
3. The FinOps harness. An agent with skills, your company context and loops to monitor, investigate, report and recommend. The hosted MCP server and the skills in this repo let Claude, Cursor or any MCP client explain a cost change, build a report or create an alert. It also answers in Slack. Loops are Scouts: assign one to your reports and alerts, give it instructions in plain text, and it adds the cause, the owner and the next step to every delivery. Costory runs it.
4. Open by default. Public API, export of allocated data to BigQuery and other destinations, skills published here as markdown. No lock-in.

Moving from another FinOps tool? Costory reads billing exports directly from each provider, read-only, so it runs alongside your current tool for the 30-day trial. Enrichment rules are YAML in git: reviewed in a PR, managed with Terraform. Starter from $300/month, never a % of your bill. See moving from another tool.

Asked to build one? One engineer with Claude and a billing API gets a useful dashboard in an afternoon. That part is free, and we recommend it. A tool the whole team can trust takes weeks, then maintenance forever. We built that part. You keep control: YAML, formulas, the API, Terraform, and export to your own warehouse. See build vs buy.

What Costory does not do

• It reads billing and usage exports and never gets write access to your cloud accounts. MCP actions create Costory objects only: virtual dimensions, alerts, reports, dashboards and events.
• It recommends optimizations, for example rightsize an instance group or partition a table. Your coding agent or your team implements them. It never changes your code or infrastructure, never applies automated rightsizing, and never buys Reserved Instances or Savings Plans.
• It does not promise a savings percentage. Recommendations come with an impact estimate from your own usage.
• It never charges a percentage of your bill.

Domain auto-join on every plan; enterprise SSO from Team. See identity and access.

Customers include Pennylane, Alan, Deezer, Delivery Hero and Voodoo.

This repository is the open part: the agent skills and plugin packaging (Claude Code, Codex, Cursor) that teach an agent how to run FinOps workflows on top of the Costory MCP tools.

• Concepts: docs.costory.io/get-started/concepts
• Endpoint: https://app-api.costory.io/mcp (streamable HTTP)
• Auth: OAuth 2.1 in the browser. No IAM credentials, no Docker, no local server
• Docs: docs.costory.io/features/mcp
• Registry name: io.costory/finops on the official MCP Registry

What engineers ask it

• "Why did our AWS bill jump last week? Which deploys line up with it?"
• "Break down Kubernetes cost by namespace and team for the payments cluster."
• "What is our total AI spend across OpenAI, Anthropic, and Bedrock this month, by team and model?"
• "Split our shared Cloud SQL cost across teams by usage and publish it as a dimension."
• "What is our cloud cost per active user, this month vs last month?"
• "Create an alert if daily BigQuery cost goes above $2,000 and post it to our #finops Slack channel."
• "Send the top 5 cost movers to Slack every Monday."

Connect the MCP

One click adds https://app-api.costory.io/mcp to VS Code or Cursor; the OAuth login opens in the browser on first use. Cursor deeplink, if you prefer to paste it: cursor://anysphere.cursor-deeplink/mcp/install?name=costory&config=eyJ1cmwiOiJodHRwczovL2FwcC1hcGkuY29zdG9yeS5pby9tY3AifQ%3D%3D

You need a Costory workspace with billing data connected. Starter from $300/month, flat; 30-day free trial.

Claude Desktop / Claude Code / Cursor / VS Code: add a custom connector pointing at https://app-api.costory.io/mcp, then complete the OAuth login in the browser window that opens. Per-client walkthroughs with screenshots are in the MCP docs.

This repo ships an .mcp.json you can copy:

{

"mcpServers": { "costory": { "type": "http", "url": "https://app-api.costory.io/mcp", "oauth": { "callbackPort": 8080 } } } }

Claude Desktop (developer config, claude_desktop_config.json), see alternative JSON config:

{

"mcpServers": { "costory": { "url": "https://app-api.costory.io/mcp" } } }

VS Code (.vscode/mcp.json):

{

"servers": { "costory": { "type": "http", "url": "https://app-api.costory.io/mcp" } } }

First prompt

Try "Use Costory to show my top cost drivers last month". The agent calls get_context, then query.

If your account has access to several organizations, get_context without a slug returns "Multiple organizations" with the list of slugs. The agent should call list_organizations (or read that list), ask which org to use, and pass that slug to get_context and the following tools. You can also name it upfront: "Use Costory org acme and show my top cost drivers last month".

MCP tools reference

The server exposes tools in five groups. Names and payloads are versioned; the API reference is the source of truth.

Write tools act only inside your Costory workspace. Query scoping follows the calling user's workspace role.

FinOps skills

Skills are the workflow layer: each one encodes how to sequence the tools above for a class of question, so the assistant does not have to rediscover it.

Recipes currently cover BigQuery warehouse routing, GCP spend-based CUDs, budget-vs-actual dashboards, EC2 spike alerts, prod-vs-R&D splits, untagged coverage, marketplace spend, provider credits, namespace cost, compute drilldowns, and period-change explanation. See plugins/costory/skills/recipes/.

Cursor Marketplace packaging

This repo also ships a Cursor plugin layout next to the Claude Code marketplace:

• .cursor-plugin/marketplace.json — multi-plugin marketplace manif