Claude KVM
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VNC_HOST | No | VNC server address | 127.0.0.1 |
| VNC_PORT | No | VNC port number | 5900 |
| VNC_PASSWORD | No | Password | |
| VNC_USERNAME | No | Username (required for ARD) | |
| CLAUDE_KVM_DAEMON_PATH | No | Daemon binary path (not needed if already in PATH) | claude-kvm-daemon |
| CLAUDE_KVM_DAEMON_PARAMETERS | No | Additional CLI arguments for the daemon |
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 |
|---|---|
| vnc_commandD | – |
| action_queueD | – |
| task_completeD | – |
| task_failedD | – |
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 4 tools
Tool names suggest distinct functions: queuing actions, completing tasks, failing tasks, and sending VNC commands. However, task_complete and task_failed are closely related status updates, and all lack descriptions, causing some ambiguity.
Naming is inconsistent: action_queue (noun_noun), task_complete (noun_verb), task_failed (noun_verb), vnc_command (noun_noun). The pattern mixes noun-noun and noun-verb structures without a clear convention.
Four tools is borderline low for a KVM server, but could be acceptable if the server focuses narrowly on task management and VNC control. However, typical virtualization operations are missing, making the count feel thin.
The tool set lacks fundamental operations for managing virtual machines (e.g., list, create, delete, start, stop). It only covers task status and VNC commands, leaving significant gaps for a KVM server's domain.