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 28 minutes, hitting 3 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. One attempt is 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.18: 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?

28 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?

3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.

Where is the evidence for kubernetes-mcp-server?

The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

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 28 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Go 1.26.4 installed, kubernetes-mcp-server binary built (102MB), all 39 test packages pass, binary runs and prints help/version, runtime requires a Kubernetes kubeconfig
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.18 (measured)
recorded runs: 1
last tested: 2026-10-04
stars: 2,142
forks: 447
open issues: 114
watchers: 13
size: 13 MB
created: 2025-02-11
last push: 2026-10-02

Subject data from GitHub, linked at the top of this page, refreshed 2026-10-04. 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.

3 test suites failing: pkg/http, pkg/kubernetes-mcp-server/cmd (TestHTTPSIGHUP) - all failed with 'dial tcp [::]:port: connect: cannot assign requested address' because IPv6 is disabled in container but test helpers defaulted to IPv65 minutes
No Go compiler found in container2 minutes
make build failed at lint step: 'parallel golangci-lint is running' due to stale process from earlier run2 minutes

Install time: 28 minutes
Cold machine to finish: 29 minutes
Errors hit and fixed: 3 hit, 3 fixed with no human help
How the result was proved: go test -count=1 -v ./... exit 0, 39 test packages passed, 0 failures. Binary at kubernetes-mcp-server (102MB) responds to --help and --version, fails at runtime expectedly with 'no current-context is set' since no kubeconfig is configured in this container
Model tokens used: 109,389
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

The end of the recording

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

-rwxrwxr-x 1 runner runner 102315200 Oct  4 14:39 kubernetes-mcp-server
/bin/sh: 1: file: not found
exec
/bin/sh -lc 'cd /work/repo && export HOME=/home/runner && export PATH=/tmp/go/bin:$HOME/.local/bin:…
 succeeded in 56979ms:
ok    github.com/containers/kubernetes-mcp-server/pkg/toolsets/tekton  0.014s
?     github.com/containers/kubernetes-mcp-server/pkg/version  [no test files]
?     github.com/containers/kubernetes-mcp-server/test/e2e  [no test files]
All tests pass on the final run too. Here's the summary:
tokens used
109,389
All tests pass on the final run too. Here's the summary:

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

Installed in 28 minutes.
Recovered from all 3 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.

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.
Measured once so far. A single attempt shows it can run, not that it runs reliably.

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 by	attempt	outcome	score	cost USD	when
Argusic Runner	1/3	Runs with mocks	92.00	0.18	2026-10-04 15:02 UTC

Topics (from GitHub)

containers context kubernetes kubernetes-mcp mcp model modelcontextprotocol openshift protocol

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 28 minutes, hitting 3 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. One attempt is 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.18: 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?: 28 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?: 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for kubernetes-mcp-server?: The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.