mcp-kubernetes (Azure)

Microsoft's Kubernetes MCP server (used by AKS tooling) with access levels.

By defaultRead-only
With our presetSame: read-only is built in
Flagssecrets

Labels are provisional (from the project README/docs, checked Nov 3, 2026). Not yet tested in our sandbox.

Read-only switch

--access-level readonly is the default. readwrite and admin raise it. Container images are no longer produced; run the released binary.

Preset

Read-onlyRead-only switch from the vendor's docs. Not sandbox-tested yet.

Claude Code

.mcp.json
{
  "mcpServers": {
    "kubernetes": {
      "command": "mcp-kubernetes",
      "args": ["--access-level", "readonly"]
    }
  }
}

Optional third layer: add "deny": ["mcp__kubernetes__<write tool>"] under permissions in .claude/settings.json.

Codex

~/.codex/config.toml
# Generated by redpresets.dev on 2026-11-03. Unverified preset. Also use a read-only credential. Not a security guarantee.

[mcp_servers.kubernetes]
command = "mcp-kubernetes"
args = ["--access-level", "readonly"]
default_tools_approval_mode = "writes"

default_tools_approval_mode = "writes" asks before any tool the server does not mark read-only.

Cursor

.cursor/mcp.json
{
  "mcpServers": {
    "kubernetes": {
      "type": "stdio",
      "command": "mcp-kubernetes",
      "args": ["--access-level", "readonly"]
    }
  }
}

Don't add write tools to mcpAllowlist in .cursor/permissions.json. Leave them on approval. Cursor's docs say the allowlist is not a security boundary.

Credential layer

Bind the kubeconfig/service account the agent uses to a read-only ClusterRole (e.g. the built-in view role). view excludes Secrets; do not grant get secrets to agents.

Facts

Vendor
Microsoft Azure official
Source
Azure/mcp-kubernetes
License
MIT
GitHub stars
61
Latest release
v0.0.16 (Aug 11, 2026)
Last push
Oct 24, 2026
Status
Active
Last checked
Nov 3, 2026

Sources

Spotted something wrong? Labels change when vendors change. Suggest a correction

Read-only alternatives in Kubernetes