mcpField
M
mcp-kubernetes

mcp-kubernetes

Local
github.com/dockndevaiCloud & Infra2Updated 3d ago

About mcp-kubernetes

mcp-kubernetes lets MCP clients inspect and operate Kubernetes clusters across contexts. Its access modes, allowlists, opt-in safeguards, and audit logging govern which operations are available.

Key features

  1. 01Inspect clusters across contexts
  2. 02Read-only, read-write, and admin modes
  3. 03Namespace and context allowlists
  4. 04Gated delete, apply, and pod exec
  5. 05Dry-run and JSON audit logging
  6. 06Optional local AI risk guard

Use cases

  1. 01Inspect pods, deployments, and cluster events
  2. 02Scale or restart deployments with scoped access
  3. 03Gate manifest changes and destructive operations
  4. 04Preview and audit Kubernetes operations

MCP support

The MCP server exposes Kubernetes read, write, and admin tools to MCP clients. Available tools depend on configured modes and safety gates; high-impact actions can request human approval through MCP elicitation.

Configuration

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

mcp.json · Universal config
{
"mcpServers": {
"dockndevai-mcp-kubernetes": {
"command": "npx",
"args": [
"-y",
"@dockndevai/mcp-kubernetes"
],
"env": {
"KUBECONFIG_PATH": "<KUBECONFIG_PATH>",
"K8S_MODE": "<K8S_MODE>"
}
}
}
}
Run commandnpx -y @dockndevai/mcp-kubernetes
Environment variables to set
KUBECONFIG_PATHPath to a kube-config file (empty = default resolution).
K8S_MODEAccess mode: read-only | read-write | admin.

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
npm@dockndevai/mcp-kubernetes0.3.3

Tools

10

Saved tool list · updated 2d ago

This tool takes no parameters.

Details

From the project README

mcp-kubernetes

CI License: MIT npm

A Model Context Protocol server for Kubernetes. It lets an MCP-capable client (Claude Desktop, Claude Code, etc.) inspect and operate Kubernetes clusters across multiple contexts — with behaviour controlled entirely by flags.

The design goal is safe by default: it starts read-only, can be scoped to an allowlist of namespaces and contexts, protects system namespaces from mutation, and gates the dangerous operations (delete, apply, exec) behind explicit opt-ins.

Features

  • Multi-cluster — every tool accepts an optional context; scope which contexts are usable with an allowlist.
  • Access modes — read-only → read-write → admin, layered so a mode never exposes tools above its level.
  • Security flags — namespace allowlist, protected namespaces, context allowlist, plus independent opt-ins for delete / apply / exec, dry-run, and JSON audit logging (see below).
  • Standard auth — uses your kube-config (or in-cluster service account). No credentials are stored by the server.

Security model

ConcernFlagDefaultEffect
What can the server do at all?K8S_MODEread-onlyread-only exposes only reads; read-write adds mutations; admin adds destructive tools. Tools above the mode are never registered.
Which namespaces are in scope?K8S_NAMESPACE_ALLOWLIST(all)When set, any operation on a namespace outside the list is refused.
Which namespaces are read-only forever?K8S_PROTECTED_NAMESPACESkube-system,kube-public,kube-node-leaseCan be read but never mutated or deleted, regardless of mode.
Which clusters are reachable?K8S_CONTEXT_ALLOWLIST(all)When set, only these kube-config contexts may be targeted.
Can it delete?K8S_ALLOW_DELETEfalsedelete_resource needs this and admin mode.
Can it apply manifests?K8S_ALLOW_APPLYfalseapply_manifest needs this and read-write mode.
Can it exec into pods?K8S_ALLOW_EXECfalseexec_in_pod needs this and admin mode; the tool isn't even registered otherwise.
Preview without touching the clusterK8S_DRY_RUNfalseWrite/admin tools validate + log intent, then return without calling the API.
Audit trailK8S_AUDIT_LOGtrueEmits a JSON line to stderr per guarded operation (ALLOW / DENY / DRY_RUN).
Interactive confirmation(automatic)—Destructive & high-impact actions prompt the human to approve via MCP elicitation before running; clients without elicitation fall back to the *_ALLOW_* gate.

The layers are independent — e.g. admin mode with all three opt-ins false can restart and scale deployments but can neither delete resources nor exec into pods.

Tools

Read (read-only+): list_contexts, list_namespaces, list_pods, get_pod, get_pod_logs, list_deployments, list_services, list_nodes, list_events, get_resource

Write (read-write+): scale_deployment, restart_deployment, set_deployment_image, create_namespace, apply_manifest (needs K8S_ALLOW_APPLY)

Admin (admin): delete_resource (needs K8S_ALLOW_DELETE), exec_in_pod (needs K8S_ALLOW_EXEC)

Optional AI risk guard. Set K8S_GUARD_MODE=monitor|enforce to have delete_resource, exec_in_pod and apply_manifest consult a local laya-guard daemon (pipx install laya-guard && laya-guard) that classifies the operation allow/confirm/block before it runs. Runs after the delete/exec/apply gates; only tightens, never grants; fails closed.

Quickstart — add to your agent

Published on npm as @dockndevai/mcp-kubernetes. No clone or build needed — your MCP client runs it on demand with npx. Start in read-only mode; see .env.example for every variable and docs/CLIENTS.md for the full per-client guide.

Claude Code (CLI)

claude mcp add kubernetes -e KUBECONFIG_PATH="/Users/you/.kube/config" -e K8S_MODE="read-only" -- npx -y @dockndevai/mcp-kubernetes

Claude Desktop · Cursor · Windsurf — same block in claude_desktop_config.json, .cursor/mcp.json, or ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "kubernetes": {
      "command": "npx",
      "args": [
        "-y",
        "@dockndevai/mcp-kubernetes"
      ],
      "env": {
        "KUBECONFIG_PATH": "/Users/you/.kube/config",
        "K8S_MODE": "read-only"
      }
    }
  }
}

OpenAI Codex CLI — in ~/.codex/config.toml:

[mcp_servers.kubernetes]
command = "npx"
args = ["-y", "@dockndevai/mcp-kubernetes"]
env = { KUBECONFIG_PATH = "/Users/you/.kube/config", K8S_MODE = "read-only" }

VS Code (GitHub Copilot, Agent mode) — in .vscode/mcp.json:

{
  "servers": {
    "kubernetes": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@dockndevai/mcp-kubernetes"
      ],
      "env": {
        "KUBECONFIG_PATH": "/Users/you/.kube/config",
        "K8S_MODE": "read-only"
      }
    }
  }
}

Run from source (development)

Prefer the published package above. To run from a clone:

npm install
npm run build
node dist/index.js   # with the environment variables set

Develop

npm run dev        # watch mode
npm test           # unit tests for the security policy
npm run typecheck

Publishing

This server ships a server.json for the official MCP registry and an mcpName for npm ownership validation. See PUBLISHING.md for publishing to npm and listing on the MCP registry, Smithery, Glama, Cursor, and PulseMCP.

License

MIT

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.