Kvm Pilot

Name: Kvm Pilot
Author: DustinTrap

by DustinTrapversion 1.0.1i★ –iRuns on your computer

Registry nameio.github.DustinTrap/kvm-pilot

Install

Overview

Description from the maker (original English)

Smart hands for your AI agents - write-capable KVM+BMC+SSH MCP server: gated, verified, audited.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other
You need to fill in: KVM_PILOT_PASSWD, ANTHROPIC_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: KVM_PILOT_PROFILE, KVM_PILOT_MCP_READ_ONLY, KVM_PILOT_MCP_DRY_RUN, KVM_PILOT_MCP_ALLOW_POWER, KVM_PILOT_HOST, KVM_PILOT_USER, KVM_PILOT_PASSWD, ANTHROPIC_API_KEY

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

PyPIPython’s uv installed (for the uvx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "kvm-pilot": {
      "command": "uvx",
      "args": [
        "kvm-pilot"
      ],
      "env": {
        "KVM_PILOT_PROFILE": "your-value",
        "KVM_PILOT_MCP_READ_ONLY": "your-value",
        "KVM_PILOT_MCP_DRY_RUN": "your-value",
        "KVM_PILOT_MCP_ALLOW_POWER": "your-value",
        "KVM_PILOT_HOST": "your-value",
        "KVM_PILOT_USER": "your-value",
        "KVM_PILOT_PASSWD": "your-value",
        "ANTHROPIC_API_KEY": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add kvm-pilot --env KVM_PILOT_PROFILE=your-value --env KVM_PILOT_MCP_READ_ONLY=your-value --env KVM_PILOT_MCP_DRY_RUN=your-value --env KVM_PILOT_MCP_ALLOW_POWER=your-value --env KVM_PILOT_HOST=your-value --env KVM_PILOT_USER=your-value --env KVM_PILOT_PASSWD=your-value --env ANTHROPIC_API_KEY=your-value -- uvx kvm-pilot

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "kvm-pilot": {
      "command": "uvx",
      "args": [
        "kvm-pilot"
      ],
      "env": {
        "KVM_PILOT_PROFILE": "your-value",
        "KVM_PILOT_MCP_READ_ONLY": "your-value",
        "KVM_PILOT_MCP_DRY_RUN": "your-value",
        "KVM_PILOT_MCP_ALLOW_POWER": "your-value",
        "KVM_PILOT_HOST": "your-value",
        "KVM_PILOT_USER": "your-value",
        "KVM_PILOT_PASSWD": "your-value",
        "ANTHROPIC_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "kvm-pilot": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "kvm-pilot"
      ],
      "env": {
        "KVM_PILOT_PROFILE": "your-value",
        "KVM_PILOT_MCP_READ_ONLY": "your-value",
        "KVM_PILOT_MCP_DRY_RUN": "your-value",
        "KVM_PILOT_MCP_ALLOW_POWER": "your-value",
        "KVM_PILOT_HOST": "your-value",
        "KVM_PILOT_USER": "your-value",
        "KVM_PILOT_PASSWD": "your-value",
        "ANTHROPIC_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

KVM_PILOT_PROFILE env
Profile name from ~/.config/kvm-pilot/config.toml naming the KVM/BMC to target
KVM_PILOT_MCP_READ_ONLY env
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 env
Rehearsal posture: destructive calls are logged, never sent (set to 1)
KVM_PILOT_MCP_ALLOW_POWER env
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 env
Device address (KVM/BMC) when not using a config-file profile
KVM_PILOT_USER env
Device username when not using a config-file profile
KVM_PILOT_PASSWD secret env
Device password when not using a config-file profile (KVM_PILOT_HOST / KVM_PILOT_USER accompany it)
ANTHROPIC_API_KEY secret env
Optional: enables server-side vision for classify_screen / wait_for_state; without it, classification falls back to the calling agent

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account DustinTrap, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32683 servers in this category
Published to the registry more recently than 72% of the other 32683 servers in this category
Basic checks equal to or better than 100% of the other 32683 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Kvm Pilot safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: KVM_PILOT_PASSWD, ANTHROPIC_API_KEY

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.1) reached the registry 15 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, MCP Server Autocad Lisp Helper

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago

Install

MCP Server Autocad Lisp Helper

by radwanalmsora

High-precision static analysis and debug server for AutoCAD AutoLISP (.lsp) files.

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

kvm-pilot

Smart hands for your AI agents. A write-capable, multi-plane (KVM + BMC + SSH) MCP server for controlling physical machines — gated, verified, audited.

kvm-pilot lets an agent drive a headless box through POST, firmware, the bootloader, and an OS install with no agent on the target: it works at the pixel level through an IP-KVM (PiKVM, the GL.iNet GLKVM fork GL-RM1 / GL-RM1PE, BliKVM), at the structured-state level through a BMC (Redfish on iDRAC/iLO/OpenBMC, IPMI on BMCs that predate Redfish), at the firmware level through Intel AMT/vPro (a BIOS/POST/GRUB screenshot + power + SOL on a business laptop an HDMI-capture KVM can't see boot on), and over SSH once an OS is up. A pluggable vision subsystem reads a KVM screenshot and tells you what boot phase the machine is in — bios_menu, grub_menu, installer_progress, login_prompt, crash_screen, and so on — and a safety layer gates every destructive operation behind operator opt-ins and per-call approvals.

Vision runs on Claude or any local OpenAI-compatible VLM (LM Studio, Ollama, vLLM, llama.cpp). Point it at a model on your own GPU and the screenshots never leave your network and cost nothing per frame.

How it works

kvm-pilot runs a see → decide → act loop, and the screen is its only sensor: it pulls a screenshot from the KVM, a vision model classifies the boot phase, and kvm-pilot acts back through the KVM's keyboard and power. Because it works at the pixel level, there is no agent on the target — the same loop drives POST, firmware, the bootloader, and an OS install.

A real, unedited run against a GLKVM on the home fleet — an honest preflight, a headless snapshot (watch it wake the on-demand encoder), a gated dry-run power-cycle, and the boot console the agent actually saw:

Quickstart

One install gives you the whole product — the `kvm-pilot` CLI, the `kvm-pilot-mcp` MCP server, and the bundled Claude skill — nothing to clone.

pip install kvm-pilot                          # CLI + skill + MCP server + WebSocket events

pip install "kvm-pilot[totp]" # + 2FA / TOTP support (pyotp) kvm-pilot install-skill # optional: put the bundled skill where Claude Code loads it

Driving a KVM from an AI agent (MCP)

claude mcp add kvm-pilot -s user \

-e KVM_PILOT_PROFILE=mykvm -e KVM_PILOT_MCP_READ_ONLY=1 -- \ kvm-pilot-mcp

KVM_PILOT_MCP_READ_ONLY=1 is the recommended first rung of the trust ladder — the agent can see everything and touch nothing until your hardware is verified. The Getting started guide covers credentials, Claude Desktop JSON config, sample prompts, and climbing the ladder. The server is published to the official MCP registry as `io.github.DustinTrap/kvm-pilot`, so registry-aware hosts can discover and install it by name. Agents: the repo root carries an llms.txt doc map.

Scripting from Python

from kvm_pilot import KVMClient

from kvm_pilot.vision import ScreenAnalyzer, make_backend

kvm = KVMClient("192.168.8.1", "admin", "secret")

Classify the current screen with Claude (model auto-resolved at runtime)

analyzer = ScreenAnalyzer(kvm, make_backend("anthropic")) print(analyzer.classify().phase)

Or run entirely on a local VLM — nothing leaves your network

local = make_backend("local", base_url="http://127.0.0.1:1234/v1", model="qwen2.5-vl-7b") analyzer = ScreenAnalyzer(kvm, local)

Block until the box reaches the GRUB menu, then pick the first entry

analyzer.wait_for_state("grub_menu", timeout=120) kvm.press_key("Enter")

For the latest unreleased tree:

pip install "kvm-pilot[totp] @ git+https://github.com/DustinTrap/kvm-pilot"

CLI

kvm-pilot info     --host 192.168.8.1 --user admin --ask-passwd   # prompt (no echo)

kvm-pilot capabilities --profile homelab # what this driver supports kvm-pilot snapshot screen.jpg --profile homelab kvm-pilot --timeout 60 power-cycle --profile homelab --dry-run # log, don't send kvm-pilot eject --profile homelab # detach virtual media kvm-pilot events --profile homelab --count 5 # stream device events kvm-pilot watch grub_menu --profile homelab \ --backend local --vision-url http://127.0.0.1:1234/v1 --vision-model qwen2.5-vl-7b

The CLI prompts for confirmation before any destructive action (power, virtual media — including uploads — keyboard/mouse injection, GPIO). Use --yes to skip prompts in automation, or --dry-run to log intended actions without sending them — dry-run short-circuits *before* the prompt, so it never blocks waiting for input. --timeout (HTTP per-request timeout) is a global flag and goes *before* the subcommand; watch keeps its own --timeout for the vision wait deadline.

Profiles like homelab live in ~/.config/kvm-pilot/config.toml. See docs/cli.md for the full command table (every subcommand, the capability it needs, and its gating), and docs/configuration.md for the config-file format, every KVM_PILOT_* environment variable, and the precedence between flags, env, and profiles.

GLKVM setup note: on GL.iNet firmware the PiKVM REST API is **disabled by

default** and a firmware upgrade can re-disable it — enable it first, per

Every /api/* call returns 404.

The tool surface, by plane

The same capability protocols span three actuation planes, so one agent workflow can mix pixels, structured BMC state, and shell access — with every destructive effect gated per class:

Plane	Read	Act (operator-gated)
KVM — pixels & HID (PiKVM · GLKVM · BliKVM)	`snapshot` · `classify_screen` · `wait_for_state` · `power_state` · `logs` · `list_virtual_media`	`power` · `type_text` / `press_key` / `send_shortcut` / `mouse` · `calibrate_mouse` · `mount_iso` / `eject`
BMC — structured state (Redfish · IPMI)	`info` · `boot_options` · `logs` (SEL) · sensors (CLI)	`power` · `set_boot_device` · SOL console (CLI `console`)
Firmware — Intel AMT/vPro (spans both planes)	`info` · `snapshot` (firmware BIOS/POST/GRUB) · `boot_options` · `power_state`	`power` · `set_boot_device` · `type`/`mouse` · SOL (`console`) · `amt_enable` (open SOL/KVM listeners)
SSH — in-band & appliance	`ssh_reachable` · `appliance_status` · `access_paths`	`ssh_exec` · `host_exec` (ssh/winrm auto-picked) · `wake` (WoL) · `appliance_reboot`
Meta — evidence & intake	`capabilities` · `support_matrix` · `healthcheck`	`file_firmware_report`

A machine with no KVM and no BMC at all is itself a first-class target: driver = "ssh" plus `ssh_host` (the machine's own address, #248) stands kvm-pilot on the recovery ladder's in-band rung — every device capability honestly absent, and the healthcheck saying plainly that there is no out-of-band recovery path there.

The canonical per-tool reference — annotations, effect gates, approval lifecycle — is the MCP server README; the CLI covers the full surface in docs/cli.md.

Status & maturity

Status: 1.0, general availability — on the strength of the run ledger,

not beyond it. Three device types have run live (GL-RM1PE, Dell R710 over

iDRAC6/IPMI, Dell Latitude 5411 over Intel AMT); three of the seven device

drivers (redfish, pikvm, blikvm) have only ever run against emulators.

See the

Hardware-Compatibility list

for what has actually been exercised — and please add to it. (The exact version lives in the

CHANGELOG.)

The core paths have graduated

from mocked-only to live-verified: a fleet of GL-RM1PE units has exercised

snapshot/healthcheck/logs/power_state/virtual_media/info across

two firmware lines — on V1.9.1 the run ledger that ships in the wheel puts

info/logs/healthcheck/power_state at ga, snapshot at rc, and

virtual_media at beta — derived from real runs, never hand-edited — and a Dell iDRAC6 has exercised the IPMI driver live end-to-end

(power, boot-device, sensors, event log, SOL serial console). The paths that

can hurt are hardened: transports never re-fire a destructive request, MCP

approvals are signed single-use receipts with an audit trail, and every

destructive effect — power, HID, media, boot-config, appliance, SSH,

external writes — has its own operator opt-in gate. Recent betas added

remote boot-device control (Redfish, IPMI, and in-band efibootmgr),

Wake-on-LAN, an IPMI driver for BMCs that predate Redfish, a serial (SOL)

console, mouse auto-calibration, and headless native-resolution GLKVM

snapshots; kvm-pilot test-report turns contributing evidence into one

command, and the firmware registry feeds itself (firmware-check auto-files

registry updates).

Now we need your hardware. PiKVM, BliKVM, other GLKVM models, and

Redfish BMCs (iDRAC/iLO/OpenBMC) are the combos the matrix needs most —

success *or* failure, a

hardware report

takes two minutes and the hourly ingest does the rest. Anything the

Hardware-Compatibility list

doesn't show as exercised is still unverified: the 1.x line keeps the public

API stable, but a rating only moves when a live run moves it; note the remote

firmware-flash no-op on GL-RM1PE

([#94](https://github.com/DustinTrap/kvm-pilot/issue

Only the beginning is shown; read the rest in the repo

Kvm Pilot

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

MCP Server Autocad Lisp Helper

README from the maker

kvm-pilot

How it works

Quickstart

Driving a KVM from an AI agent (MCP)

Scripting from Python

Classify the current screen with Claude (model auto-resolved at runtime)

Or run entirely on a local VLM — nothing leaves your network

Block until the box reaches the GRUB menu, then pick the first entry

CLI

The tool surface, by plane

Status & maturity