kvm-auto-mcp
Related Servers
Alternatives to kvm-auto-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables pixel-accurate mouse control, full keyboard and Unicode typing, screenshot capture, and an OCR element tree with bounding boxes on a remote GLKVM/PiKVM target, driven over its HTTPS API with no agent installed on the machine. It also detects concurrent human input and offers opt-in USB mass-storage file push/pull.1AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceGives AI agents full keyboard, mouse, and screen access to a physical PC via a KVM server and OCR.5MIT
- FlicenseAqualityDmaintenanceEnables AI assistants to remotely control Sipeed NanoKVM hardware for BIOS-level management of servers and headless machines. It provides tools for power control, keyboard and mouse emulation, screen capture, and ISO image mounting via the Model Context Protocol.1914-
- AlicenseAqualityBmaintenanceLets AI agents see and operate a physical computer below the OS level over WebRTC, from BIOS/UEFI and boot menus to installers and login screens. Provides HDMI screenshots, USB keyboard and mouse input, ATX power and Wake-on-LAN control, and virtual media such as CD-ROM images, disks, and a file-transfer USB drive.22MIT
- FlicenseNot gradedqualityBmaintenanceEnables MCP clients to remotely control a real retro or legacy computer, including keyboard and mouse input, video capture, audio, power cycling, and file transfer, so agents can run tests against physical hardware.5-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to control remote desktops through screen capture, mouse movement, and keyboard input.MIT
TDQS
Scored across 12 tools
Most tools target clearly distinct actions (device selection, status, screenshots, individual input types, power), but kvm_wait and kvm_screenshot both return screenshots and could be confused if an agent does not read the timing distinction carefully. The other input tools are well-separated by their descriptions.
All tools share the kvm_ prefix and use lowercase snake_case, which provides a predictable family identity. However, some names are verb-led (wait, paste, keystroke) while others are noun-led (status, screenshot, mouse, atx), making the pattern slightly inconsistent.
Twelve tools is well within the ideal range and each tool maps to a necessary KVM workflow: device selection, status/screenshot, keyboard/mouse input, HID configuration, and ATX power. Nothing feels redundant or missing enough to bloat the surface.
The surface covers the core KVM lifecycle well: select a device, inspect status, capture the screen, send text/keys/mouse input, and control power. Minor gaps exist such as file transfer or remote media mounting, but for a KVM-focused server the main operational needs are addressed.