Developer · Local MCP server
WhiteCapData Dev
Operate a k3s / Kubernetes cluster from your AI agent - safe-by-default MCP server.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.Michael-WhiteCapData/WhiteCapData-Dev- Version
- 0.1.2
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- PyPI
- Published
- 2026-06-23
- Updated
- 2026-06-23
- Publisher
- Michael-WhiteCapData (GitHub) · 3 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/Michael-WhiteCapData) · how
- Listed under
- Kubernetes MCP servers
- Repository
- github.com/Michael-WhiteCapData/WhiteCapData-Dev
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPI | whitecapdata-dev | 0.1.2 | stdio |
How to connect WhiteCapData Dev
WhiteCapData Dev runs locally from a Python package published to PyPI: whitecapdata-dev version 0.1.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx whitecapdata-dev. It reads these environment variables: HOMELAB_MCP_CONTEXT, HOMELAB_MCP_READONLY, HOMELAB_MCP_MUTABLE_NAMESPACES and HOMELAB_MCP_MAX_REPLICAS; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"whitecapdata-dev": {
"command": "uvx",
"args": [
"whitecapdata-dev"
],
"env": {
"HOMELAB_MCP_CONTEXT": "<value>",
"HOMELAB_MCP_READONLY": "<value>",
"HOMELAB_MCP_MUTABLE_NAMESPACES": "<value>",
"HOMELAB_MCP_MAX_REPLICAS": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from Michael-WhiteCapData (GitHub)
| Server | Runs |
|---|---|
| Ollama HandoffOffload cheap work from your AI agent to a local Ollama model, at zero cloud cost. | Local · stdio |
| Tablebridge MCPQuery a folder of CSV / Parquet / JSON files with SQL - one queryable source, read-only. | Local · stdio |
More developer servers
| Server | Runs |
|---|---|
| whichlibDependency picker for coding agents: recommends, compares and scores GitHub repos with a verdict. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| WhichModelCost-optimized LLM model routing recommendations for autonomous AI agents. | Remote · HTTPLive check: ✗ no handshake |
| WhisperOne routable IPv6 per AI agent, verifiable from the DNS root. Keyless tools need no signup. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| WhisperGraphThe internet's infrastructure graph for AI agents - 46B nodes and edges, free trial via 2 HTTP calls. | Remote & Local · HTTP, stdioLive check: sign-in required |
| Whmcs MCP ServerMCP server for WHMCS - 73 tools, 10 resources, 8 prompts, simulate mode, rate limiting. | Local · stdio |
| Whois MCP ServerDomain registration, availability, DNS records, and IP/ASN resolution via RDAP and DNS-over-HTTPS. | Local · stdio, HTTP |
| WhoisJSONWHOIS, DNS, SSL, and domain availability lookups for AI assistants. | Local · stdio |
| Whoop MCPRead-only WHOOP v2 data for MCP clients, with local SQLite cache and CSV/JSONL/Parquet exports. | Local · stdio |