KVMFleet MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KVMFLEET_API | No | The API endpoint URL. Default is https://app.kvmfleet.io | https://app.kvmfleet.io |
| KVMFLEET_TOKEN | Yes | Your API token for authentication. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_devicesA | List all KVM devices in the operator's organisation, with online/offline state and recent health metrics. Use this to answer 'what's in the fleet' or 'is X online' questions. |
| get_device_healthB | Detailed health snapshot for a single device: temperature, uptime, agent version, last seen. |
| query_audit_logB | Recent audit events for the org, optionally filtered. Useful to answer questions like 'who started a console session today' or 'were there failed logins overnight'. |
| verify_audit_integrityA | Re-walk the per-org audit hash chain on the server and report whether it's intact. Use this when a user wants compliance reassurance. |
| list_open_console_sessionsA | List currently-open (unended) console sessions in the org. |
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 5 tools
Each tool targets a distinct aspect: device health, device listing, console sessions, audit events, and audit integrity. No overlap in purpose.
All tool names follow a consistent verb_noun pattern (e.g., get_device_health, list_devices). No mixing of conventions.
With 5 tools, the server is well-scoped for monitoring and auditing a KVM fleet. No unnecessary tools.
Covers device health, listing, sessions, and audit, but lacks operations to start/stop console sessions or manage devices. Minor gaps.