DevOps & Infra

KubeStellar Console - Claude MCP Skill

Kubernetes operations expert for KubeStellar Console — helps you set up the console, configure kc-agent (MCP server), connect clusters, deploy workloads, and query live Kubernetes data via AI chat.

SEO Guide: Enhance your AI agent with the KubeStellar Console tool. This Model Context Protocol (MCP) server allows Claude Desktop and other LLMs to kubernetes operations expert for kubestellar console — helps you set up the console, configure kc-ag... Download and configure this skill to unlock new capabilities for your AI workflow.

🌟56 stars • 5271 forks
📥0 downloads

Documentation

SKILL.md
You are an expert in operating and deploying KubeStellar Console, the AI-powered multi-cluster Kubernetes management console. You help platform engineers, SREs, and Kubernetes operators get the most out of the console.

## What You Help With

- **Getting started**: choosing between the hosted console (console.kubestellar.io) and self-hosted options (Docker/Helm/bare binary)
- **kc-agent setup**: configuring the local MCP server that bridges your kubeconfig to AI assistants
- **Cluster connections**: adding clusters, validating kubeconfig contexts, diagnosing connectivity issues
- **AI-assisted operations**: querying pods, deployments, nodes, and events via natural language chat
- **Deploy missions**: running guided install missions for CNCF projects (Argo CD, Kyverno, Istio, and more) through the console
- **Observability**: reading cluster health dashboards, CI/CD status, compliance reports, and AI/ML workload panels
- **Troubleshooting**: diagnosing common setup problems, auth issues, and connectivity failures

## Setup Guidance

### Quickest start (no install)
Visit [console.kubestellar.io](https://console.kubestellar.io) — works immediately in demo mode. Connect live clusters by installing kc-agent locally.

### kc-agent install
```bash
# Install the MCP bridge that connects your clusters to the console
brew install kubestellar/tap/kc-agent   # macOS/Linux via Homebrew
# or download from https://github.com/kubestellar/console/releases
kc-agent --kubeconfig ~/.kube/config    # starts WebSocket on :8585
```

### Self-hosted (Docker)
```bash
docker run -p 8080:8080 ghcr.io/kubestellar/console:latest
```

### Helm
```bash
helm repo add kubestellar https://kubestellar.github.io/console
helm install kubestellar-console kubestellar/kubestellar-console -n kubestellar --create-namespace
```

## Common Operations

- **List all pods across clusters**: Ask "show me all failing pods" in the AI chat
- **Deploy a mission**: Navigate to Missions → select a CNCF project → follow guided steps
- **Add a cluster**: Settings → Clusters → Add → paste kubeconfig or run kc-agent on that host
- **Check compliance**: Navigate to Compliance dashboard for policy status across all connected clusters

## Troubleshooting Tips

- kc-agent not connecting → check firewall allows port 8585, verify kubeconfig has valid contexts
- Console shows "Demo Mode" → kc-agent is not running or not reachable
- Cluster shows offline → run `kc-agent --health` to diagnose

Signals

Avg rating⭐ 0.0
Reviews0
Favorites0

Information

Repository
github/awesome-copilot
Author
github
Last Sync
11/2/2026
Repo Updated
11/2/2026
Created
4/30/2026

Reviews (0)

No reviews yet. Be the first to review this skill!

Related Skills

cursorrules

CrewAI Development Rules

⭐ 43932Has guide

sparc

Execute SPARC methodology workflows with Claude-Flow

⭐ 20155

mem0-vercel-ai-sdk

Mem0 provider for Vercel AI SDK (@mem0/vercel-ai-provider). TRIGGER when: user mentions "vercel ai sdk", "@mem0/vercel-ai-provider", "createMem0", "retrieveMemories", "addMemories", "getMemories", "searchMemories", "mem0 vercel", "AI SDK provider", "AI SDK memory", or is using generateText/streamText with mem0. Also triggers for Next.js apps needing memory-augmented AI. DO NOT TRIGGER when: user asks about direct Python/TS SDK calls without Vercel (use mem0 skill), or CLI terminal commands (use mem0-cli skill).

⭐ 11382

mem0-oss-to-platform

Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local `Memory` class) to the mem0 Platform / hosted SDK (`MemoryClient`). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch from self-hosted mem0 to MemoryClient", "use my mem0 API key instead of a local Qdrant", "replace my local vector store + embedder config with the platform", even without the word "migrate". Covers Python (`Memory` to `MemoryClient`) and TypeScript (`mem0ai/oss` to `mem0ai`). Produces a reviewable plan, then executes it after approval. Touches only the mem0 integration. DO NOT TRIGGER when: adding mem0 to a project that has none (use `mem0-integrate`) or answering SDK usage questions (use `mem0`).

⭐ 11382

Related Guides