Kubeadapt MCP
Worked examples
Worked Kubeadapt MCP examples: what to ask Claude, ChatGPT or Cursor about Kubernetes costs, which tools run, what the answer holds, and its limits.
Last updated
Each example takes one common FinOps job and shows what to ask an AI tool connected to Kubeadapt MCP, which Kubeadapt tools it calls, what the answer contains, good follow-up questions, and what it can't do. They work the same in Claude, ChatGPT, Claude Code, Cursor and any other connected AI tool.
Examples
| Example | The job | Main tools |
|---|---|---|
| Review monthly Kubernetes spend | Spend by cluster or namespace, the change, and a month-end estimate | query_costs, get_cost_trend |
| Investigate a cost increase | Why spend went up, which workloads drove it, and what an alert found | compare_costs, get_incident |
| Team chargeback and showback | What each team and department cost, and what no team owns yet | get_team_costs, list_cost_labels |
| Rightsize workloads | Recommended requests and limits, with a YAML patch to review | list_recommendations, get_rightsizing_plan |
| Find idle capacity and node savings | Capacity paid for and not used, empty nodes, spot and ARM what-ifs | get_capacity_overview, get_node_optimization |
| Ask about network cost | Internet egress, cross-zone traffic and who a workload talks to | query_network_costs, get_workload_traffic |
Before you start
- Connect once. Follow Connect your AI tool. Your AI tool signs in with your Kubeadapt account.
- Allow the data each example needs. A connection only gets the tools for the kinds of data you allowed when connecting: Costs and carbon, Savings, Alerts, or Network costs. Each example names the kinds it needs. See Permissions and security.
- You don't name tools. Ask in your own words; the AI tool picks the tools. Naming the cluster, namespace, team and period gives the most precise answer.
What every example has in common
- Read-only. No tool changes anything in Kubeadapt or in your clusters. Rightsizing patches are proposals you review and apply yourself.
- Your view of Kubeadapt. Answers cover the clusters the connection can see, within your own permissions.
- Stated windows. Dates are UTC calendar days. Without dates, most cost tools read the last 30 complete days;
compare_costsreads the last 7, andget_team_coststhe current month to date. - Caveats included. Answers say when a cluster stopped reporting, a price is missing or data is still arriving, instead of showing a misleading number.
- A link back. Most answers include a link that opens the same view in Kubeadapt.
For more questions to start with, see What you can ask. For every tool and its arguments, see the Tools reference.