Skip to main content
Glama
DustinTrap

kvm-pilot

by DustinTrap
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to kvm-pilot

No user-submitted related servers found.

    Related Servers

    • jetkvm-mcp

      shvartzj1
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP 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.
      17
      MIT

    • NanoKVM MCP Server

      raymatos
      F
      license
      A
      quality
      C
      maintenance
      MCP 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
      -

    • smol-mcp

      smol-machines
      A
      license
      A
      quality
      F
      maintenance
      An 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.
      11
      3 npm
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 34 tools

    Disambiguation4/5

    Most tools have clearly distinct roles, and the descriptions actively cross-reference boundaries such as power_state/power/wake, logs/events, type_text/press_key/send_shortcut, and ssh_reachable/ssh_exec/appliance_status. The main residual ambiguity is the large read-only introspection cluster (info, healthcheck, capabilities, support_matrix, session, doctrine, access_paths) and the overlapping Ctrl+Alt+Del paths, though the descriptions mitigate this well.

    Naming Consistency3/5

    All names use snake_case, so the delimiter and casing are consistent. However the set mixes noun-only names (info, logs, snapshot, power_state, capabilities) with verb-oriented names (set_boot_device, mount_iso, ssh_exec) and inconsistent orderings such as firmware_check vs file_firmware_report and ssh_reachable vs ssh_discover.

    Tool Count2/5

    34 tools is well above the typical 3-15 range for a well-scoped MCP server. Many are read-only diagnostics or meta tools (info, healthcheck, capabilities, support_matrix, doctrine, session, access_paths, power_state, logs, events, boot_options, list_virtual_media, ssh_reachable, appliance_status, firmware_check) that could be consolidated or exposed through a more compact interface.

    Completeness4/5

    Core KVM lifecycle coverage is strong: identify/health/capabilities, power state/change/wake, boot options/set, HID typing/keys/mouse/calibration, virtual media list/mount/eject, SSH reachable/exec, appliance status/reboot, logs/events, and firmware check/report. Minor gaps remain, such as no virtual-media upload/delete management, no detailed BMC sensor view, and no serial-console tool for non-video devices.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources