메뉴
Multi-cluster Kubernetes dashboard with AI-powered operations via MCP server and 10+ built-in agent skills
Use when CrossFrame Suite routes explicit Chinese casebook work: turning materials into reusable cases, anonymized entries, mechanisms, and retrieval indexes.
Use only when the user explicitly names crossframe-critical for a Chinese structural critique dossier, article plan, or long-form critical essay.
Use when CrossFrame Suite routes explicit Chinese proposition testing, debate analysis, hidden-premise review, rebuttal design, or withdrawal condition checks.
Use when CrossFrame Suite routes explicit Chinese reader replies, editor responses, consultation-style short answers, or boundary-aware structural advice.
Use when explicit CrossFrame work needs a Chinese critical insight essay, commentary, concept essay, public piece, or structure-to-article draft after diagnosis.
Use when CrossFrame Suite routes explicit Chinese notes for books, theories, articles, excerpts, bidirectional reading, absorption, or conflict mapping.
| name | kubestellar-console |
| description | Multi-cluster Kubernetes dashboard with AI-powered operations via MCP server and 10+ built-in agent skills |
| category | devops |
| risk | critical |
| source | community |
| source_repo | kubestellar/console |
| source_type | community |
| date_added | 2026-04-27 |
| author | kubestellar |
| tags | ["kubernetes","multi-cluster","mcp","dashboard","cncf","devops","observability"] |
| tools | ["claude","cursor","gemini","codex"] |
| license | Apache-2.0 |
| license_source | https://github.com/kubestellar/console/blob/main/LICENSE |
| plugin | {"setup":{"type":"manual","summary":"Requires kc-agent binary (brew tap kubestellar/tap && brew install kc-agent)","docs":"https://github.com/kubestellar/console#quick-start"}} |
KubeStellar Console is an open-source multi-cluster Kubernetes dashboard (CNCF project) with AI-powered operations. It ships with kc-agent, an MCP server that bridges coding agents to kubeconfig and Kubernetes APIs, plus 10+ built-in agent skills for development, testing, and operations.
brew tap kubestellar/tap && brew install kc-agent
kc-agent
This bridges the active kubeconfig context to any MCP-compatible coding agent. Do not start it from a cluster-admin or write-capable context unless the user explicitly accepts that risk.
The project ships with agent skills accessible via CLAUDE.md and AGENTS.md:
kc-agent bridges your active kubeconfig context to MCP-compatible agents. If that context carries cluster-admin, write permissions, or secret read access, agents inherit those capabilities.kc-agent uses. Start kc-agent only after switching KUBECONFIG/context to dedicated least-privilege credentials and verifying them.resources='*', because it includes sensitive objects such as Secrets. Prefer an explicit non-secret resource list and verify access before starting the MCP server:
kubectl create serviceaccount kc-agent -n default
kubectl create clusterrole kc-agent-readonly \
--verb=get,list,watch \
--resource=pods,services,deployments.apps,replicasets.apps,statefulsets.apps,daemonsets.apps,namespaces,nodes,events,configmaps
kubectl create clusterrolebinding kc-agent-readonly \
--clusterrole=kc-agent-readonly \
--serviceaccount=default:kc-agent
kubectl auth can-i get secrets --as=system:serviceaccount:default:kc-agent
kubectl auth can-i list pods --as=system:serviceaccount:default:kc-agent
can-i command must return no; the second should return yes. Then create or select a kubeconfig that actually authenticates as that ServiceAccount before running kc-agent.kc-agent on a public network without authentication.kc-agent) installed separately via Homebrew.