vmware-vdi
<!-- mcp-name: io.github.vmware-skills/vmware-vdi -->
# VMware-VDI
<a id="readme-overview"></a>
Investigate Horizon desktops and sessions with focused operational tools.
English · [简体中文](README-CN.md)
Community-maintained · MIT · Not an official VMware/Broadcom/Omnissa product.
[](https://github.com/vmware-skills/marketplace/blob/main/assets/demos/vmware-skills-en.mp4)
Synthetic-data animation, not a live recording. [Watch the AI-narrated family introduction (~2 min)](https://github.com/vmware-skills/marketplace/blob/main/assets/demos/vmware-skills-en.mp4)
<a id="readme-capabilities-and-workflows"></a>
## Why use it?
- Inspect pools, farms, machines and health.
- Work with sessions and entitlements.
- Plan supported image and desktop operations explicitly.
<a id="readme-quick-start"></a>
## Get started
Install the published CLI and inspect its commands:
```sh
uv tool install vmware-vdi==2.4.5
vmware-vdi --help
```
Requires uv and Python >=3.10. Configure targets and credentials locally before remote queries. [Setup guide](skills/vmware-vdi/references/setup-guide.md).
For Claude Code and other host installation paths, see the [family portal](https://github.com/vmware-skills/marketplace).
<a id="readme-safety-and-audit"></a>
## Know the boundaries
Includes session logoff, desktop reset and image operations. Missing or incomplete evidence must not be treated as a complete inventory. Horizon live-validation limits remain documented.
<a id="readme-mcp-configuration"></a> <a id="readme-troubleshooting"></a> <a id="readme-reference"></a>
## Go deeper
- [Capabilities](skills/vmware-vdi/references/capabilities.md)
- [CLI reference](skills/vmware-vdi/references/cli-reference.md)
- [Detailed usage and architecture](skills/vmware-vdi/references/detailed-guide.md)
- [MCP launch configuration](.mcp.json)
- [Canonical skill instructions](skills/vmware-vdi/SKILL.md)
<a id="readme-companion-skills"></a>
Part of [VMware Skills](https://github.com/vmware-skills/marketplace): 15 skills, 14 MCP servers and one shared Policy library. If it helps your work, star the family portal.
<a id="readme-license"></a>
[Issues and feedback](https://github.com/vmware-skills/VMware-VDI/issues) · [MIT](LICENSE)
TDQS
Scored across 27 tools
Each tool targets a distinct resource and action: lists vs single-gets are paired (list_desktop_pools/get_desktop_pool, list_vdi_machines/get_vdi_machine, list_vdi_sessions/get_vdi_session), write operations are unique verbs (reset, maintenance, remove, enable, push, logoff, disconnect, message), and the three reporting tools (health_summary, session_stats, utilization) are explicitly differentiated as aggregate vs per-row views. Descriptions even cross-reference ('the reporting counterpart to list_vdi_sessions'), leaving little room for misselection.
Names follow a predictable snake_case verb_noun pattern (list_*, get_*, set_*, remove_*, add_*, cancel_*, search_*). Minor deviation: the 'vdi' domain token appears inconsistently (list_vdi_machines, list_vdi_sessions) while other resources drop it (list_desktop_pools, list_app_pools, list_farms).
27 tools is on the heavy side, but each covers a genuinely distinct object (pools, farms, images, machines, sessions, entitlements, tasks, events) with no redundant duplicates. Slightly over the ideal band but justified by the broad VDI management surface.
Strong lifecycle coverage: pools (list/get/enable/push image), machines (list/get/reset/maintenance/remove), sessions (list/get/logoff/disconnect/message), entitlements (list/add/remove), plus tasks, events, and health/stats reporting. Gaps exist in provisioning (no desktop pool/farm creation or deletion, farms are read-only), which is acceptable for an operations-focused server but leaves some lifecycle dead ends.