{"id":"nokamoto-mcp-server-k8s-go","name":"mcp-server-k8s-go","homepage":null,"repo_url":"https://github.com/nokamoto/mcp-server-k8s-go","category":"infrastructure","subcategories":[],"tags":["mcp","kubernetes","go","stdio-transport","devtools","automation"],"what_it_does":"Provides an MCP server (stdio transport) intended to interact with Kubernetes using Go. The README shows how to run it for local testing and how to configure it as a local MCP server (with KUBECONFIG) in clients like Cline.","use_cases":["Kubernetes cluster inspection and operations via MCP tooling (e.g., prompts that trigger kubectl-like actions)","Local dev/testing of MCP agents that need access to Kubernetes resources","Hands-on experimentation with Model Context Protocol servers and the stdio transport"],"not_for":["Production-grade cluster automation without additional security hardening","Use cases requiring robust, documented CRUD semantics, pagination, or formal API contracts beyond the MCP interface","Environments where agents must not have access to kubeconfig-derived credentials"],"best_when":"You have a local or controlled Kubernetes environment (e.g., minikube) and want an MCP bridge for experimentation or internal tooling.","avoid_when":"You need strict operational safety controls (RBAC scoping, auditability, approval workflows) or you cannot manage kubeconfig permissions securely.","alternatives":["Generic MCP Kubernetes tools if available in your ecosystem","Direct kubectl integration through function/tool calling rather than MCP","Using Kubernetes-specific APIs/SDKs (client-go) behind your own authenticated service layer"],"af_score":38.0,"security_score":31.5,"reliability_score":17.5,"package_type":"mcp_server","discovery_source":["github"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T21:20:08.041403+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":null,"has_sdk":false,"sdk_languages":["Go"],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["KUBECONFIG (client-side kubeconfig environment variable)"],"oauth":false,"scopes":false,"notes":"No explicit auth mechanism is described in the README beyond using a kubeconfig path via env. Actual authorization is therefore governed by the kubeconfig credentials and Kubernetes RBAC."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"No pricing information provided (repo appears to be open source)."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":38.0,"security_score":31.5,"reliability_score":17.5,"mcp_server_quality":45.0,"documentation_accuracy":35.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":85.0,"rate_limit_clarity":0.0,"tls_enforcement":10.0,"auth_strength":30.0,"scope_granularity":20.0,"dependency_hygiene":40.0,"secret_handling":60.0,"security_notes":"The interface (stdio MCP) suggests no network transport/TLS concerns from the README alone, but the server likely operates with kubeconfig-derived credentials. Security therefore depends heavily on least-privilege Kubernetes RBAC and protecting the kubeconfig. README does not mention RBAC hardening, auditing, or safe operation constraints, and provides no guidance on how secrets are handled/logged by the server.","uptime_documented":0.0,"version_stability":30.0,"breaking_changes_history":20.0,"error_recovery":20.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["MCP communication is via stdio; agents/tools must correctly wire stdin/stdout transport.","The README provides only high-level usage; the available MCP tools/resources and their parameter schemas are not shown here.","KUBECONFIG is passed via env; agents may accidentally target the wrong cluster/context if kubeconfig is misconfigured.","No rate-limit, timeout, or retry guidance is documented, so agents may need conservative timeouts and manual retries if supported by the implementation."]}}