Kunobi Ninja MCP

MCP运维云端

提供方 kunobi-ninja · 包名 @kunobi/mcp

运维云端 stdio · 本地进程 无需鉴权 社区 / 第三方 ClaudeCursorWindsurf
查看接入方式

Kunobi是一个基于Rust和React构建的桌面IDE,专为平台工程而设计,提供实时集群可视化和AI辅助管理Kubernetes、FluxCD、ArgoCD和Helm的功能。

一句话选型结论

按资料字段整理

Kunobi Ninja MCP 属于运维云端类 MCP 服务器,stdio · 本地进程,无需鉴权,可直接接入 Claude、Cursor、Windsurf,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类运维云端 传输方式stdio · 本地进程 鉴权无需鉴权 部署方式本地部署
GitHub 星标 1 仓库热度,无公开仓库时显示未标注
工具数 4 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

运维云端
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量4暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

Kubernetes管理TypeScript本地部署平台工程AI辅助实时可视化FluxCD支持ArgoCD支持

安装与配置

stdio · 本地进程 无需鉴权
客户端在本机拉起子进程,数据不出本机
npx @kunobi/mcp --install

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后客户端会列出约 4 个工具,随便调一个只读工具确认能返回结果。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
云资源查询

查实例、存储、账单等云上资源状态。

部署与发布

把部署、重启、回滚这类操作接进对话。

监控与告警

拉取监控指标,异常时让模型帮你判断。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 资料标注 4 个工具,职责相对集中,接入后不容易误操作。
  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude、Cursor、Windsurf,换客户端不用重新研究配置。
  • 资料标注无需鉴权,装好就能连。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在运维云端场景里让模型直接调用外部能力的人。
  • 已经在用 Claude、Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Kunobi Ninja MCP当前 4 stdio · 本地进程 本地部署 有 2026-05-17
lobehub 未标注 stdio · 本地进程 本地部署 有 2026-04-11
TrendRadar 未标注 stdio · 本地进程 本地部署 有 2026-04-13
Ui Tars Desktop 8a825770 未标注 stdio · 本地进程 本地部署 有 2026-05-17
ruflo 未标注 stdio · 本地进程 本地部署 有 2026-04-13
FastGPT 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

运维云端
字段来自项目仓库与公开索引,中文说明由本站标注
提供方kunobi-ninja上游标注的维护方 kunobi-ninja
分类运维云端本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式无需鉴权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时@kunobi/mcp · Node.js本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

7.9 KB
来自项目仓库与上游目录的原文,未做删改

@kunobi/mcp

MCP bridge to Kunobi, a desktop platform management IDE. AI assistants manage Kubernetes, FluxCD, ArgoCD, and Helm while users maintain real-time visual oversight.

What is Kunobi?

Kunobi is a desktop IDE for platform engineering — built with Rust and React, no Electron.

  • Real-time cluster visibility with resource browser, YAML editor, and embedded terminal
  • Native FluxCD, ArgoCD, and Helm support
  • Built-in MCP server for AI assistants (Claude Code, Cursor, Windsurf, Codex CLI, Gemini CLI, GitHub Copilot CLI)
  • Available on macOS, Windows, and Linux
  • No account required, no cloud dependency

Setup

Enable MCP in Kunobi under Settings > AI & MCP, then install:

Automatic (recommended)

Register with all your AI clients in one step:```bash
npx @kunobi/mcp --install


This interactively detects your installed AI clients and registers the server with them. Supported clients:

- **Claude Code** — project or user scope
- **Claude Desktop** — user scope
- **Cursor** — project or user scope
- **Windsurf** — project or user scope
- **Codex CLI** — project or user scope
- **Gemini CLI** — project or user scope
- **GitHub Copilot CLI** — user scope

To remove the server from all clients:```bash
npx @kunobi/mcp --uninstall

Updating

install pins your clients to an exact version (e.g. @kunobi/mcp@1.2.3) so each
launch runs from the npm cache instead of resolving latest from the registry on
every spawn — startup stays fast and can't stall on the network. When a newer
version is published, the server tells you on connect; apply it with:```bash
npx @kunobi/mcp upgrade


This re-pins every client where Kunobi is registered to the newest version and
warms the cache. **Restart your AI client** to load it (the new version takes
effect on the next start).

**Installed before pinning existed?** Pin your current version in place — no
upgrade, no registry call:```bash
npx @kunobi/mcp pin

If you ran an older build, the server also hints this on connect when it detects
an unpinned config. Silence the hint with MCP_KUNOBI_NO_PIN_HINT=1.

Prefer always-latest? Opt back out — each launch will resolve the newest
version again (slower startup, and can stall on the registry):```bash
npx @kunobi/mcp unpin


### Manual

If you prefer manual setup, add the following to your client's MCP config:```json
{
  "mcpServers": {
    "kunobi": {
      "command": "npx",
      "args": ["-y", "@kunobi/mcp"]
    }
  }
}

How it works```

AI assistant <--stdio--> @kunobi/mcp <--HTTP--> Kunobi variants
│
├── keeps one MCP connection per configured variant
├── retries disconnected variants every 5s
└── manages one bundler per variant


The server keeps a persistent MCP connection for each configured Kunobi variant. When a variant is available, its tools are registered with a `variant__` prefix (e.g., `dev__list_clusters`, `stable__query_store`). When a variant briefly drops, the hub keeps the last-known surface stable while it reconnects in the background. If the disconnect outlives the reconnect grace window, the stale registrations are removed.

### Multi-variant support

Kunobi ships multiple release channels that run on different ports. This MCP server discovers all of them simultaneously:

| Variant  | Default port | Tool prefix    |
|----------|--------------|----------------|
| legacy   | 3030         | `legacy__`     |
| stable   | 3200         | `stable__`     |
| unstable | 3300         | `unstable__`   |
| dev      | 3400         | `dev__`        |
| local    | 3500         | `local__`      |
| e2e      | 3600         | `e2e__`        |

These defaults are auto-generated into `~/.config/kunobi/mcp.json` on first run. You can add custom variants or change ports — see Configuration.

### Built-in tools

These are always available, even when no Kunobi instance is running:

- **`kunobi_status`** — reports all variant connection states, ports, and tool counts
- **`kunobi_launch`** — launches a Kunobi variant by name
- **`kunobi_refresh`** — forces an immediate reconnect attempt across all configured variants
- **`kunobi_call`** — stable entrypoint for variant tools (`variant`, `tool`, `arguments`)

### Recommended calling pattern

Use the stable path below for the most reliable MCP client behavior:

1. Call `kunobi_status`
2. Read `kunobi://tools` to discover full downstream tool schemas and metadata
3. Execute via `kunobi_call(variant, tool, arguments)`

### Dynamic tools

When a Kunobi variant is detected, its tools appear automatically with a variant prefix. For example, if `dev` and `stable` are both running:

- `dev__app_info`, `dev__query_store`, `dev__list_stores`, ...
- `stable__app_info`, `stable__query_store`, `stable__list_stores`, ...

Tools appear dynamically as variants start, and they are withdrawn only after a sustained disconnect — no MCP server restart needed.

These dynamic `variant__tool` entries are still supported, but some MCP clients may not refresh dynamic tool lists reliably. Use `kunobi_call` as the primary path when in doubt.

### Resources

Resources exposed by Kunobi variants are proxied through automatically. When a variant connects, its resources become available to the AI client with variant-namespaced URIs to avoid collisions between multiple running variants.

The server also provides built-in resources:

- **`kunobi://status`** — JSON snapshot of all variant connection states, ports, and capability counts. Supports subscriptions — clients receive `notifications/resources/updated` whenever variants connect or disconnect.
- **`kunobi://tools`** — JSON discovery document listing each variant status plus full downstream tool, resource, and prompt metadata for `kunobi_call`.

### Prompts

Prompts from Kunobi variants are registered with a `variant__` prefix (e.g., `dev__setup_cluster`). They appear and disappear alongside their variant, just like tools.

## Configuration

### Config file

Variant-to-port mappings are stored in `~/.config/kunobi/mcp.json` (auto-generated on first run with defaults). You can edit this file directly or use the CLI:```bash
# List all configured variants and their connection status
kunobi-mcp list

# Add a custom variant
kunobi-mcp add juan 4200

# Remove a variant
kunobi-mcp remove juan

Environment variables

Env var Default Description
MCP_KUNOBI_RECONNECT_INTERVAL_MS 5000 Reconnect interval in ms
MCP_KUNOBI_VARIANTS — name:port pairs to merge (e.g., juan:4200,test:5000)
MCP_KUNOBI_AUTO_CONNECT true Set false to disable automatic background connections. kunobi_refresh still works for manual retries.
MCP_KUNOBI_NO_PIN_HINT — Set 1 to suppress the startup hint that suggests pinning an unpinned install.

Priority: config file defaults → MCP_KUNOBI_VARIANTS env var (merges on top).

CLI```

kunobi-mcp [command] [options]


| Command | Description |
|---------|-------------|
| `list` | Show configured variants and connection status |
| `add  ` | Add or update a variant |
| `remove ` | Remove a variant |
| `install` | Register this MCP server with your AI clients (pinned to the current version) |
| `uninstall` | Remove this MCP server from your AI clients |
| `pin` | Pin your AI clients to the current version (faster, hang-proof startup) |
| `unpin` | Revert to always-latest (`npx -y @kunobi/mcp`; slower startup) |
| `upgrade` | Re-pin your AI clients to the latest published version (restart to apply) |
| `--help`, `-h` | Show help message |
| `--version`, `-v` | Show version number |
| *(no command, piped)* | Start the stdio MCP server (used by AI clients) |

## Development```bash
pnpm install
pnpm build
pnpm test

For local development against @kunobi/mcp-bundler:bash pnpm dev:link # link local bundler pnpm dev:unlink # revert to npm version

License

Apache-2.0

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Kunobi Ninja MCP 怎么安装?

在客户端按下面的安装命令接入:npx @kunobi/mcp --install。对应的包名是 @kunobi/mcp。装完在客户端配置里引用同一个包或端点。

Kunobi Ninja MCP 怎么在 Claude、Cursor、Windsurf 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Kunobi Ninja MCP 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Kunobi Ninja MCP 需要 API Key 吗?

资料标注为无需认证,装好就能连;如果实际调用时报鉴权错误,按官方文档补上凭据。

Kunobi Ninja MCP 支持哪些客户端?

资料标注支持 Claude、Cursor、Windsurf;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Kunobi Ninja MCP 能提供哪些能力?

资料显示约 4 个工具;能力标签包括 Kubernetes管理、TypeScript、Claude。具体工具清单以官方文档为准。

Kunobi Ninja MCP 需要什么运行环境?

运行时为 Node.js;属于本地进程,需要在本机装好运行环境。

Kunobi Ninja MCP 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。