Compatible with every major AI agent and IDE
What is the OpenCost (K8s Cost) MCP Server?
Connect your OpenCost instance to any AI agent to gain real-time visibility into your Kubernetes spending and infrastructure efficiency through natural language.
What you can do
- Workload Allocation — Query costs and resources allocated to clusters, nodes, namespaces, controllers, and pods using
get_allocation. - Asset Inspection — Retrieve backing cost data for physical infrastructure like Nodes, Disks, and Load Balancers via
get_assets. - Cloud Billing Integration — Access AWS CUR, Azure Export, and GCP Billing data directly with
get_cloud_costto reconcile K8s costs with provider bills. - Third-Party Costs — Track external service expenses (e.g., Datadog, MongoDB Atlas) using custom cost timeseries and total summary tools.
- Granular Filtering — Aggregate data by labels, annotations, or service levels to understand exactly where your budget is going.
How it works
- Subscribe to this server
- Enter your OpenCost API Base URL
- Start auditing your cloud spend from Claude, Cursor, or any MCP client
Who is this for?
- DevOps & Platform Engineers — Identify expensive namespaces or orphaned resources without manual dashboard diving.
- FinOps Teams — Reconcile internal Kubernetes allocations with external cloud provider billing reports instantly.
- Engineering Managers — Get quick summaries of project-based costs to stay within budget during development cycles.
Built-in capabilities (6)
Query costs and resources allocated to Kubernetes workloads
Retrieve backing cost data broken down by individual assets
Retrieve cloud cost data directly from cloud provider billing reports
g., Datadog, MongoDB Atlas). Get samples of third-party service costs over time steps
Get summary of third-party costs over a window
Change OpenCost log level at runtime
Why Claude Desktop?
Claude Desktop is the definitive way to connect OpenCost (K8s Cost) to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 6 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
OpenCost (K8s Cost) in Claude Desktop
OpenCost (K8s Cost) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect OpenCost (K8s Cost) to Claude Desktop through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for OpenCost (K8s Cost) in Claude Desktop
The OpenCost (K8s Cost) MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 6 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Desktop only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
OpenCost (K8s Cost) for Claude Desktop
Every tool call from Claude Desktop to the OpenCost (K8s Cost) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I see costs grouped by a specific Kubernetes namespace?
Yes. Use the get_allocation tool and set the aggregate parameter to 'namespace'. You can also specify a window like '7d' to see trends over the last week.
Does this server support viewing external cloud provider billing?
Absolutely. The get_cloud_cost tool retrieves data directly from cloud provider billing reports (AWS CUR, Azure Export, GCP Billing) to give you a complete financial picture.
Can I track costs for non-Kubernetes services like Datadog?
Yes, if configured in your OpenCost instance, you can use get_custom_cost_total or get_custom_cost_timeseries to query costs for third-party SaaS and infrastructure services.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.
Explore More MCP Servers
View all →
Collibra
10 toolsEnable your AI agent to manage data assets, domains, and communities via the Collibra Data Intelligence API.

Kustomer
10 toolsManage customer service — list conversations, audit customers, and search timelines.

Cloudflare
25 toolsAI edge infrastructure: manage Workers, KV, D1, R2, routes, and deployments via agents.

Memo Meister
11 toolsCreate and organize smart notes with AI-powered tagging, search, and knowledge connections that make your ideas retrievable.
