Skip to main content
Glama
onprem-ai

asus-ipmi-mcp

by onprem-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to asus-ipmi-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
      14
      -

    • kvm-pilot

      DustinTrap
      A
      license
      A
      quality
      A
      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
      83 PyPI
      9
      Apache 2.0

    • arkkvm-mcp

      tioan
      A
      license
      A
      quality
      B
      maintenance
      Lets 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.
      22
      MIT

    • NanoKVM MCP Server

      raymatos
      F
      license
      A
      quality
      D
      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
      -

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

    B3.4/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool maps to a clearly distinct action or resource: individual mouse primitives (click, move_mouse, drag, scroll), keyboard primitives (type_text, press_keys), screen observation (screenshot, wait_for_screen_change), and read-only BMC queries (kvm_status, system_info, sensors, media_status, firmware_check_update). The only near-overlap is screenshot vs wait_for_screen_change, but the blocking semantics make the boundary explicit.

    Naming Consistency4/5

    Action tools consistently use verb_noun or single verbs (move_mouse, type_text, press_keys, wait_for_screen_change), while status tools use noun phrases (kvm_status, system_info, media_status). This split is predictable and readable, though bare names like drag, scroll, and screenshot break the pattern slightly.

    Tool Count5/5

    13 tools is well within the sweet spot and every tool covers a distinct capability of a KVM/IPMI interaction loop (observe, act, wait, query). Nothing feels redundant or padded.

    Completeness3/5

    Observation and input are fully covered, but core IPMI operations are missing: there is no power control (on/off/reset/cycle), and media_status is read-only with no tool to mount/unmount an ISO. An agent can drive the screen but cannot power-cycle the host or attach remote media, which are key BMC workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources