Skip to main content
Glama
mantis5x5

kvm-auto-mcp

by mantis5x5
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to kvm-auto-mcp

No user-submitted related servers found.

    Related Servers

    • NanoKVM MCP Server

      scgreenhalgh
      F
      license
      A
      quality
      D
      maintenance
      Enables 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.
      19
      13
      -

    • vcctrl-mcp

      ecliptik
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      -

    • rustdesk-mcp-bridge

      jeremiejt38
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to control remote desktops through screen capture, mouse movement, and keyboard input.
      MIT

    • kvmhelm

      PaulFreund
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables computer-use clients to control KVM devices via MCP tools for listing, opening, viewing, and controlling remote computers with low-latency video and input.
      -

    • mcp-incus-vm

      RAGton
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to control and automate Incus/QEMU virtual machines via SSH, supporting mouse/keyboard, screenshots, commands, and lifecycle management.
      MIT
    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.7/5.0

    Scored across 12 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources