{"id":"randybias-k0rdent-mcp-server","name":"k0rdent-mcp-server","af_score":42.5,"security_score":19.5,"reliability_score":18.8,"what_it_does":"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.","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.","last_evaluated":"2026-04-04T21:20:16.611266+00:00","has_mcp":true,"has_api":false,"auth_methods":["Kubeconfig-based access (admin kubeconfig path)"],"has_free_tier":false,"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)."],"error_quality":0.0}