mcp-kubernetes MCP Server
Multi-cluster Kubernetes monitoring & ops for AI agents — safe by default.
About
MCP server for Kubernetes. Inspect and operate clusters across contexts — pods, logs, deployments, services, nodes, events — and manage them (scale, restart, set image, apply, delete, exec) with read-only / read-write / admin access modes, namespace and context allowlists, protected system namespaces, independent delete/apply/exec opt-ins, dry-run, and audit logging. Uses your kube-config or in-cluster service account; stores no credentials.
Security Report
This is a well-designed Kubernetes MCP server with a strong security-by-default model. Authentication relies on standard Kubernetes credentials (kube-config or in-cluster service accounts), and a comprehensive policy engine gates all operations by capability mode, namespace, context, and destructive-operation flags. Code quality is high with proper input validation, no dangerous patterns, and excellent audit logging. Minor findings around error handling and input validation do not materially impact security. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 3 high severity). Package verification found 1 issue.
7 files analyzed · 9 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Required
This plugin requests these system permissions. Most are normal for its category.
How to Install
Add this to your MCP configuration file:
{
"mcpServers": {
"mcp-kubernetes": {
"args": [
"-y",
"@dockndevai/mcp-kubernetes"
],
"command": "npx"
}
}
}Getting Started
Once installed, try these example prompts and explore these capabilities:
- 1"List the pods in the default namespace"
- 2"Show recent events in namespace app"
- 3"Get the logs for pod X in namespace app"
- 4Tool: scale_deployment — scale a deployment (requires read-write mode)
Documentation
View on GitHubFrom the project's GitHub README.
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
| Concern | Flag | Default | Effect |
|---|---|---|---|
| What can the server do at all? | K8S_MODE | read-only | read-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_NAMESPACES | kube-system,kube-public,kube-node-lease | Can 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_DELETE | false | delete_resource needs this and admin mode. |
| Can it apply manifests? | K8S_ALLOW_APPLY | false | apply_manifest needs this and read-write mode. |
| Can it exec into pods? | K8S_ALLOW_EXEC | false | exec_in_pod needs this and admin mode; the tool isn't even registered otherwise. |
| Preview without touching the cluster | K8S_DRY_RUN | false | Write/admin tools validate + log intent, then return without calling the API. |
| Audit trail | K8S_AUDIT_LOG | true | Emits a JSON line to stderr per guarded operation (ALLOW / DENY / DRY_RUN). |
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)
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
Reviews
No reviews yet
Be the first to review this server!
More Cloud & DevOps MCP Servers
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
mcp-creator-python
Freeby mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.
MarkItDown
Freeby Microsoft · Content & Media
Convert files (PDF, Word, Excel, images, audio) to Markdown for LLM consumption
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.
FinAgent
Freeby mcp-marketplace · Finance
Free stock data and market news for any MCP-compatible AI assistant.
Google Workspace MCP
Freeby Taylorwilsdon · Productivity
Control Gmail, Calendar, Docs, Sheets, Drive, and more from your AI