mcpField
W

WhiteCapData-Dev

Local
github.com/Michael-WhiteCapDataCloud & Infra
Repository

About WhiteCapData-Dev

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

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "michael-whitecapdata-whitecapdata-dev": {
      "command": "uvx",
      "args": [
        "whitecapdata-dev"
      ],
      "env": {
        "HOMELAB_MCP_CONTEXT": "<HOMELAB_MCP_CONTEXT>",
        "HOMELAB_MCP_READONLY": "<HOMELAB_MCP_READONLY>",
        "HOMELAB_MCP_MUTABLE_NAMESPACES": "<HOMELAB_MCP_MUTABLE_NAMESPACES>",
        "HOMELAB_MCP_MAX_REPLICAS": "<HOMELAB_MCP_MAX_REPLICAS>"
      }
    }
  }
}
Run commanduvx whitecapdata-dev
Environment variables to set
HOMELAB_MCP_CONTEXTkubeconfig context to use (defaults to current-context).
HOMELAB_MCP_READONLYSet to 1/true to disable all mutating tools.
HOMELAB_MCP_MUTABLE_NAMESPACESComma-separated namespaces mutations may touch; '*' allows all.
HOMELAB_MCP_MAX_REPLICASUpper bound accepted by scale_deployment.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
pypiwhitecapdata-dev0.1.2

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

The maintainer has not added details yet. Check the README in the repository.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.