k0rdent-mcp-server
An experimental MCP server (localhost-only) that exposes k0rdent management capabilities—such as managing ClusterDeployments, installing/deleting ServiceTemplates, listing providers/credentials, and Kubernetes read operations like namespaces/events/pod logs—to MCP-compatible AI clients.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Major risks called out by the README: no TLS (localhost-only), requires admin kubeconfig with no RBAC enforcement, and experimental AI-assisted code not security reviewed. Because access is effectively the kubeconfig and localhost reachability, treat the server as high-privilege; protect the kubeconfig file and the local network. Rate limits and fine-grained authorization are not described. Error recovery/cleanup may fail, increasing operational risk.
⚡ Reliability
Best When
You have a local, trusted dev machine and an existing k0rdent management cluster, and you want to prototype MCP-driven orchestration/observability for k0rdent during development or testing.
Avoid When
You need hardened auth (OIDC/RBAC), TLS/remote exposure, reliable idempotent operations, strong error recovery/cleanup, or you cannot tolerate experimental instability and potential cloud resource leakage.
Use Cases
- • Explore k0rdent management via MCP from an AI assistant (Claude Desktop/Claude Code).
- • List and inspect k0rdent resources (namespaces, cluster templates, service templates, cluster deployments, provider credentials).
- • Trigger k0rdent cluster/service workflows through MCP tools (including creating/deleting ClusterDeployments and applying ServiceTemplates).
- • Monitor provisioning progress and subscribe to cluster/event streams via MCP resources.
Not For
- • Production use or any scenario requiring strong security guarantees.
- • Exposing the service to untrusted networks (it explicitly runs without TLS).
- • RBAC-restricted environments (requires admin kubeconfig; no RBAC filtering).
- • Environments where cost and cloud resource lifecycle risk are unacceptable (operations can create real cloud resources and may leave orphans).
Interface
Authentication
No OIDC or RBAC enforcement is described. Auth is effectively “whoever holds the admin kubeconfig / can reach localhost can act,” and some tooling is explicitly marked as not suitable for RBAC-restricted environments.
Pricing
No SaaS pricing indicated; costs are primarily cloud infrastructure costs from provisioning actions.
Agent Metadata
Known Gotchas
- ⚠ Localhost-only + no TLS: ensure the MCP client is on the same host and do not expose externally.
- ⚠ Requires admin kubeconfig and no RBAC enforcement: agents must be prevented from performing unsafe/destructive actions unless explicitly approved.
- ⚠ Cluster deployment operations can create real cloud resources and incur costs; failures may leave orphaned resources.
- ⚠ GCP deployments are untested/likely broken; AWS is minimally tested.
- ⚠ Catalog synchronization may have bugs; concurrent operations may race.
- ⚠ Some apply/service operations may not handle parameters robustly (e.g., ServiceTemplate apply mentions doesn’t handle params).
- ⚠ If you restart the server, the client may need to reconnect (Claude Code / /mcp hint mentioned).
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for k0rdent-mcp-server.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-04-04.