Community System
Kubernetes
Inspect + modify Kubernetes resources — pods, deployments, services, ConfigMaps, secrets.
1,611 stars 286 forks Last commit 1d ago Language Go License Apache-2.0
Install
npm install -g mcp-server-kubernetes Maintain this server? Add the badge
Show your README readers it's in a curated directory — and give them a one-click path to install docs and config.
Markdown
[](https://prismix.dev/mcp/kubernetes) Theme-aware version (auto dark/light on GitHub) →
<a href="https://prismix.dev/mcp/kubernetes"><picture><source media="(prefers-color-scheme: dark)" srcset="https://prismix.dev/api/badge/mcp/kubernetes.svg?theme=dark"><img alt="Listed on Prismix" src="https://prismix.dev/api/badge/mcp/kubernetes.svg"></picture></a> About
kubectl-equivalent surface as MCP tools. Reads cluster state via the loaded kubeconfig context, supports create/update/delete on standard resources, and can stream pod logs. Use with a restricted ServiceAccount in production.
Recent releases (5)
All releases →- Release v4.2.2 v4.2.2 Latest Nov 10, 2026
Adding context parameter to helm tools. Thanks to @lbarrosby for the contribution!
View on GitHub ↗ - Release v4.2.1 v4.2.1 Oct 26, 2026
Tool arguments are now validated against each tool's input schema before running, with errors that name the argument, the expected type or values, and what was received (#393).
View on GitHub ↗ - Release v4.2.0 v4.2.0 Oct 26, 2026
Hardening of kubectl argument handling: a verb policy for kubectl_generic (#387), fail-closed argv checks (#388), kubectl_create input validation (#389), flag-shaped operand checks in the remaining tools (#390), private temp files (#391), and kubectl_context set disabled in read-only mode (#392).
View on GitHub ↗ - Release v4.1.9 v4.1.9 Oct 2, 2026
`exec_in_pod` is now classified as a destructive tool, so not allowed under ALLOW_ONLY_NON_DESTRUCTIVE_TOOLS. @rr-paras-patel
View on GitHub ↗ - Release v4.1.8 v4.1.8 Sep 29, 2026
Start in degraded mode instead of crashing when kubeconfig has no current-context, so MCP initialize still succeeds and cluster tools return a clear configuration error (#377).
View on GitHub ↗
Discussion (0)
Sign in to comment →No comments yet. Sign in to start the discussion.