Skip to main content
Glama
raymatos

NanoKVM MCP Server

by raymatos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to NanoKVM MCP Server

No user-submitted related servers found.

    Related Servers

    • jetkvm-mcp

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

    • 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
      -
    • tinypilot-mcp by tiny-pilot

      tinypilot-mcpofficial

      tiny-pilot
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server that exposes fleet-aware KVM primitives for AI agents to control TinyPilot devices, including screen capture, keyboard input, mouse events, and device selection.
      MIT

    • kvm-pilot

      DustinTrap
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that gives AI agents smart hands for physical machines, controlling them via IP-KVM, BMC, and SSH with visual boot-phase classification and operator-gated actions.
      34
      53 PyPI
      6
      Apache 2.0

    • rustdesk-mcp

      zsunny6658
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that enables AI agents to control remote machines via RustDesk, supporting device management, remote shell commands, file operations, power controls, and screen interaction.
      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.9/5.0

    Scored across 20 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: power, video, HID, storage, and device info. Even similar actions like tap vs click are clearly differentiated by touchscreen vs mouse semantics.

    Naming Consistency4/5

    All tools share the nanokvm_ prefix and use snake_case, but patterns vary between verb_noun (mount_iso, send_text), bare verbs (power, tap), and nouns (info, hardware). The prefix and clear verb choices keep it readable.

    Tool Count4/5

    20 tools is on the higher end but justified for a full KVM feature set covering power, display, input, and ISO management. No redundant tools; each serves a unique purpose.

    Completeness4/5

    The surface covers core KVM operations: power control, HDMI status/reset, keyboard/mouse input, ISO mounting/unmounting, and screenshots. Minor gaps like individual keyboard layout per key send are not critical.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources