Skip to main content
Glama
tioan

arkkvm-mcp

by tioan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to arkkvm-mcp

No user-submitted related servers found.

    Related Servers

    • 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.
      -

    • 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
      -

    • kvm-auto-mcp

      mantis5x5
      A
      license
      A
      quality
      B
      maintenance
      Enables agents to remotely control IP-KVM devices such as GLKVM, PiKVM, and TinyPilot out-of-band using keyboard, mouse, HID, and power tools, with screenshot verification for each action.
      12
      24
      MIT

    • 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.
      11
      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
      -
    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.5/5.0

    Scored across 22 tools

    Disambiguation4/5

    Most tools map to distinct actions: input control (move_mouse, click, drag, scroll, type_text, press_keys), power, media mounting, and USB drive management are clearly separated. The only mild overlaps are mount_media_url vs mount_media_storage (differentiated by source) and status vs usb_drive_status (differentiated by scope), and the descriptions resolve both.

    Naming Consistency4/5

    Consistent snake_case everywhere, with predictable verb_noun patterns for the usb_drive_* and mount_media_* families. A few tools are bare nouns/verbs (screenshot, click, drag, scroll, power, status), which is a minor but readable deviation from a strict verb_noun convention.

    Tool Count4/5

    22 tools is on the heavier side, but the domain is genuinely broad (video capture, HID input, ATX power, virtual media, USB file transfer, status). Each tool covers a distinct operation rather than padding, though it sits near the upper comfortable bound.

    Completeness4/5

    Strong coverage of the KVM lifecycle: capture, input, power/WOL, media mount/list/unmount, and full USB-drive CRUD (status, attach, list, upload, download, delete), plus a raw rpc_call escape hatch for advanced/configuration methods. Minor gaps like clipboard or video-recording are largely reachable via rpc_call.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources