NanoKVM MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NANOKVM_HOST | Yes | NanoKVM IP address or hostname | |
| NANOKVM_PASS | No | Web UI password | admin |
| NANOKVM_USER | No | Web UI username | admin |
| NANOKVM_HTTPS | No | Use HTTPS instead of HTTP | false |
| NANOKVM_SCREEN_WIDTH | No | Target screen width in pixels | 1920 |
| NANOKVM_SCREEN_HEIGHT | No | Target screen height in pixels | 1080 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| nanokvm_powerA | |
| nanokvm_power_cycleA | |
| nanokvm_led_statusA | |
| nanokvm_hdmi_statusA | |
| nanokvm_hdmi_resetA | Reset the HDMI connection. Useful if video is not displaying correctly. |
| nanokvm_send_textA | |
| nanokvm_send_keyA | |
| nanokvm_tapA | |
| nanokvm_clickB | |
| nanokvm_moveA | |
| nanokvm_scrollB | |
| nanokvm_screenshotA | |
| nanokvm_list_imagesA | |
| nanokvm_mount_isoA | |
| nanokvm_unmount_isoB | Unmount the currently mounted ISO image. |
| nanokvm_mounted_imageA | |
| nanokvm_reset_hidA | Reset the HID (keyboard/mouse) devices. Use this if keyboard or mouse input stops working. |
| nanokvm_infoB | |
| nanokvm_hardwareB | |
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 19 tools
Each tool has a distinct purpose with clear boundaries. For example, nanokvm_click, nanokvm_move, and nanokvm_tap handle different mouse/touch actions, while nanokvm_power and nanokvm_power_cycle manage power operations with specific use cases. No tools appear to overlap or cause confusion in selection.
All tools follow a consistent snake_case naming convention with a 'nanokvm_' prefix and descriptive verb_noun combinations, such as nanokvm_click, nanokvm_hardware, and nanokvm_mount_iso. This uniformity makes the tool set predictable and easy to navigate.
With 19 tools, the server provides comprehensive coverage for NanoKVM device management, including input emulation, power control, media handling, and status monitoring. The count is well-scoped for the domain, offering necessary functionality without being excessive.
The tool set covers all essential aspects of NanoKVM operations: hardware and status queries (e.g., nanokvm_info, nanokvm_hdmi_status), input control (e.g., nanokvm_click, nanokvm_send_text), power management (e.g., nanokvm_power, nanokvm_power_cycle), and ISO image handling (e.g., nanokvm_mount_iso, nanokvm_unmount_iso). No obvious gaps exist for the server's purpose.