M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionKubernetes MCP ServerNative Kubernetes and OpenShift control for AI assistants via MCP.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS63 / 100 · C79 / 100 · B
Reliability10 / 2012 / 20
Security and permissions10 / 2018 / 20
Maintenance14 / 2016 / 20
Documentation17 / 2018 / 20
Setup experience12 / 2015 / 20
Best for
  • Developers and platform engineers who want AI assistants (Claude Desktop, Claude Code, VS Code, Cursor) to interact directly with Kubernetes/OpenShift clusters
  • Teams needing lightweight, dependency-free cluster access without kubectl/helm binaries installed locally
  • Multi-cluster environments defined across kubeconfig contexts
  • Engineering teams scaling AI coding agents while controlling spend
  • Platform teams that need auditable, rollback-aware agent execution records
  • Organizations using multiple agents (Claude, Codex, Gemini) under one governed flow
Not for
  • Users without access to a Kubernetes cluster
  • Strictly read-only or isolated environments where --read-only/--disable-destructive flags haven't been reviewed first
  • Users who just want a thin kubectl wrapper (this is a native reimplementation, not kubectl passthrough)
  • Developers who just want a simple code-completion helper without run governance
  • Teams unwilling to accept local JSONL run records with HMAC signing
  • Environments without a supported adapter (Claude/Codex/Gemini CLIs, direct provider, or verifier-only)
Required permissions
  • Requires a kubeconfig file (or in-cluster ServiceAccount) with API access to the target cluster(s)
  • Docker/OCI deployment requires a mounted kubeconfig volume and an exposed HTTP port
  • By default has full read/write access to cluster resources unless --read-only or --disable-destructive is set
  • The pods_exec tool can run arbitrary commands inside cluster containers
  • Read/write access to the configured repo root (writable scope restrictable via --allow-path/--deny-path)
  • Ability to invoke the chosen agent CLI (Claude/Codex/Gemini, etc.) and its underlying model account
  • Local disk writes for run records, receipts, and share outputs (share/run-receipt., etc.)
  • Execution of user-configured verifier commands (e.g. npm test)
Risks and side effects
  • Default configuration allows create/update/delete on any Kubernetes/OpenShift resource, including Secrets, unless restricted via denied_resources or read-only mode
  • pods_exec and resources_create_or_update can be used to run arbitrary commands or alter cluster state
  • Streamable HTTP mode exposes a network endpoint (port 8080 in the Docker example) that should be secured with the supported OAuth/OIDC before exposing beyond localhost
  • Multi-cluster support means a single compromised MCP session could reach every cluster defined in the kubeconfig
  • Verifier commands are executed; poorly chosen verifier commands carry security risk despite preflight policy checks
  • Cost and token figures may be estimates (labeled with provenance) and should not be treated as settled accounting
  • Receipt integrity must be verified before use as trustworthy evidence; missing rollback evidence is flagged as EVIDENCE_BOUNDARY
  • Policy defaults come from martin.config.yaml and can be overridden by CLI flags; misconfiguration can loosen safety boundaries
Supported clientsClaude Desktop, Claude Code, VS Code, Cursor, Goose CLIClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools460