mcp-server-kubernetes
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_podsC | List pods in a namespace |
| list_deploymentsC | List deployments in a namespace |
| list_servicesB | List services in a namespace |
| list_namespacesB | List all namespaces |
| create_podC | Create a new Kubernetes pod |
| create_deploymentC | Create a new Kubernetes deployment |
| delete_podC | Delete a Kubernetes pod |
| describe_podB | Describe a Kubernetes pod (read details like status, containers, etc.) |
| cleanupC | Cleanup all managed resources |
| list_nodesB | List all nodes in the cluster |
| get_logsC | Get logs from pods, deployments, jobs, or resources matching a label selector |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Kubernetes Pods | List of pods in the default namespace |
| Kubernetes Deployments | List of deployments in the default namespace |
| Kubernetes Services | List of services in the default namespace |
| Kubernetes Namespaces | List of all namespaces |
| Kubernetes Nodes | List of all nodes in the cluster |
TDQS
Scored across 11 tools
Most tools target a clearly distinct resource and action (list_pods vs list_deployments vs describe_pod vs get_logs). The only mild overlaps are `cleanup` versus `delete_pod` and `get_logs` being much broader than the pod-specific read tools, but descriptions help distinguish them.
The set follows a consistent snake_case verb_noun pattern such as list_pods, create_deployment, delete_pod, and describe_pod. `cleanup` is the only noticeable deviation as a verb-only name.
Eleven tools is well-scoped for a Kubernetes MCP server, covering common read and write operations without feeling bloated. Each listed tool has a plausible place in typical cluster workflows.
Read coverage is decent for pods, deployments, services, namespaces, and nodes, but write coverage is thin: deployments and services have no delete/update/scale operations, and pods lack update/exec. These gaps would likely force agents to fall back to raw kubectl or fail on common lifecycle tasks.