asus-ipmi-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ASUS_IPMI_HOST | Yes | Card IP / hostname | |
| ASUS_IPMI_USER | No | Card user (needs KVM privilege) | admin |
| ASUS_IPMI_PASSWORD | Yes | Card password | |
| ASUS_IPMI_ALLOW_MEDIA | No | 1 enables media_configure_share, media_mount, … | off |
| ASUS_IPMI_ALLOW_POWER | No | 1 enables power and set_boot_once | off |
| ASUS_IPMI_ALLOW_FIRMWARE | No | 1 enables firmware_prepare and firmware_flash (card firmware update) | off |
| ASUS_IPMI_SCREENSHOT_MAX | No | Long side of returned screenshots (pixels) | 1024 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| screenshotA | Returns the current host screen (via the IPMI card KVM). Wakes a blanked display by nudging the mouse. Optional crop region (screen pixels) to read small text. |
| wait_for_screen_changeA | Blocks until the host screen changes noticeably (or timeout), then returns a screenshot. Use after actions that take time (boot, install steps, page loads). |
| clickB | Clicks at absolute screen coordinates (pixels of the full host screen, see screenshot metadata). |
| move_mouseA | Moves the pointer to absolute screen coordinates (also wakes a sleeping display). |
| dragB | Press left button at (x1,y1), move to (x2,y2), release. |
| scrollC | Scrolls at a position. Positive amount scrolls up, negative down (wheel notches). |
| type_textA | Types text on the host keyboard (US layout; use \n for Enter, \t for Tab). Non-ASCII characters are not supported. Take a screenshot first: if the host locked its screen meanwhile, the text goes into the password field (a failed login). |
| press_keysB | Presses keys, e.g. "enter", "esc", "f2", "del", "tab", "up", "ctrl+alt+delete", "ctrl+alt+f3", "super", "alt+f4". Several can be given in order. |
| kvm_statusB | Connection state, screen resolution, whether the host display is blank, mouse mode, other KVM clients. |
| system_infoC | BMC firmware, host power state, host BIOS/model (via Redfish). |
| sensorsC | Temperatures, fans, voltages from the BMC (Redfish). |
| media_statusC | Remote-media settings (share), images found on the share, active redirections. |
| firmware_check_updateB | Compares the card firmware with the releases on the ASUS support page (version, date, SHA-256). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
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.
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.
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.
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.