WhiteCapData-Dev
About
Operate a k3s / Kubernetes cluster from your AI agent — health, logs, and guarded restart/scale/delete; safe by default with a read-only switch and namespace allowlist.
Details
- Author
- michael-whitecapdata
- Categories
- Cloud Service, Other, Infrastructure
Jump to
Setup
Install WhiteCapData-Dev in your MCP client (Claude Desktop, Cursor, Windsurf, and others).
Repository: https://github.com/michael-whitecapdata/WhiteCapData-Dev
Follow the installation instructions in the repository README, then restart your MCP client.
Operate a k3s / Kubernetes cluster straight from your AI agent — safe by default.
The design goal issafe by default: reads are always on; every mutating action (restart / scale / delete) is gatedbefore the API callby a read-only switch and a namespace allowlist, so an over-eager agent can't touchkube-systemor nuke a deployment you didn't sandbox.
Name note:the PyPI package iswhitecapdata-dev(thehomelab-k8s-style name was taken); the import package and tools are k8s/homelab-focused as described here.
- 🩺One-call health.cluster_summarygives node + pod totals and the unhealthy pods, so the agent starts triage with real data.
- 🔒Safe by default.Mutations are blocked unless the namespace is on your allowlist; flipHOMELAB_MCP_READONLY=1to make the whole server read-only.
- 🧰The operations you actually do.Pods, deployments, events, logs, node health, rollout-restart, scale, delete-pod.
- 🪶No bespoke backend.Uses the standard Kubernetes API + your kubeconfig — nothing to deploy server-side.
- ✅Tested.Pure logic is unit-tested with fakes; guard logic is tested against a mocked API. No cluster needed to run the suite.
- A reachable cluster and a workingkubeconfig(the same onekubectluses), or run it in-cluster with a service account.
- Python 3.11+ (or justuvx).
uvx whitecapdata-dev # run directly # or pip install whitecapdata-dev # then run: whitecapdata-dev
claude mcp add homelab -- uvx whitecapdata-dev
{ "mcpServers": { "homelab": { "command": "uvx", "args": ["whitecapdata-dev"], "env": { "HOMELAB_MCP_MUTABLE_NAMESPACES": "default,apps,monitoring", "HOMELAB_MCP_READONLY": "0" } } } }
docker build -t whitecapdata-dev . docker run --rm -i \ -v "$HOME/.kube/config:/home/app/.kube/config:ro" \ -e HOMELAB_MCP_READONLY=1 \ whitecapdata-dev
- Read-only switch—HOMELAB_MCP_READONLY=1rejects every mutating tool up front.
- Namespace allowlist— mutating tools refuse any namespace not inHOMELAB_MCP_MUTABLE_NAMESPACES(default a homelab-friendly set;*opts into all).
- Bounded scale—scale_deploymentclamps to0..HOMELAB_MCP_MAX_REPLICAS.
The cluster's own RBAC still applies on top — this server can only do what the kubeconfig identity is permitted to do.
git clone https://github.com/Michael-WhiteCapData/WhiteCapData-Dev cd WhiteCapData-Dev uv pip install -e ".[dev]" ruff check . pytest # no cluster required — APIs are faked/mocked
Query and interact with kubernetes environments monitored by Metoro
An MCP server for managing Kubernetes clusters, configured via an external JSON file.
A comprehensive Model Context Protocol (MCP) server for the Cloudability API, providing advanced cost management, Kubernetes container analytics, and budget forecasting capabilities.
A server for Kubernetes CLI tools like kubectl, istioctl, helm, and argocd, supporting multi-cluster management via dynamic kubeconfig.
An MCP server for kubectl, enabling AI assistants to interact with Kubernetes clusters through a standardized protocol.
A read-only MCP server for retrieving information and diagnosing issues in Kubernetes clusters.
Provides safe, read-only access to Kubernetes cluster resources for debugging and inspection.
Execute Kubernetes commands using kubectl from any MCP-compatible client. Requires a valid kubeconfig file.
A server for managing Kubernetes clusters using the Model Context Protocol.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
