MCP server for Kubernetes command execution, node inspection, and diagnostics
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"k8s-mcp-extension","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# K8s MCP Server MCP server for Kubernetes command execution, node inspection, and node-level diagnostics. Extension of [k8s-mcp-server](https://github.com/alexei-led/k8s-mcp-server) by alexei-led. ## Features - validated wrappers around `kubectl`, `helm`, `istioctl`, and `argocd` - node-aware kubeconfig selection through `K8S_NODE_PREFIX_MAPPING` - `run_checkup_on_node` for `kubectl node-shell ... checkup -n` - `get_logs_on_node` for collecting `dmesg`, `journalctl`, `/var/log/*`, and `/var/crash` - Kubernetes node inspection tools for status, labels, pods, and resources ## Configuration Set `K8S_NODE_PREFIX_MAPPING` to a JSON object that maps a node prefix to a kubeconfig file name: ```json { "node-a": "cluster-a.config", "edge": "edge-cluster.config" } ``` The kubeconfig files are resolved relative to `K8S_KUBECONFIG_DIR`, which defaults to `~/.kube`. ## Example MCP Client Configuration When installing from PyPI, you can use the package-matched command name `k8s-mcp-extension`. The legacy `k8s-mcp-server` command remains available for backward compatibility. ```json { "mcpServers": { "k8s-server": { "command": "k8s-mcp-extension", "cwd": "/absolute/path/to/project", "env": { "K8S_KUBECONFIG_DIR": "/path/to/.kube", "K8S_NODE_PREFIX_MAPPING": "{\"node-a\": \"cluster-a.config\", \"edge\": \"edge-cluster.config\"}", "K8S_MCP_TIMEOUT": "600" } } } } ``` ## Development Create the environment and run checks: ```bash uv sync --extra dev .venv/bin/python -m pytest .venv/bin/python -m ruff check ``` Run the server locally: ```bash .venv/bin/python -m k8s_mcp_server ``` After installing the package, either console script works: ```bash k8s-mcp-extension k8s-mcp-server ```
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.