MCP and the AI agent

kcore has two ways to let a model work on a cluster. Both use the same tools and the same rule: the model asks questions, shows a plan, and changes nothing until a person says yes.

The rule: ask, plan, apply

  1. kcore_advise returns the questions an operator still has to answer: image URL, checksum, network, SSH key, node, disk. The model must put them to you. It does not guess.
  2. kcore_plan shows the diff against the controller: create, update, or refused because a field is immutable.
  3. kcore_apply, kcore_delete, and kcore_operation run only after you approve. Apply is an upsert: it creates what is missing, updates mutable fields, and rejects immutable changes.

Node installs partition disks. They need the exact phrase wipe the selected disks in the spec, typed by the operator.

Tools

ToolWhat it does
kcore_catalogResource kinds and which fields can change.
kcore_adviseQuestions to ask before a change. Read-only.
kcore_planLocal diff, plus a controller read.
kcore_applyDeclarative apply after confirm: true.
kcore_readGet and describe calls.
kcore_deleteDelete, or cancel a cluster update that has not finished.
kcore_operationPower, migrate, drain, cordon, approve a node, set the cluster version (canary by default), approve, promote, cancel, or roll back an update, install a node.
kcore_rpcAny unary controller, node agent, Provisioning, or Vault RPC. Calls that are not a get, list, classify, check, or plan need confirm: true.

With kcore_rpc the same assistant that creates a VM can list a Provisioning machine, read a Vault inventory, or start a restore, with the same approval step.

kcore MCP in an editor

The server runs on your machine over stdio and reads ~/.kcore/config, the file kctl uses. It presents your client certificate to the controller, so the roles you have are the roles the model has. It can also bootstrap a first cluster, writing the CA, controller certificate, and client certificate into ~/.kcore.

{
  "mcpServers": {
    "kcore": {
      "command": "npx",
      "args": ["-y", "kcore-mcp"]
    }
  }
}

Needs Node.js 20 or newer. KCORE_CONFIG points at another config file. KCORE_PROVISIONING sets the default Provisioning address. The Vault address defaults to 127.0.0.1:9191. The same server ships as a Cursor plugin with an operator skill that tells the agent to ask, plan, then apply, and as a VS Code extension for Copilot agent mode.

kctl agent

kctl agent
kctl agent --role read-only
kctl agent --role vm-admin --port 8123 --no-browser

A browser tab opens on 127.0.0.1. Sessions are on the left, the chat is in the middle, and each tool call is a card. A change shows an approval card with the exact request. You can approve, decline, or stop. You can say “create a VM for the build runner”, and the agent asks for the image, network, and key in a form with pick lists filled from the cluster.

What keeps it safe

Limits