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 ServerMCP server for interacting with Kubernetes clusters via kubectlMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS61 / 100 · C79 / 100 · B
Reliability10 / 2012 / 20
Security and permissions3 / 2018 / 20
Maintenance16 / 2016 / 20
Documentation17 / 2018 / 20
Setup experience15 / 2015 / 20
Best for
  • Developers and operators managing Kubernetes clusters via AI assistants
  • Scenarios requiring quick troubleshooting and diagnosis of K8s issues
  • Users integrating with MCP clients like Claude Desktop, Codex CLI
  • 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 needing a GUI for Kubernetes management
  • Environments without kubectl or kubeconfig
  • Production environments where fine-grained RBAC control is trusted to AI assistants
  • 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
  • Read and modify Kubernetes resources (possibly restricted by configuration)
  • Execute kubectl commands (including creating, deleting, updating resources)
  • Access kubeconfig file to connect to clusters
  • May perform port forwarding and node draining operations
  • 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
  • Accidental deletion or modification of resources (mitigated by non-destructive mode)
  • Exposure of sensitive information (e.g., secrets, mitigated by secrets masking)
  • Overly broad permissions can lead to cluster misconfiguration or failures
  • Unauthorized access if kubeconfig is leaked
  • 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 Code, Claude Desktop, Codex, Cursor, VS CodeClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools230