Vmware Vdi
VMware/Omnissa Horizon VDI ops: pools, sessions, machines, images — 27 MCP tools.
- Transport
- Not stated
- Package
- —
- Registry id
- io.github.vmware-skills/vmware-vdi
No install snippet on purpose. A working MCP config is a command, its arguments and an environment block — the last two are where API keys live, so this catalogue never stores them and cannot publish them. Follow the link above for the authors' own instructions.
AI-powered intelligent operations for VMware / Omnissa Horizon VDI — manage desktop pools, RDS farms, published apps, user sessions, desktop machines, entitlements, instant-clone images, and Horizon events/health/statistics through the Horizon 8 Connection Server REST API. Ships as both an MCP server (for AI agents) and a CLI (for help-desk and scripting). Part of the VMware skill family.
Disclaimer: Community-maintained open-source project, not affiliated with, endorsed by, or sponsored by VMware, Inc., Broadcom Inc., or Omnissa, LLC. "VMware", "Horizon", and "Omnissa" are trademarks of their respective owners. Source is publicly auditable under the MIT license.
Status: v1.0.0 (beta). REST endpoints are verified against the official Horizon Server API; GET-response field projections are defensive and pending validation against a live Connection Server (a field-name mismatch yields empty results, not a crash — see the beta note).
Why vmware-vdi
Every other VMware family skill stops at the vСenter VM. A Horizon desktop pool sits on those VMs —
so vmware-aiops can reset the backing VM, but it cannot see a user session, log a user off, disable a
pool, or push a golden image. vmware-vdi fills exactly that day-2 VDI gap — "who is stuck on a broken
desktop", "log this user off so their profile unlocks", "why is this pool not provisioning", "push the
patched image to Finance tonight" — with the family's governed-ops harness: every write is audited,
previews its blast radius, and is authorized by the Horizon account's own RBAC role.
Capabilities — 27 MCP tools (16 read / 11 write)
| Category | Tools |
|---|---|
| Monitoring | health summary · session list/get · machine list/get · event list |
| Statistics | session concurrency stats · per-pool utilization |
| Management | pool list/get · farm list · app-pool list · entitlement list · image list · AD search · pool enable/disable · entitlement add/remove |
| Ops actions | session logoff / disconnect / message · machine reset / maintenance / remove |
| Tasks | task status · image push · task cancel |
Reads are strictly non-destructive. Writes preview their blast radius, double-confirm at the CLI, and
are audit-logged to ~/.vmware/audit.db. pool_push_image recreates every desktop in a pool — the
highest single-call blast radius in the family — and its preview states affected-desktop and
in-session counts before any confirm, together with occupancy: determined when those counts
can be believed, unknown when sessions exist that cannot be attributed to any pool or farm. An
unknown occupancy refuses the confirm rather than reporting an unverified zero; overriding it
needs --acknowledge-unknown-occupancy and is recorded in the audit row.
Quick start
uv tool install vmware-vdi
vmware-vdi init # friendly wizard: connect to a Connection Server + discover your pools
vmware-vdi doctor # verify config / credentials / connectivity
vmware-vdi health # one-glance VDI health
vmware-vdi init prompts for the Connection Server host, admin username, AD domain, and password; writes
~/.vmware-vdi/config.yaml + a 0600 .env (password obfuscated); tests the login; and on success
discovers your pools, machines, and sessions with the next commands to try.
Example workflows
Help-desk — a user's desktop is stuck
vmware-vdi session list --user alice
vmware-vdi machine list --state AGENT_UNREACHABLE
vmware-vdi session logoff --user alice --dry-run # preview which sessions
vmware-vdi session logoff --user alice # double-confirm, then logs off + audits
From the project's README.