How to connect Cursor to your Kubernetes costs

What you can ask Cursor about Kubernetes

• “What does each namespace cost per week on our EKS clusters?”

• “What is our Kubernetes waste ratio by node pool?”

• “Schedule a weekly report of Kubernetes cost per namespace.”

• “Which team owns most of this month's increase?”

• “Set up a weekly Slack report of this spend for #finops.”

What Cursor sees

Costory ingests Kubernetes cost through EKS natively (AWS Split Cost Allocation with Kubernetes labels, no agent, or AWS-managed usage metrics), GKE natively (GKE cost allocation labels, no agent), and AKS or other clusters through a Kubecost or OpenCost export, normalizes it into one cost model alongside your other providers, and allocates it with cluster, namespace, label, team; idle/waste ratio per node pool. Through the MCP server, Cursor can query that allocated cost, compare periods, look up deploys and other events in the same window, and create alerts, reports and dashboards in Costory. It has no write access to your cloud accounts.

Good to know for this setup

• Cursor reads Costory from its MCP settings: a server named costory with type "http" and the URL https://app-api.costory.io/mcp.

• Cluster cost is shared; namespace allocation needs usage metrics, not just node tags.

Set up in about 30 minutes

1. Connect Kubernetes to Costory. Follow the Kubernetes setup guide in the docs.

2. Map spend to owners. Use Virtual Dimensions to group accounts, projects, labels and tags into teams, products and environments, even where tagging is incomplete.

3. Add Costory to Cursor.

Add Costory to your Cursor MCP settings (mcp.json):

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

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

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

The first call opens a browser window to log in with your Costory account.

Full client instructions: MCP setup guide.

Good to know

Cluster cost is shared; namespace allocation needs usage metrics, not just node tags.

Kubernetes tools compared

Based on each tool's public documentation; check current docs before deciding.

FAQ

Does Cursor get write access to my Kubernetes account?

No. Costory reads billing data you export to it. MCP actions create Costory objects (alerts, reports, dashboards, events) and never change your cloud resources.

What Kubernetes permissions does Costory need?

Read access to billing data only. The exact permissions are listed in the Kubernetes setup guide.

Where is the data stored?

Costory stores and processes data in the EU.

How much does it cost?

Plans start at €250/month (up to €10M annual cloud spend), billed annually, with a 30-day free trial. See pricing.