Kubecost MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KUBECOST_BASE_URL | Yes | The base URL of your Kubecost instance | |
| KUBECOST_PASSWORD | No | Password for basic authentication | |
| KUBECOST_USERNAME | No | Username for basic authentication | |
| KUBECOST_API_TOKEN | No | API token for authentication | |
| NODE_TLS_REJECT_UNAUTHORIZED | No | Disables TLS certificate validation for Node.js when connecting to Kubecost instances using self-signed certificates or certificates from private CAs |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_budgetsB | List all budget rules in Kubecost |
| get_budgetC | Get detailed information about a specific budget rule |
| create_budgetC | Create a new budget rule in Kubecost |
| update_budgetC | Update an existing budget rule in Kubecost |
| delete_budgetC | Delete a budget rule from Kubecost |
| get_cost_allocationC | Get cost allocation data from Kubecost |
| get_assetsC | Get asset data from Kubecost |
| health_checkB | Check if Kubecost API is healthy and accessible |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose with no ambiguity. Budget tools (create, delete, get, list, update) are clearly separated from data retrieval tools (get_assets, get_cost_allocation) and the health_check utility. The descriptions reinforce these distinctions, making misselection unlikely.
All tools follow a consistent verb_noun pattern with snake_case throughout. Budget-related tools use consistent verbs (create, delete, get, list, update) paired with 'budget', while other tools maintain the same naming convention (get_assets, get_cost_allocation, health_check). There are no deviations in style.
With 8 tools, this is well-scoped for a Kubecost server. Each tool earns its place by covering budget management (5 tools), data retrieval (2 tools), and health checking (1 tool). This count is neither too thin nor overwhelming for the domain.
The tool set provides complete CRUD coverage for budget rules and includes essential data retrieval and health checks. A minor gap exists in not having tools for other Kubecost features like alerts or recommendations, but core workflows are well-covered and agents can work effectively with what's provided.