Kubernetes Read Only 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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_podsA | List all pods in a namespace or across all namespaces |
| list_deploymentsB | List all deployments in a specified namespace |
| get_pod_logsC | Get logs from a pod in a specified namespace |
| list_servicesA | List all services in a namespace or across all namespaces |
| list_namespacesA | List all namespaces in the cluster |
| get_eventsB | Get Kubernetes events from the cluster for a specific namespace or all namespaces |
| get_logsB | Get logs from pods, deployments, jobs, or resources matching a label selector |
| list_nodesA | List all nodes in the cluster |
| list_resourceA | List resources of any kind (including CRDs) via the dynamic client. GET/LIST only; never mutates. |
| get_resourceA | Get a single resource of any kind (including CRDs) by name via the dynamic client. GET only; never mutates. |
| list_api_resourcesA | Discover which resource kinds (including CRDs) the cluster exposes and can be listed. Read-only discovery. |
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 11 tools
Most tools have distinct purposes, but get_logs and get_pod_logs have overlapping functionality; however, their descriptions clarify that get_logs is for broader resource types while get_pod_logs targets a specific pod, reducing ambiguity.
All tool names follow a consistent verb_noun pattern with underscores (e.g., get_events, list_pods), making the set predictable and easy to navigate.
With 11 tools, the server is well-scoped for a read-only Kubernetes interface, covering essential resources and operations without unnecessary bloat or omissions.
The set includes generic get_resource and list_resource for CRDs, plus specific tools for common resources, logs, events, and API discovery, providing comprehensive read-only coverage without obvious gaps.