A
licenseNot graded
qualityB
maintenanceMCP server that enables AI to see and control a physical computer via a JetKVM device for screen viewing, mouse/keyboard input, media mounting, and power management.
5
MIT
kvm-pilot
by DustinTrap
Related Servers
Alternatives to kvm-pilot
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceThis MCP server connects AI agents to a PiKVM device, enabling full keyboard, mouse, and screen control of a physical machine without emulation.283GPL 3.0
- AlicenseNot gradedqualityDmaintenanceAn MCP server that gives AI agents direct control over QEMU virtual machines.281MIT
- FlicenseAqualityCmaintenanceMCP server for controlling Sipeed NanoKVM devices, enabling remote hardware control via keyboard, mouse, power, and screenshots. It allows AI assistants like Claude to manage headless machines at the BIOS level.20-
- AlicenseNot gradedqualityCmaintenanceAn MCP server for managing home lab VMs and PNETLab topologies, enabling AI agents to power VMs, handle snapshots, and verify device configurations with explicit allowlists and confirmation gating.MIT
- AlicenseNot gradedqualityCmaintenanceA free, open-source MCP server that gives AI agents real filesystem, terminal, git, and process control over your machine for inspection, diagnosis, and repair.MIT
TDQS
A3.6/5.0
Scored across 34 tools
Disambiguation5/5
Each tool targets a distinct resource/action (read vs write, target vs appliance, HID vs media vs SSH), and descriptions explicitly cross-reference related tools (e.g., boot_options suggests allowable values for set_boot_device). Even the keyboard tools (type_text, press_key, send_shortcut, ctrl_alt_delete) are differentiated by granularity and effect gating. No two tools appear to do the same thing.
Naming Consistency3/5
Names mix bare nouns (info, logs, snapshot, doctrine), verb-noun phrases (classify_screen, set_boot_device, mount_iso), bare verbs (power, wake, eject), and prefix families (ssh_*, appliance_*). While each name is descriptive and prefixes provide loose grouping, there's no consistent verb_noun convention across the set, making the surface less predictable.
Tool Count2/5
With 34 tools, the set is well above the 'heavy' range (16–25). Although the KVM domain has many legitimate operations, several tools could be consolidated (e.g., keyboard input tools, multiple status readouts), and the high count increases agent cognitive load. It remains scoped to server management rather than being a generic grab-bag.
Completeness4/5
The tool set offers broad coverage of KVM management: power, boot device, screen capture, HID input, virtual media, SSH in-band, appliance maintenance, and firmware reporting. Read/write pairs are well represented (e.g., boot_options/set_boot_device, power_state/power). Minor gaps include no direct firmware update tool and no image management beyond mount/eject, but these are not dead ends.
Maintenance
ActivityActive
ResponsivenessResponsive