EKS Metrics MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_eks_metricsC | Fetch EKS metrics from api_server or cloudwatch. The api_server source calls Kubernetes API server /metrics, equivalent to kubectl get --raw /metrics. CloudWatch is reserved for a future implementation step. |
| list_api_server_metric_namesC | List metric names exposed by Kubernetes API server /metrics. |
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 2 tools
Each tool has a clear, distinct purpose: one fetches actual metrics data, the other lists available metric names. No overlap or ambiguity.
Both tools use consistent snake_case verb_noun pattern: get_eks_metrics and list_api_server_metric_names. Naming is predictable and uniform.
With 2 tools, the server is minimal but well-scoped for its purpose of EKS metrics retrieval. It slightly edges into 'thin' territory but is still reasonable.
Core operations (fetch metrics, list names) are present, but there are notable gaps like filtering, aggregation, or time-range queries. CloudWatch support is missing.