I Built an MCP Server That Lets Claude Control My Kubernetes Cluster

Why I Built This Every DevOps incident I've dealt with follows the same pattern. Something breaks. I open five terminal tabs. I run kubectl, check the AWS console, tail Docker logs, and manually piece together what went wrong — all while the clock is ticking. The tools all exist. They're just completely disconnected from each other. I wanted one interface that could ask a question, reach into all of them simultaneously, and explain what it found. So I built an MCP server that gives Claude Desktop direct access to my real infrastructure. How It Works The server runs locally on my laptop. Claude Desktop launches it on startup and communicates over stdio (standard input/output). When I type a question, Claude reads the 14 registered tool descriptions, decides which ones to call, and sends a JSON request to my server: { "method" : "call_tool" , "params" : { "name" : "get_failing_pods" , "arguments" : { "namespace" : "default" }}} My server executes against real infrastructure and returns s