@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)

• 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:

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

To remove the server from all clients:

npx @kunobi/mcp --uninstall

Manual

If you prefer manual setup, add the following to your client's MCP config:

{
  "mcpServers": {
    "kunobi": {
      "command": "npx",
      "args": ["-y", "@kunobi/mcp"]
    }
  }
}

How it works

AI assistant <--stdio--> @kunobi/mcp <--HTTP--> Kunobi variants
                          │
                          ├── scans ports every 5s
                          ├── confirms Kunobi identity via serverInfo
                          └── manages one bundler per variant

The server periodically probes known ports for running Kunobi instances. When a variant is detected, its tools are registered with a variant/ prefix (e.g., dev/list_clusters, stable/query_store). When a variant stops, its tools are automatically removed.

Multi-variant support

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

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

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 and disappear dynamically as variants start and stop — no MCP server restart needed.

Configuration

No configuration is required. The server scans all known ports automatically.

CLI

npx @kunobi/mcp [option]

Development

pnpm install
pnpm build
pnpm test

For local development against @kunobi/mcp-bundler:

pnpm dev:link    # link local bundler
pnpm dev:unlink  # revert to npm version

License

Apache-2.0