kvm-pilot
Related Servers
Alternatives to kvm-pilot
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP 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.22MIT
- AlicenseCqualityDmaintenanceThis MCP server connects AI agents to a PiKVM device, enabling full keyboard, mouse, and screen control of a physical machine without emulation.285GPL 3.0
- AlicenseNot gradedqualityCmaintenanceAn MCP server that gives AI agents direct control over QEMU virtual machines.31 npm1MIT
- FlicenseAqualityDmaintenanceMCP 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-
- AlicenseAqualityFmaintenanceAn MCP server that lets AI agents manage virtual machines across local and cloud targets, with tools to create machines, run commands, transfer files, and clean up ephemeral instances via natural language.1115 npmApache 2.0
- AlicenseNot gradedqualityDmaintenanceAn 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
TDQS
Scored across 34 tools
Tools mostly occupy distinct resource/action slots: power vs wake vs ctrl_alt_delete vs appliance_reboot are clearly separated, and screen/log diagnostics are explained by purpose. Some read-only meta tools (healthcheck/support_matrix/capabilities/session) and logs/events require careful reading, but descriptions provide boundaries.
All names are snake_case, but the set mixes noun-only names (info, logs, snapshot, power, events) with verb_noun names (set_boot_device, mount_iso, wait_for_state). It remains readable and domain-predictable, though not a single consistent pattern.
34 tools is above the 25-tool threshold and a lot for an agent to navigate; while many are specialized safety/diagnostic operations, several meta/diagnostic tools could be consolidated. The scope is broad, but the surface feels heavy.
Covers identification, health/capabilities, power, boot override, screen/HID, virtual media, SSH, appliance recovery, logs/events, firmware currency, and external report filing. Minor gaps remain (e.g., no firmware update action, no AMT disable, limited appliance lifecycle), but core operational workflows are present.