Rancher MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| harvester_addon_listC | List Harvester addons with their enabled/disabled state |
| harvester_host_listB | List Harvester hosts (nodes) with maintenance mode and disk status |
| harvester_image_listB | List Harvester VM images (VirtualMachineImage) with download progress |
| harvester_network_listB | List Harvester VLAN networks (NetworkAttachmentDefinition) |
| harvester_settingsB | List or get Harvester cluster settings (backup-target, auto-disk-provision-paths, etc.) |
| harvester_subnet_listB | List KubeOVN Subnets (requires kubeovn-operator addon). Subnets define VM network CIDRs and are linked to Networks via provider. |
| harvester_vm_getB | Get a single virtual machine with full spec and status (metrics, disks, networks) |
| harvester_vm_listC | List virtual machines across Harvester clusters with status, IP, node, CPU/memory |
| harvester_volume_listB | List PersistentVolumeClaims (Longhorn-backed volumes) with size and health |
| harvester_vpc_listB | List KubeOVN VPCs (requires kubeovn-operator addon enabled) |
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 10 tools
Each tool targets a distinct Harvester resource type (addons, hosts, images, networks, settings, subnets, VMs, volumes, VPCs). The only potential overlap is between harvester_vm_get and harvester_vm_list, but they are clearly differentiated for single vs. list operations.
All tools follow the pattern 'harvester_<resource>_<action>' except 'harvester_settings' which omits the '_list' suffix. This is a minor inconsistency, but overall the naming is predictable and consistent.
10 tools is well-scoped for managing a Harvester environment. It covers major resource categories without being overwhelming or too sparse.
The tool set is almost entirely read-only (list/get), lacking create, update, or delete operations for any resource. This is a significant gap for lifecycle management, likely causing agent failures when mutations are needed.