A Model Context Protocol (MCP) server for managing Kubernetes clusters from MCP-compatible clients like Claude Desktop, Cursor, and Continue.
Kai MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. A Model Context Protocol (MCP) server for managing Kubernetes clusters from MCP-compatible clients like Claude Desktop, Cursor, and Continue.
Kai exposes Kubernetes operations as MCP tools, letting an LLM client manage your cluster through natural language — workloads, networking, config, storage, RBAC, custom resources, and raw manifests.
Once Kai is connected, these are the calls the assistant has available:
Networking — The Networking tool exposed by this serverConfiguration — The Configuration tool exposed by this serverStorage — The Storage tool exposed by this serverSecurity — The Security tool exposed by this serverUtilities — The Utilities tool exposed by this serverAdvanced — The Advanced tool exposed by this serverCursor — The Cursor tool exposed by this serverContinue — Add to your Continue configuration (~/.continue/config.json):The server connects to your current kubectl context by default. Ensure you have access to a Kubernetes cluster configured for kubectl (e.g., minikube, Rancher Desktop, kind, EKS, GKE, AKS).
cyclon/kai on a container image is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Among the file and storage access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Kai's toolset — Networking, Configuration, Storage and 5 more — is a fair guide to whether it matches your workflow. It is maintained by basebandit; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Networking | The Networking tool exposed by this server. |
| Configuration | The Configuration tool exposed by this server. |
| Storage | The Storage tool exposed by this server. |
| Security | The Security tool exposed by this server. |
| Utilities | The Utilities tool exposed by this server. |
| Advanced | The Advanced tool exposed by this server. |
| Cursor | The Cursor tool exposed by this server. |
| Continue | Add to your Continue configuration (~/.continue/config.json): |
Add the server configuration:
```json
{
"mcpServers": {
"kubernetes": {
"command": "/path/to/kai"
}
}
}Configuration as documented by the project. Restart the client after saving.
The server connects to your current kubectl context by default. Ensure you have access to a Kubernetes cluster configured for kubectl (e.g., minikube, Rancher Desktop, kind, EKS, GKE, AKS).
Scoped local file access — read, write, search and reorganise files in directories you explicitly allow.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Chat with your second brain — search, read and write vault notes through the Local REST API.
Connects AI models to an Obsidian knowledge base for direct access and manipulation of notes and folders.