Operate a k3s / Kubernetes cluster from your AI agent — safe-by-default MCP server.
WhiteCapData MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Operate a k3s / Kubernetes cluster from your AI agent — safe-by-default MCP server.
An MCP server that lets an agent (Claude Code, Claude Desktop, Cursor, …) inspect and operate a Kubernetes / k3s cluster — your homelab box, a dev cluster, whatever your kubeconfig points at — without shelling out to kubectl. It talks to the Kubernetes API directly using your existing kubeconfig (or an in-cluster service account).
The server ships on PyPI as whitecapdata-dev, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Once WhiteCapData is connected, these are the calls the assistant has available:
cluster_summary — readlist_pods — readlist_deployments — readlist_events — readpod_logs — readnode_health — readrestart_deployment — writescale_deployment — writedelete_pod — writeserver_info — readYou will need 2 environment variables: HOMELAB_MCP_MUTABLE_NAMESPACES, HOMELAB_MCP_READONLY. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
kubectl uses), or run it in-cluster with a service account. - Python 3.11+ (or just uvx).Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. WhiteCapData's toolset — cluster_summary, list_pods, list_deployments and 7 more — is a fair guide to whether it matches your workflow. It is maintained by Michael-WhiteCapData; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| cluster_summary | read |
| list_pods | read |
| list_deployments | read |
| list_events | read |
| pod_logs | read |
| node_health | read |
| restart_deployment | **write** |
| scale_deployment | **write** |
| delete_pod | **write** |
| server_info | read |
{
"mcpServers": {
"homelab": {
"command": "uvx",
"args": ["whitecapdata-dev"],
"env": {
"HOMELAB_MCP_MUTABLE_NAMESPACES": "default,apps,monitoring",
"HOMELAB_MCP_READONLY": "0"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
kubectl uses), or run it in-cluster with a service account. - Python 3.11+ (or just uvx).| Variable | Description | Required |
|---|---|---|
| HOMELAB_MCP_MUTABLE_NAMESPACES | Configuration value read at startup. | Optional |
| HOMELAB_MCP_READONLY | Configuration value read at startup. | Optional |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.