Official Homebrew tap for KubeStellar tools.
brew tap kubestellar/tap
# Install the local agent (bridges browser to kubeconfig and Claude Code)
brew install kc-agent
# Install KubeStellar operational tools
brew install kubestellar-ops
brew install kubestellar-deploy| Tool | Homebrew status | Notes |
|---|---|---|
kc-agent |
✅ Available | Install with brew install kc-agent |
kubestellar-ops |
✅ Available | Install with brew install kubestellar-ops |
kubestellar-deploy |
✅ Available | Install with brew install kubestellar-deploy |
kubectl-claude |
❌ Not planned | Use binary releases from kubestellar/kubestellar-mcp instead |
kubestellar-console |
❌ Not planned | Use the quick-start script or install from source instead |
kubectl-claude is not published as a Homebrew formula in this tap today.
The upstream project now lives at
kubestellar/kubestellar-mcp
and ships the two supported binaries you can install from this tap right now:
brew tap kubestellar/tap
brew install kubestellar-ops kubestellar-deploy
brew install kubestellar/tap/kubectl-claudeis not planned. Use binary releases fromkubestellar/kubestellar-mcp, the formulas above, or the Claude Code plugins below.
kubestellar-ops— multi-cluster diagnostics, RBAC analysis, and security checkskubestellar-deploy— app-centric deployment, GitOps, Helm, and rollout workflows
# Inspect clusters from your current kubeconfig
kubestellar-ops clusters list
kubestellar-ops clusters health
# Run the deployment tool as an MCP server for Claude Code
kubestellar-deploy --mcp-server- The CLI tools use your current kubeconfig by default.
- Set
KUBECONFIGif you want to use a non-default config file. - No separate API key is required for the binaries themselves.
export KUBECONFIG=$HOME/.kube/configIf you want the Claude Code marketplace workflow mentioned above, add the KubeStellar marketplace and install the plugins explicitly:
/plugin marketplace add kubestellar/claude-plugins
/plugin install kubestellar-ops
/plugin install kubestellar-deploy
/mcp
After /mcp, you should see both plugins connected.
- Audit cluster health, pod issues, and warning events across clusters
- Inspect RBAC permissions and security misconfigurations
- Deploy or update an app across multiple clusters
- Run Helm or GitOps workflows through Claude Code
If you prefer to install from source, follow the upstream project:
git clone https://github.com/kubestellar/kubestellar-mcp.git
cd kubestellar-mcp
go build -o bin/kubestellar-ops ./cmd/kubestellar-ops
go build -o bin/kubestellar-deploy ./cmd/kubestellar-deploy
sudo mv bin/kubestellar-* /usr/local/bin/See the upstream repository for releases and full documentation: https://github.com/kubestellar/kubestellar-mcp
Multi-cluster Kubernetes management console with built-in AI support.
Note: A
kubestellar-consoleHomebrew formula is not planned. Use the quick-start script below or install from source.
curl -sSL https://raw.githubusercontent.com/kubestellar/console/main/start.sh | bashThis downloads and runs the pre-built KubeStellar Console binary, starts kc-agent as a background daemon, and opens your browser automatically. Press Ctrl+C to stop the console (kc-agent continues in background).
| Environment Variable | Description | Default |
|---|---|---|
KC_CONSOLE_PORT |
Console server port | 8080 |
KC_DATA_DIR |
Data directory for PID files, logs, .env | ~/.kubestellar-console |
GITHUB_CLIENT_ID |
GitHub OAuth client ID (optional) | (none) |
GITHUB_CLIENT_SECRET |
GitHub OAuth client secret (optional) | (none) |
To enable GitHub OAuth login, create ~/.kubestellar-console/.env:
GITHUB_CLIENT_ID=your-client-id
GITHUB_CLIENT_SECRET=your-client-secretLocal agent for KubeStellar Console - bridges your browser to your kubeconfig and Claude Code CLI.
brew tap kubestellar/tap
brew install kc-agent# Start the agent (runs on localhost:8585)
kc-agent| Environment Variable | Description | Default |
|---|---|---|
KC_ALLOWED_ORIGINS |
Comma-separated list of allowed origins for CORS | localhost only |
KC_AGENT_TOKEN |
Optional shared secret for authentication | (none) |
If you're running the console on a custom domain:
# Single origin
KC_ALLOWED_ORIGINS="https://my-console.example.com" kc-agent
# Multiple origins
KC_ALLOWED_ORIGINS="https://console1.example.com,https://console2.example.com" kc-agent- Origin Validation: Only allows connections from configured origins
- Localhost Only: Binds to
127.0.0.1- not accessible from other machines - Optional Token Auth: Can require a shared secret via
KC_AGENT_TOKEN - Command Allowlist: Only permits safe kubectl commands
If brew install/brew upgrade is broken for any formula in this tap, start here:
- Formula Rollback Runbook — detection, triage, rollback, and user self-service recovery steps
- CI / Scheduled-Scan Failure Detection Runbook — how to notice and triage a failing
brew-ci.yml,validate-formulae.yml,codeql.yml, orscorecard.ymlrun today, before any automated alert exists - Scheduled Workflow Failure Runbook — what to do once a maintainer applies the proposed
workflow_run-based failure-alert workflow - SLOs/SLIs — CI health targets and detection/mitigation time budgets
- File an incident report
- Postmortem template — for incidents exceeding the mitigation budget or affecting more than a handful of users
Apache License 2.0