Kvm Pilot MCP Server

What the code does

We read the source, 7 d ago · rules 995398eba69f

A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.

        listed = subprocess.run(  # nosec B603 B607 - fixed args, no shell; gh from PATH is intentional

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

            proc = subprocess.run(  # nosec B603 - fixed argv from config, shell=False

        env = dict(os.environ)

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add kvm-pilot -- uvx kvm-pilot

{
  "mcpServers": {
    "kvm-pilot": {
      "command": "uvx",
      "args": [
        "kvm-pilot"
      ]
    }
  }
}

[mcp_servers.kvm-pilot]
command = "uvx"
args = ["kvm-pilot"]

{
  "mcpServers": {
    "kvm-pilot": {
      "command": "uvx",
      "args": [
        "kvm-pilot"
      ]
    }
  }
}

{
  "servers": {
    "kvm-pilot": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "kvm-pilot"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: KVM_PILOT_PROFILE (Profile name from ~/.config/kvm-pilot/config.toml naming the KVM/BMC to target), KVM_PILOT_MCP_READ_ONLY (Least-privilege posture: only read-only tools are registered; effect gates force-closed. Recommended for first contact (set to 1)), KVM_PILOT_MCP_DRY_RUN (Rehearsal posture: destructive calls are logged, never sent (set to 1)), KVM_PILOT_MCP_ALLOW_POWER (Operator opt-in enabling power control of the managed host (per-effect gate; see also _ALLOW_HID, _ALLOW_MEDIA, _ALLOW_SSH, _ALLOW_APPLIANCE, _ALLOW_EXTERNAL_WRITE)), KVM_PILOT_HOST (Device address (KVM/BMC) when not using a config-file profile), KVM_PILOT_USER (Device username when not using a config-file profile), KVM_PILOT_PASSWD (Device password when not using a config-file profile (KVM_PILOT_HOST / KVM_PILOT_USER accompany it)), ANTHROPIC_API_KEY (Optional: enables server-side vision for classify_screen / wait_for_state; without it, classification falls back to the calling agent).