list_resourcesLABSCO SUMMARY
Cluster triage in conversation, with one call that writes.
Listing, describing and reading logs cover the debugging loop and change nothing, which is what makes this attachable to a live cluster. The exception is the rolling restart, which does act on a deployment — worth knowing before you point it at production.
What it is
A Go MCP server for Kubernetes inspection. It reads through your existing kubeconfig, works with any Custom Resource Definition in the cluster, and finds resources by API-group substring — flux for FluxCD, argo for ArgoCD.
What you get
- Resources of any kind listed and filtered, custom resources included
- A named resource described in detail
- Pod logs retrieved, with filtering
- Discovery by API-group substring, so the exact group name is not needed
- A rolling restart of a deployment
Requirements
A kubeconfig with read permission on whatever you want to inspect — it picks up ~/.kube/config by default, or the path in KUBECONFIG. Install with go install, or build from source with Go 1.24 or later.
Setup effort
One command — go install github.com/k4mrul/kubernetes-mcp@latest
USE CASES
01
Working out why a pod will not come up
List what is there, describe the one that is failing, then read its logs — three calls in one thread.
02
Reading logs without switching to a terminal
Pull the pod log with filtering, in the conversation where you are already discussing the incident.
03
Finding the custom resources an operator installed
Search by API-group substring when you do not remember the full group name, then describe what comes back.
04
Kicking a deployment that has wedged
Roll it and let the pods come back, without leaving the conversation for a shell.
05
Getting your bearings in an unfamiliar cluster
Walk the resource kinds and describe the ones that look load-bearing, before you touch anything.
4 tools
Listed in project docs. Your client may show a different list.
describe_resourceget_pod_logsrollout_restartBEFORE YOU INSTALL
What to know first
Tools you get
4 tools named in the project's documentation.
Requires
- Go 1.24 or later
- A kubeconfig with access to your Kubernetes cluster (~/.kube/config by default, or the path in KUBECONFIG)
INSTALLATION
Connect your client
The block needs a path only you can supply — the full path to the binary the install command creates. Everything else in it is the project's own.
Server setup
Configuration file
JSON
{
"mcpServers": {
"kubernetes": {
"command": "<YOUR_PATH_TO_KUBERNETES_MCP>"
}
}
}In the Config file block, <YOUR_PATH_TO_KUBERNETES_MCP> is the full path to the binary: go install puts it at $GOPATH/bin/kubernetes-mcp, or $HOME/go/bin/kubernetes-mcp if GOPATH is not set. It reads ~/.kube/config by default; to use another kubeconfig, add a KUBECONFIG entry under env.
go install
TERMINAL
go install github.com/k4mrul/kubernetes-mcp@latest
