k8s-ops-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_podsA | Lists all pods in a namespace with their name, status, restart count, age, and node. Use this as a first step to get an overview of what is running and spot any pods in Error, CrashLoopBackOff, or Pending state. |
| get_pod_statusA | Returns the detailed status of a single pod: phase, readiness, restart count, last termination reason (e.g. OOMKilled, Error), container states, and pod conditions. Use this to dig into why a specific pod is unhealthy. |
| get_pod_logsA | Fetches logs from a specific pod. Set previous=true to get logs from the pod's last run before a crash — essential for diagnosing CrashLoopBackOff or OOMKilled pods. Use tailLines to limit output to the most recent N lines. |
| get_recent_eventsA | Returns Kubernetes events (Warning and Normal) for a namespace or specific pod, sorted by most recent. Events often reveal the root cause of failures: OOMKilled, FailedScheduling, ImagePullBackOff, Liveness probe failures, etc. |
| get_resource_usageA | Returns real-time CPU and memory usage for pods, compared against their resource requests and limits. Requires metrics-server to be running in the cluster (enable via: minikube addons enable metrics-server). Use to identify pods that are throttled, near their memory limit, or OOMKill candidates. |
| get_deployment_statusA | Returns rollout status for a Deployment: desired vs ready vs available replicas, whether the rollout is complete, container images in use, and any degraded conditions. Use to check if a deployment rolled out successfully or is stuck. |
| scale_deploymentA | WRITE ACTION — This modifies cluster state. Scales a Deployment to the specified number of replicas. Always confirm with the user before calling this. Use dryRun=true (default) to preview the change without executing it. |
| restart_podA | WRITE ACTION — This modifies cluster state. Deletes the specified pod, which triggers automatic recreation if the pod is managed by a Deployment or ReplicaSet. Always confirm with the user before calling this. Use dryRun=true (default) to preview the action without executing it. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/harish235/k8s-ops-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server