GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
作者提供的说明(英文原文)
AI-powered Kubernetes diagnostics, RBAC analysis, security checks, and app deployment via MCP
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
KUBECONFIG你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"kubestellar": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"KUBECONFIG",
"ghcr.io/kubestellar/kubestellar-mcp:0.9.22-nightly.20261103"
],
"env": {
"KUBECONFIG": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add kubestellar --env KUBECONFIG=your-value -- docker run -i --rm -e KUBECONFIG ghcr.io/kubestellar/kubestellar-mcp:0.9.22-nightly.20261103运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"kubestellar": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"KUBECONFIG",
"ghcr.io/kubestellar/kubestellar-mcp:0.9.22-nightly.20261103"
],
"env": {
"KUBECONFIG": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"kubestellar": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"KUBECONFIG",
"ghcr.io/kubestellar/kubestellar-mcp:0.9.22-nightly.20261103"
],
"env": {
"KUBECONFIG": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
KUBECONFIG env这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 kubestellar 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.9.22-nightly.20261103)于4天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Docker。
同一分类中有:GitHub, Desktop Commander, Cloudflare MCP
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
AI-powered multi-cluster Kubernetes tools for Claude Code.
Single-cluster UX for multi-cluster reality - work with your apps, not your clusters.
kubestellar-mcp is the AI entry point to the KubeStellar platform — a CNCF Sandbox ecosystem for multi-cluster Kubernetes orchestration.
| Sub-project | Role |
|---|---|
| kubestellar | Core engine — BindingPolicy, WDS, ITS, WEC workload propagation |
| console | Web dashboard — 300+ cards, AI missions, GPU and LLM-d monitoring |
| console-marketplace | 153+ community card presets (GPU/AI/ML, ArgoCD, OPA, Falco, security) |
| console-kb | AI knowledge base — community missions and operational runbooks |
| kubestellar-mcp | This repo — MCP server for Claude, Cursor, Windsurf, VS Code |
kubestellar-mcp lets AI agents inspect and operate clusters through natural language. For visual dashboards and AI missions, see KubeStellar Console.
| Binary | Description |
|---|---|
| kubestellar-ops | Multi-cluster diagnostics, RBAC analysis, security checks |
| kubestellar-deploy | App-centric deployment, GitOps, smart workload placement |
Additional documentation lives in docs/:
docs/index.md - expanded setup, plugin workflow, CLI usage, and operational guidancedocs/ARCHITECTURE.md - architecture overview and contributor guide for the two MCP servers, request lifecycle, and how to add new toolsIf you are contributing new MCP capabilities, start with docs/ARCHITECTURE.md; it is the best guide to how the servers are organized and where new tools should be added.
docs/slo.md - Service Level Objectives and Indicatorsdocs/alerts/ - importable Prometheus alert rules aligned with the SLOsdocs/dashboards/ - importable Grafana dashboardrunbooks/ - operational runbooks (startup/shutdown, cluster discovery failures, credential rotation, connectivity loss, release rollback)docs/postmortem-template.md - incident postmortem templatedocs/severity-levels.md - P1-P4 incident severity scale used by the incident template and postmortem requirementbrew tap kubestellar/tap
brew install kubestellar-ops
brew install kubestellar-deploy
brew install kubestellar-ops kubestellar-deploy
Download from GitHub Releases.
Prerequisites: Go 1.26+ (go version to verify)
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/
In Claude Code, run:
/plugin marketplace add kubestellar/claude-plugins
/plugin install kubestellar-ops
/plugin install kubestellar-deploy
Or:
/plugin → Marketplaces tab → click Update on kubestellar marketplace/plugin → Discover tab → Install kubestellar-ops and/or kubestellar-deployRun /mcp in Claude Code - you should see:
plugin:kubestellar-ops:kubestellar-ops · ✓ connected
plugin:kubestellar-deploy:kubestellar-deploy · ✓ connected
Add to ~/.claude/settings.json:
{
"permissions": { "allow": [ "mcp__plugin_kubestellar-ops_kubestellar-ops*", "mcpplugin_kubestellar-deploy_kubestellar-deploy__*" ] } }
Or run in Claude Code:
/allowed-tools add mcp__plugin_kubestellar-ops_kubestellar-ops__*
/allowed-tools add mcp__plugin_kubestellar-deploy_kubestellar-deploy__*
You can run either binary as a generic MCP stdio server with kubestellar-ops --mcp-server or kubestellar-deploy --mcp-server. Any MCP-compatible client can use the binary over stdio.
Create .vscode/mcp.json:
{
"servers": { "kubestellar-ops": { "command": "kubestellar-ops", "args": ["--mcp-server"] } } }
Create .cursor/mcp.json:
{
"mcpServers": { "kubestellar-ops": { "command": "kubestellar-ops", "args": ["--mcp-server"] } } }
Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": { "kubestellar-ops": { "command": "kubestellar-ops", "args": ["--mcp-server"] } } }
OpenCode is an open-source AI coding agent. Add the following to your project's opencode.json or opencode.jsonc:
{
"$schema": "https://opencode.ai/config.json", "mcp": { "kubestellar-ops": { "type": "local", "command": ["kubestellar-ops", "--mcp-server"], "enabled": true }, "kubestellar-deploy": { "type": "local", "command": ["kubestellar-deploy", "--mcp-server"], "enabled": true } } }
After adding, run opencode mcp list and verify both servers show as connected.
For your AI agent — Copy and paste this message into your OpenCode session to have it configure the MCP tools automatically:
`
Install kubestellar-ops and kubestellar-deploy:
# macOS — Homebrew
brew tap kubestellar/tap
brew install kubestellar-ops kubestellar-deploy
# Linux — download from GitHub Releases
curl -LO https://github.com/kubestellar/kubestellar-mcp/releases/latest/download/kubestellar-ops_linux_amd64.tar.gz
curl -LO https://github.com/kubestellar/kubestellar-mcp/releases/latest/download/kubestellar-deploy_linux_amd64.tar.gz
tar xzf kubestellar-ops_linux_amd64.tar.gz
tar xzf kubestellar-deploy_linux_amd64.tar.gz
sudo mv kubestellar-ops kubestellar-deploy /usr/local/bin/
# Or build from source (any OS, requires Go 1.26+)
git clone https://github.com/kubestellar/kubestellar-mcp.git
cd kubestellar-mcp
go build -o /usr/local/bin/kubestellar-ops ./cmd/kubestellar-ops
go build -o /usr/local/bin/kubestellar-deploy ./cmd/kubestellar-deploy
Then create opencode.jsonc in the project root with:
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"kubestellar-ops": {
"type": "local",
"command": ["kubestellar-ops", "--mcp-server"],
"enabled": true
},
"kubestellar-deploy": {
"type": "local",
"command": ["kubestellar-deploy", "--mcp-server"],
"enabled": true
}
}
}
Verify with: opencode mcp list
`
kubestellar-ops --mcp-server
kubestellar-deploy --mcp-server
The MCP binaries use your active kubeconfig by default. If you run them in-cluster, bind the same permissions to the pod ServiceAccount.
| Use case | Typical permissions |
|---|---|
| kubestellar-ops read-only | get, list, watch on namespaces, nodes, pods, pods/log, services, endpoints, deployments, replica sets, statefulsets, daemonsets, jobs, cronjobs, events, resourcequotas, limitranges, roles, rolebindings, clusterroles, and clusterrolebindings |
| kubestellar-deploy write | Everything above, plus create, update, patch, and delete on the resource types you plan to manage |
Example read-only ClusterRole:
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole metadata: name: kubestellar-mcp-readonly rules:
For write workflows, add create, update, patch, and delete to the resource rules you actually need.
which kubestellar-ops.kubectl auth can-i --list to see what your current identity can access.kubectl config current-context.KUBECONFIG is set and points to the kubeconfig file you expect.echo '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"capabilities":{}}}' | ./bin/kubestellar-ops --mcp-server
Update the CLI tools via Homebrew:
brew update
brew upgrade kubestellar-ops kubestellar-deploy
Update the plugins in Claude Code:
/plugin update kubestellar-ops
/plugin update kubestellar-deploy
Multi-cluster Kubernetes diagnostics, RBAC analysis, and security checks.
| Category | Tools |
|---|---|
| Cluster | list_clusters, get_cluster_health, get_nodes, audit_kubeconfig |
| Workloads | get_pods, get_deployments, get_services, get_events, describe_pod, get_pod_logs |
| RBAC | get_roles, get_cluster_roles, get_role_bindings, can_i, analyze_subject_permissions |
| Diagnostics | find_pod_issues, find_deployment_issues, check_resource_limits, check_security_issues |
| Gatekeeper | check_gatekeeper, install_ownership_policy, list_ownership_violations |
| Upgrades | detect_cluster_type, get_cluster_version_info, check_helm_release_upgrades |
| GitOps | detect_drift |
| Command | Description |
|---|---|
/k8s-health | Check health of all clusters |
/k8s-issues | Find pod and deployment issues |
/k8s-security | Check for security misconfigurations |
/k8s-rbac | Analyze RBAC permissions |
/k8s-analyze | Comprehensive namespace analysis |
/k8s-audit-kubeconfig | Audit kubeconfig clusters and recommend cleanup |
/k8s-ownership | Manage ownership tracking with OPA Gatekeeper |
/k8s-upgrade-check | Check for available upgrades |
/k8s-upgrade | Upgrade cluster (master and nodes) |
App-centric multi-cluster deployment and operations.
只显示了开头部分;其余内容请在仓库中阅读