kubernetes-mcp-server

Model Context Protocol (MCP) server for Kubernetes and OpenShift

Runs with mockssource: GitHubGoApache-2.0commit f4a39b17ca4c

Go, Apache-2.0 licensed. The project labels itself: containers, context, kubernetes, kubernetes mcp, mcp, model, modelcontextprotocol and openshift.

kubernetes-mcp-server runs, with stand-ins for the services it depends on. An Argusic agent installed it in 20 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Go 1.26.4 toolchain installed, the 143MB binary builds cleanly, all 39 test packages (pkg, internal, cmd) pass, and the server binary responds to --version (0.0.0) and --help.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.07 (measured)
recorded runs
2
last tested
stars
2,265
forks
491
open issues
146
watchers
13
size
18 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing kubernetes-mcp-server, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Go binary not found in container PATH3 minutes
  • IPv6 disabled in container causes net.DialTCP('tcp',...) to fail with 'cannot assign requested address' in HTTP tests2 minutes
Install time
20 minutes
Cold machine to finish
15 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
go test -count=1 ./pkg/... ./internal/... ./cmd/... exited 0, 39 packages pass; ./kubernetes-mcp-server --version prints '0.0.0'; --help prints usage
Model tokens used
89,480
Exact commit tested
f4a39b17ca4c
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Behaviour against real services
this run was verified against stand-in services only

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

        return nil
      }
    }
    time.Sleep(50 * time.Millisecond)
  }
  if err != nil {
    return err
  }
  return fmt.Errorf("healthz endpoint returned 404 after retries")
}
tokens used
89,480

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed Apache-2.0, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Took 20 minutes to install, slower than the median of the 3 comparable projects Argusic has measured.

Of the 4 containers projects Argusic has installed and timed, kubernetes-mcp-server was the 3rd fastest to reach a running state, and 2 of 4 reached one at all.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs with mocks92.000.07
Argusic Runner1/3Runs with mocks92.000.18

Topics (from GitHub)

containerscontextkuberneteskubernetes-mcpmcpmodelmodelcontextprotocolopenshiftprotocol

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/kubernetes-mcp-server.svg)](https://argusic.com/subject/kubernetes-mcp-server)

Questions

Does kubernetes-mcp-server run?
kubernetes-mcp-server runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 20 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test kubernetes-mcp-server?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit f4a39b17ca4c. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test kubernetes-mcp-server?
The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does kubernetes-mcp-server take to install?
20 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does kubernetes-mcp-server need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing kubernetes-mcp-server?
2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does kubernetes-mcp-server compare with the alternatives?
Of the 4 containers projects Argusic has installed and timed, kubernetes-mcp-server was the 3rd fastest to reach a running state, and 2 of 4 reached one at all.
Where is the evidence for kubernetes-mcp-server?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion