Field names and resource shapes move between Kubernetes releases and a model's recall of them carries no date. Loading v1.33 and v1.35 side by side turns "is this field still there" into a lookup with a version attached.
A container that serves Kubernetes API resource documentation over MCP. You tell it which versions to pre-load and it answers from those.
- Kubernetes API resources listed for the versions you loaded
- The full definition of a named resource, read back from that version's documentation
- Several versions pre-loaded side by side, which is how you see what changed between them
- Anonymous mode for local use, or an API key store with per-tier rate limits when the instance is shared
A container runtime — podman or docker — publishing the server's HTTP port. An environment variable picks which Kubernetes versions load, and it defaults to v1.33. A GitHub token is optional and raises the GitHub API rate limit, which matters when loading several versions at once. Running it anywhere but locally means declaring the hostnames it will answer on.
One command — podman run -d \ -p 3000:3000 \ -e K8S_VERSIONS=v1.33 \ ghcr.io/kubernetools/mcp-server:latest