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 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
26 unit test files pass (297 tests), the build compiles cleanly, the MCP server responds to initialize and tool calls, and all tool interactions are handled through a mock kubectl since no real cluster is available.
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
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.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- kubectl not installed; official CDN download returned 404 errors3 minutes
- bun not available in PATH0.5 minutes
- Install time
- 1 minutes
- Cold machine to finish
- 14 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- npx vitest run 26 test files returned 297/297 passed; echo '{jsonrpc...initialize...}' | node dist/index.js returned serverInfo version 4.1.9 with tools/list and tools/call for kubectl_get pods returning JSON
- Model tokens used
- 141,305
- 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.
| `prompts.test.ts` | 1 passed | | `server-config.test.ts` | 1 passed | | `sse.test.ts` | 2 passed | | `streaming_http.test.ts` | 2 passed | | `telemetry-config.test.ts` | 40 passed | | `telemetry-integration.test.ts` | 13 passed | | `allowed_tools_validation.unit.test.ts` | 5 passed | **Server end-to-end**: The server binary accepts initialize and tool/list requests, and executing `… **Skipped tests** (need real cluster + kubectl binary on PATH): `configmap.test.ts`, `contexts.test… **Issues encountered and fixed**: - `bun` not found — installed as local npm dependency in `node_modules/.bin/` - `kubectl` not found — download failed (CDN returning XML errors for this container), created mock…
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 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, 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.08 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](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 2 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. One attempt is 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.08: 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?
- 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.
- Where is the evidence for mcp-server-kubernetes?
- 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.