MCP.Market

WhiteCapData Dev MCP server

by Michael-WhiteCapData·io.github.Michael-WhiteCapData/WhiteCapData-Dev·v0.1.2·2 stars

Operate a k3s / Kubernetes cluster from your AI agent — safe-by-default MCP server.

A89/100grade A
What users say
No reviews yet
Be the first
Safety scan
A89/100

full report

Adoption
Growing

2 stars119 downloads/wk

Reviews

Write one

Nobody has reviewed WhiteCapData Dev yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

WhiteCapData Dev tools (10, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • cluster_summary

    Summarize overall cluster health in a single call.

  • delete_podwrite action

    Delete a single pod so its controller recreates it.

  • list_deployments

    List deployments with their ready/desired replica counts and namespace.

  • list_events

    Return recent cluster events, most relevant first (Warnings before Normal).

  • list_pods

    List pods with phase, restart count, and node, unhealthy pods sorted first.

  • node_health

    Report per-node readiness, kubelet version, capacity, and pressure conditions.

  • pod_logs

    Return the last `tail` lines of a single pod's logs as plain text.

  • restart_deployment

    Trigger a rolling restart of a deployment (like `kubectl rollout restart`).

  • scale_deployment

    Scale a deployment to a specific replica count.

  • server_info

    Report the server's effective configuration.

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

no findings
  • Code scan7 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 3 days ago15/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 89/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How WhiteCapData Dev compares

Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
89/100
higher than 80% of 1,119 Developer tools servers
Tools
10
the typical Developer tools server has 7
Tools that change things
10%
typical: 5%. Fewer write tools means less an agent can break
GitHub stars
2
more than 65% of 854 Developer tools servers
Downloads a week
119
more than 62% of 430 Developer tools servers with a package

What its tools let an agent do: 8 read · 1 delete · 1 run or deploy

Install WhiteCapData Dev in Claude Code, Cursor or VS Code

claude mcp add WhiteCapData-Dev -- uvx whitecapdata-dev
Add to Cursor

What the publisher says

From the WhiteCapData Dev repository's README, as published. We do not edit it. Read it on GitHub

<!-- mcp-name: io.github.Michael-WhiteCapData/WhiteCapData-Dev -->

WhiteCapData-Dev

Operate a k3s / Kubernetes cluster straight from your AI agent — safe by default.

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 design goal is safe by default: reads are always on; every mutating action (restart / scale / delete) is gated before the API call by a read-only switch and a namespace allowlist, so an over-eager agent can't touch kube-system or nuke a deployment you didn't sandbox.

Name note: the PyPI package is whitecapdata-dev (the homelab-k8s-style name was taken); the import package and tools are k8s/homelab-focused as described here.

Why you'd want this

  • 🩺 One-call health. cluster_summary gives 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; flip HOMELABMCPREADONLY=1 to 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.

Requirements

  • A reachable cluster and a working kubeconfig (the same one kubectl uses), or run it in-cluster with a service account.
  • Python 3.11+ (or just uvx).

Install

uvx whitecapdata-dev          # run directly
# or
pip install whitecapdata-dev  # then run: whitecapdata-dev

Claude Code

claude mcp add homelab -- uvx whitecapdata-dev

Claude Desktop / Cursor

{
  "mcpServers": {
    "homelab": {
      "command": "uvx",
      "args": ["whitecapdata-dev"],
      "env": {
        "HOMELAB_MCP_MUTABLE_NAMESPACES": "default,apps,monitoring",
        "HOMELAB_MCP_READONLY": "0"
      }
    }
  }
}

Run with Docker

A Dockerfile is included. The server speaks MCP over stdio and reaches your cluster through a mounted kubeconfig. Run interactively (-i), starting read-only:

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

Tools

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

WhiteCapData Dev: common questions

Is WhiteCapData Dev MCP server safe?
Yes, by our scan: it is graded A (89/100). Read the WhiteCapData Dev safety report
How do I install WhiteCapData Dev?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does WhiteCapData Dev need an API key?
No secret keys are declared. It reads 4 settings from the environment.
Is WhiteCapData Dev maintained?
The last commit was 40 days ago (2026-09-23). The latest release is v0.1.2.
What can I use instead of WhiteCapData Dev?
Servers from other publishers that do the same job: Nora MCP server, KSail MCP server and Kubently MCP server. Compare all WhiteCapData Dev alternatives.
How does WhiteCapData Dev compare with other Developer tools MCP servers?
safety score 89/100 (higher than 80% of 1,119 Developer tools servers); tools 10 (the typical Developer tools server has 7); tools that change things 10% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to WhiteCapData Dev

Same job from other publishers: the closest match first, then the best rated.

All WhiteCapData Dev alternatives →
  • Nora
    Operate self-hosted OpenClaw and Hermes agent fleets on Docker or Kubernetes from MCP clients.
    B
  • KSail
    SDK for creating, managing, and operating Kubernetes clusters and workloads with ease.
    A
  • Kubently
    Troubleshoot Kubernetes agentically: natural-language cluster diagnosis via ask_kubently
    B
  • Ocm
    Guardrailed fleet ops for AI agents: multi-cluster Kubernetes via OCM with policy, approval, audit.
    B
  • Strimzi Kafka CLI
    Manage Apache Kafka on Kubernetes via Strimzi. Clusters, topics, users, connectors, MM2.
    A

More from Michael-WhiteCapData →