AI assistants

​

How it works

• Your clusters. Every context in your kubeconfig, as on the start screen.
• Your credentials. Lumovi reads and changes clusters with the credentials in your kubeconfig, so an assistant can’t see or do more than your account can. See Permissions.
• Your guard rails. Read-only clusters stay read-only, and each change waits for you, unless you let a cluster’s assistants make some changes without asking.

​

What assistants can do

• See a Secret’s values. They get its keys, and (hidden by Lumovi) for each value.
• Change a read-only cluster, or one whose Changes they ask for is set to Never.
• Go past your RBAC. A change your account can’t make fails at the dry run, before you’re asked.
• Delete without asking. Deletions always wait for you, and some ask you to type the name first.
• Anything else. They have only Lumovi’s tools: no shells, port forwards or Helm.

​

Turn it on

• Choose AI assistants, the sparkles at the bottom of the sidebar. It has a green dot while an assistant is connected.
• On the start screen, choose the same button at the bottom, next to the theme.
• Choose AI assistants… in the command palette (⌘K, or CtrlK on Windows and Linux).
• Choose View → AI Assistants…

• They read: Clusters’ objects, events and logs, and what’s failing; never Secrets’ values.
• They ask: Each change shows here, with the diff it makes, for you to approve or reject.
• Only on this computer: With a token of its own. Read-only clusters, and your own access (RBAC), always apply.

Listening at http://127.0.0.1:47830/mcp

​

The port

Lumovi can’t use port 47830 (listen EADDRINUSE: …): choose another one.

​

Connect an assistant

claude mcp add --transport http --scope user lumovi http://127.0.0.1:47830/mcp --header "Authorization: Bearer <token>"

"lumovi": {
  "command": "/Applications/Lumovi.app/Contents/MacOS/Lumovi",
  "args": ["--mcp-stdio=/Users/you/Library/Application Support/Lumovi"]
}

"lumovi": {
  "command": "C:\\Users\\you\\AppData\\Local\\Programs\\Lumovi\\Lumovi.exe",
  "args": [
    "C:\\Users\\you\\AppData\\Local\\Programs\\Lumovi\\resources\\app.asar.unpacked\\out\\mcp-stdio\\bridge.cjs",
    "C:\\Users\\you\\AppData\\Roaming\\Lumovi"
  ],
  "env": { "ELECTRON_RUN_AS_NODE": "1" }
}

{
  "mcpServers": {
    "lumovi": {
      "url": "http://127.0.0.1:47830/mcp",
      "headers": {
        "Authorization": "Bearer <token>"
      }
    }
  }
}

​

Connected now

​

A new token

​

Security

• Only on this computer. Lumovi listens on 127.0.0.1, which other computers can’t reach.
• Only with the token. Every request has to carry it, as Authorization: Bearer <token>. It’s 43 random characters, made the first time you turn assistants on, and Lumovi compares it in constant time. A request without it gets “Lumovi needs its token: set this assistant up again from Lumovi.”
• Not from web pages. A browser marks the requests a page makes with an Origin header, and Lumovi refuses them: “Web pages may not connect to Lumovi.” A page that points a name of its own at your computer (DNS rebinding) sends that name as the Host, and is refused too: “Only this computer may connect.” Only requests addressed to 127.0.0.1 or localhost, at Lumovi’s port, get in.
• Small messages. A message is at most 4 MB. A larger one gets “That’s more than Lumovi takes: 4 MB at most.” Only /mcp answers.
• Kept where only you can read it. The token is in Lumovi’s settings.json, with what each cluster lets assistants change. On macOS and Linux, Lumovi keeps that file readable by your account only. See Privacy and security.