mcp-server-kubernetes

MCP Server for kubernetes management commands

Runs with mockssource: GitHubhomepageTypeScriptMITcommit 3d71add20401

TypeScript, MIT licensed. The project labels itself: infrastructure, kubernetes, mcp and server.

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

The MCP server for Kubernetes builds from source and starts successfully. 249 tests across 23 test files pass using a mock kubectl that responds to all commands the test suite issues. The remaining integration tests require a real Kubernetes cluster.

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.58 (measured)
recorded runs
2
last tested
stars
1,614
forks
288
open issues
9
watchers
13
size
3 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 mcp-server-kubernetes, 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.

  • No Kubernetes cluster available for integration tests15 minutes
  • kubectl binary not found in PATH1 minute
  • bun binary not found in PATH1 minute
Install time
1 minutes
Cold machine to finish
55 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
npx vitest run 23 test files covering unit tests and integration tests with mock kubectl -> 249 passed, 0 failed
Model tokens used
431,352
Exact commit tested
3d71add20401
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.

/bin/sh -lc 'cd /work/repo && echo "=== Build ===" && ls -la dist/index.js && echo "=== Server star…
 succeeded in 1623ms:
=== Build ===
-rwxrwxr-x 1 runner runner 11736 Nov 14 10:32 dist/index.js
=== Server start ===
Starting Kubernetes MCP server v4.1.9, handling commands...
Telemetry: Disabled
=== End ===
Here's the final report.
tokens used
431,352
Here's the final report.

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 1 minute.
  • Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed MIT, 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.

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.58
Argusic Runner1/3Runs with mocks92.000.08

Topics (from GitHub)

infrastructurekubernetesmcpserver

Embed the badge

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

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

Questions

Does mcp-server-kubernetes run?
mcp-server-kubernetes runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 1 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test mcp-server-kubernetes?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 3d71add20401. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test mcp-server-kubernetes?
The run that produced this verdict cost $0.58: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does mcp-server-kubernetes take to install?
1 minute in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does mcp-server-kubernetes need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing mcp-server-kubernetes?
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 mcp-server-kubernetes?
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