VMware-AIops
This server provides read and write operations for managing VMware vCenter/ESXi infrastructure, including VM lifecycle, deployment, guest automation, snapshots, clusters, datastores, alarms, and auditable multi-step plans.
List, acknowledge, and reset vCenter alarms with scope-aware clearing.
Create, delete, configure, inspect clusters, and add/remove ESXi hosts.
Browse and scan datastores for OVA/ISO/OVF/VMDK deployable images.
Deploy VMs from OVA files, vSphere templates, linked clones, batch clones, or declarative YAML specs.
Create, clone, migrate, reconfigure, power on/off, convert to template, and delete VMs.
Run guest operations via VMware Tools: execute commands, capture output, upload/download files, and provision VMs with ordered steps.
Create, list, revert, and delete VM snapshots; poll long-running vSphere tasks.
Build, apply, rollback, and list multi-step VM operation plans with validation and rollback information.
Set, cancel, and list VM TTLs for daemon-driven auto-deletion.
Use read-only tools for alarms, clusters, datastores, snapshots, plans, TTLs, and task status; writes are audited to ~/.vmware/audit.db.
Supports sending automated notifications, monitoring alerts, and scan logs to Discord channels via webhooks.
Provides tools for managing vSphere Kubernetes Service (VKS), including listing Tanzu clusters, checking node status, and scaling worker nodes.
Supports sending automated notifications, monitoring alerts, and scan logs to Slack channels via webhooks.
Enables comprehensive management of vCenter and ESXi environments, including VM lifecycle operations, vSAN health monitoring, hardware sensor reporting, and datastore browsing.
VMware-AIops
Turn VM lifecycle requests into explicit, auditable operations for vCenter and ESXi.
English · 简体中文
Community-maintained · MIT · Not an official VMware/Broadcom product.

Synthetic-data GIF; video includes redacted historical screenshots. Download the AI-narrated family introduction (~3 min)
Why use it?
Deploy and manage VMs, snapshots and guest tasks.
Preview destructive actions and inspect task results.
Use dedicated companion modules for focused investigations.
Related MCP server: VMware-Monitor
Get started
Install the published CLI and inspect its commands:
uv tool install vmware-aiops==2.5.3
vmware-aiops --helpRequires uv and Python >=3.10. Configure targets and credentials locally before remote queries. Setup guide.
One-click installs, after init: Claude Desktop extension (.mcpb), which offers read-only tools until you change its setting · Install in VS Code. Both run the pinned 2.5.3 server and read the configuration init wrote.
For agent-host installation, use the setup guide and Cursor, Codex, Gemini CLI, Cline and local-model examples.
Choose a model with the shared model-fit workflow: compare the same tasks, review quality and safety, then select the smallest tested passing configuration per task group; this is not a production guarantee.
Know the boundaries
Includes sensitive infrastructure writes, guest execution and file transfers. Account permissions, local Policy and host-path boundaries apply; confirmation is not independent human approval.
Go deeper
Part of VMware Skills: 15 skills, 14 MCP servers and one shared Policy library. If it helps your work, star the family portal.
Share setup progress or a first result · Using it at your organization? · Report a bug · MIT
MCP result contract
Offset-capable listings expose next_offset; stop when it is null rather than looping on truncated. Failed calls provide structuredContent.vmware_error through Policy 1.26.0. Existing text, legacy flags, success values and confirmation checks remain unchanged. See the contract.
Available Tools
44 toolsacknowledge_vcenter_alarmA
[WRITE] Acknowledge a triggered vCenter alarm — marks it as seen WITHOUT clearing it.
The alarm stays in the active list with acknowledged=true until its condition clears or it is reset. To remove the alarm entirely after fixing the root cause, use reset_vcenter_alarm instead. Get exact entity_name and alarm_name values from list_vcenter_alarms first; an unknown pair returns a not-found error. Audited to ~/.vmware/audit.db.
Args: entity_name: Name of the VM, ESXi host, or cluster the alarm fired on (from list_vcenter_alarms output). alarm_name: Exact alarm definition name, e.g. "Virtual machine CPU usage". target: vCenter target name from config.yaml; omit to use the default target.
Returns: Dict: entity_name, alarm_name, action ("acknowledged"), acknowledged (true).
Inputs: alarm_name (required), entity_name (required), target.
attach_iso_to_vmA
[WRITE] Mount a datastore ISO into a VM's virtual CD-ROM drive.
Reconfigures the existing CD-ROM (replacing any currently mounted ISO) or adds a new CD-ROM on the VM's IDE controller if none exists; fails with a clear message if the VM has no IDE controller. Works whether the VM is powered on or off — the device is set connected and start-connected. Find ISO files first with browse_datastore using pattern "*.iso". Audited to ~/.vmware/audit.db.
Args: vm_name: Exact VM name as shown in vCenter inventory. iso_ds_path: Full datastore path in bracket format, e.g. "[datastore1] iso/ubuntu-22.04.iso" (datastore name in brackets, then the path relative to the datastore root). target: vCenter/ESXi target name from config.yaml; omit to use the default target.
Returns: Status string confirming attachment, or a VM-not-found / no-IDE-controller error.
Inputs: vm_name (required), iso_ds_path (required), target. Returns: result
batch_clone_vmsA
[WRITE] Batch clone multiple VMs from a source VM (gold image).
Each clone: full copy → optional reconfigure → optional snapshot → optional power on.
Args: source_vm_name: Source VM to clone from. vm_names: List of names for the new VMs. cpu: Override CPU count for all clones (optional). memory_mb: Override memory for all clones (optional). snapshot_name: Create a baseline snapshot on each clone (optional). power_on: Power on each clone after creation. target: Optional vCenter/ESXi target name from config.
Inputs: vm_names (required), source_vm_name (required), cpu, target, +3 more. Returns: result
batch_deploy_from_specA
[WRITE] Deploy multiple VMs in one call from a declarative YAML spec file.
Use for fleet provisioning (several VMs, shared defaults); for a single VM prefer deploy_vm_from_template, vm_clone, deploy_vm_from_ova, or deploy_linked_clone. The provisioning channel is chosen by spec keys: top-level "source" (full clone), "template", "linked_clone: {source, snapshot}", per-VM "ova", else empty-VM creation (optionally with "iso"). A "defaults" block sets cpu/memory_mb/disk_gb/network/ datastore/snapshot/power_on, overridable per VM. VMs deploy sequentially; one VM's failure is recorded and the rest continue. Audited to ~/.vmware/audit.db.
Args: spec_path: Local filesystem path to the deploy.yaml specification file. target: vCenter/ESXi target name from config.yaml; omit to use the default target.
Returns: One dict per VM: name, status ("ok" or "error"), and messages with per-step results.
Inputs: spec_path (required), target. Returns: result
batch_linked_clone_vmsA
[WRITE] Batch create linked clones from a VM snapshot (fastest batch provisioning).
Each clone shares the source disk via copy-on-write.
Args: source_vm_name: Source VM to clone from. snapshot_name: Snapshot to use as clone base. vm_names: List of names for the new linked clones. cpu: Override CPU count (optional). memory_mb: Override memory (optional). power_on: Power on each clone. baseline_snapshot: Create a new snapshot on each clone (optional). target: Optional vCenter/ESXi target name from config.
Inputs: vm_names (required), snapshot_name (required), source_vm_name (required), cpu, +4 more. Returns: result
browse_datastoreARead-onlyIdempotent
[READ] Browse files in a vSphere datastore directory.
Use this to discover OVA, ISO, VMDK, and other files on datastores before deploying VMs.
Args: datastore_name: Name of the datastore to browse. path: Subdirectory path (empty string for root). pattern: Glob pattern to filter files (e.g. ".ova", ".iso", "*"). target: Optional vCenter/ESXi target name from config.
Inputs: datastore_name (required), path, target, pattern. Returns: result
cluster_add_hostA
[WRITE] Move an ESXi host that vCenter already manages into a cluster.
The host must already be in vCenter inventory (standalone or in another cluster) — this tool does NOT register brand-new hosts and takes no host credentials; use the vCenter UI for first-time host registration. Idempotent: a host already in the cluster returns success without change. Maintenance mode is not required to join (it IS required by cluster_remove_host). Check membership with cluster_info. Audited to ~/.vmware/audit.db.
Args: cluster_name: Existing destination cluster name (create with cluster_create). host_name: Host name exactly as shown in vCenter inventory, typically the FQDN, e.g. "esxi-01.lab.local". target: vCenter target name from config.yaml; omit to use the default target.
Returns: Status string: moved, already-in-cluster, or host/cluster-not-found error.
Inputs: host_name (required), cluster_name (required), target. Returns: result
cluster_configureA
[WRITE] Reconfigure cluster HA/DRS settings.
Args: name: Cluster name. ha: Enable (True) or disable (False) HA, or None to leave unchanged. drs: Enable (True) or disable (False) DRS, or None to leave unchanged. drs_behavior: DRS behavior: "fullyAutomated", "partiallyAutomated", or "manual". target: Optional vCenter target name from config.
Inputs: name (required), ha, drs, target, +1 more. Returns: result
cluster_createA
[WRITE] Create a new empty cluster in a datacenter, optionally enabling HA and DRS.
Fails with a clear error (no partial state) if a cluster with that name already exists or drs_behavior is invalid. After creation, add hosts with cluster_add_host; change HA/DRS later with cluster_configure; verify with cluster_info. Audited to ~/.vmware/audit.db.
Args: name: Name for the new cluster; must be unique in the datacenter. datacenter: Datacenter name; omit to use the first datacenter on the target. ha: True enables vSphere HA (default False). drs: True enables DRS (default False). drs_behavior: "fullyAutomated" (default), "partiallyAutomated", or "manual". Only takes effect when drs=True. target: vCenter target name from config.yaml; omit to use the default target.
Returns: Status string confirming creation and which features (HA/DRS) were enabled.
Inputs: name (required), ha, drs, target, +2 more. Returns: result
cluster_deleteADestructive
[WRITE] Delete an empty cluster (no hosts must remain).
Args: name: Name of the cluster to delete. target: Optional vCenter target name from config.
Inputs: name (required), target. Returns: result
cluster_infoARead-onlyIdempotent
[READ] Get detailed cluster information: member hosts, HA/DRS config, resource capacity.
Read-only, no side effects. Use before cluster_add_host / cluster_remove_host (shows membership and per-host maintenance mode) and to verify cluster_configure changes.
Args: name: Exact cluster name. target: vCenter target name from config.yaml; omit to use the default target.
Returns: Dict with name, host_count, hosts (each: name, connection_state, power_state, maintenance_mode), ha_enabled, ha_admission_control, drs_enabled, drs_behavior, total/effective CPU (MHz) and memory (GB). Errors return a dict with "error" + hint.
Inputs: name (required), target.
cluster_remove_hostADestructive
[WRITE] Remove a host from a cluster (host must be in maintenance mode).
Args: cluster_name: Cluster to remove the host from. host_name: ESXi host name to remove. target: Optional vCenter target name from config.
Inputs: host_name (required), cluster_name (required), target. Returns: result
convert_vm_to_templateA
[WRITE] Convert a powered-off VM to a vSphere template.
After conversion the VM cannot be powered on — it serves as a clone source for deploy_vm_from_template.
Args: vm_name: Name of the VM to convert (must be powered off). target: Optional vCenter/ESXi target name from config.
Inputs: vm_name (required), target. Returns: result
deploy_linked_cloneA
[WRITE] Create a linked clone from a VM snapshot — near-instant, minimal disk usage.
The clone shares the source's base disk and writes changes to a copy-on-write delta disk, so it depends on the source VM staying intact. Fastest provisioning method for test/dev fleets; use vm_clone or deploy_vm_from_template for fully independent copies. Requires the source VM to have the named snapshot — run vm_list_snapshots first; unknown names return the available list. Audited to ~/.vmware/audit.db.
Args: source_vm_name: Exact name of the source VM (must have at least one snapshot). snapshot_name: Snapshot on the source to use as the clone base (from vm_list_snapshots). new_name: Name for the new linked clone; must not already exist. cpu: Override vCPU count; omit to keep the source's value. memory_mb: Override memory in MB; omit to keep the source's value. power_on: True powers the clone on after creation (default False). baseline_snapshot: If set, creates a snapshot with this name on the new clone. target: vCenter/ESXi target name from config.yaml; omit to use the default target.
Returns: Status string with the new clone name, or a snapshot/VM-not-found error.
Inputs: new_name (required), snapshot_name (required), source_vm_name (required), cpu, +4 more. Returns: result
deploy_vm_from_ovaA
[WRITE] Create a new VM by importing a local .ova file (OVF parse + VMDK upload).
Use for OVA appliance files on the local machine. For vSphere templates use deploy_vm_from_template; to copy an existing VM use vm_clone or deploy_linked_clone. Upload time scales with OVA size. Fails before creating anything if the datastore is not found. Audited to ~/.vmware/audit.db.
Args: ova_path: Local filesystem path to the .ova file (must be readable by this server). vm_name: Name for the new VM; must not already exist. datastore_name: Target datastore name; discover with browse_datastore. network_name: Port group for the VM's NICs (default "VM Network"). folder_path: vCenter VM folder path; omit to use the datacenter's root VM folder. power_on: True powers the VM on after import (default False). snapshot_name: If set, creates a baseline snapshot with this name after deploy. target: vCenter/ESXi target name from config.yaml; omit to use the default target.
Returns: Status string with the deployed VM name, or an error naming the missing resource.
Inputs: vm_name (required), ova_path (required), datastore_name (required), target, +4 more. Returns: result
deploy_vm_from_templateA
[WRITE] Deploy a new VM by cloning from a vSphere template.
Args: template_name: Name of the source vSphere template. new_name: Name for the new VM. datastore_name: Target datastore (uses template's datastore if omitted). cpu: Override CPU count (optional). memory_mb: Override memory in MB (optional). power_on: Power on after deployment. snapshot_name: Create a baseline snapshot with this name (optional). target: Optional vCenter/ESXi target name from config.
Inputs: new_name (required), template_name (required), cpu, target, +4 more. Returns: result
list_vcenter_alarmsARead-onlyIdempotent
[READ] List active/triggered alarms across the vCenter inventory.
Returns alarms with severity (critical/warning/info), entity name and type, alarm name, acknowledged flag, and trigger time.
Args: target: Optional vCenter target name from config. Uses default if omitted. limit: Max number of alarms to return (None = all). Use when many alarms are active.
Inputs: limit, target. Returns: result
reset_vcenter_alarmA
[WRITE] Clear triggered vCenter alarms back to normal state.
Uses AlarmManager.ClearTriggeredAlarms. The named alarm no longer appears in the active alarm list. Use this after resolving the underlying issue. Use list_vcenter_alarms to find entity_name and alarm_name values.
Gotcha: vSphere has no per-alarm clear — this clears ALL triggered alarms matching the named alarm's entity type (host/VM/all) and current status (red/yellow). The response's 'scope' field states exactly what was cleared.
Args: entity_name: Name of the entity with the alarm (VM name, host name, or cluster name). alarm_name: Exact alarm definition name from list_vcenter_alarms output. target: Optional vCenter target name from config.
Inputs: alarm_name (required), entity_name (required), target.
scan_datastore_imagesARead-onlyIdempotent
[READ] Scan all accessible datastores for deployable images (OVA/ISO/OVF/VMDK).
Results are cached locally in ~/.vmware-aiops/image_registry.json for fast lookup via list_cached_images. Run this to refresh the cache.
Args: target: Optional vCenter/ESXi target name from config.
Inputs: target.
vm_apply_planA
[WRITE] Execute a previously created plan step by step.
Steps run sequentially. On failure: stops immediately, keeps the plan file with per-step results, and returns rollback_available flag. On success: deletes the plan file.
If a step fails and rollback_available is true, ask the user whether to rollback, then call vm_rollback_plan if confirmed.
Args: plan_id: The plan ID returned by vm_create_plan. target: Optional vCenter/ESXi target name from config.
Inputs: plan_id (required), target.
vm_cancel_ttlADestructive
[WRITE] Cancel an existing TTL for a VM (prevents auto-deletion).
Args: vm_name: Name of the VM whose TTL should be cancelled.
Inputs: vm_name (required). Returns: result
vm_clean_slateADestructive
[WRITE] Revert a VM to its baseline snapshot (Clean Slate).
Powers off the VM first if it is running, then reverts to the named snapshot. Use this to reset a lab/dev VM to a clean starting state after a task completes.
Args: vm_name: Name of the VM to revert. snapshot_name: Snapshot name to revert to (default: "baseline"). target: Optional vCenter/ESXi target name from config.
Inputs: vm_name (required), target, snapshot_name. Returns: result
vm_cloneA
[WRITE] Clone a VM. Without to_host/to_datastore the clone lands on the source's host+datastore.
Args: vm_name: Source VM (or template) name. new_name: Name for the new clone. to_host: Target ESXi host name (default: source's host). to_datastore: Target datastore name (default: source's datastore). power_on: Power on the clone after creation. target: vCenter/ESXi target name from config.
Inputs: vm_name (required), new_name (required), target, to_host, +2 more. Returns: result
vm_createA
[WRITE] Create a new empty VM with the given hardware sizing.
Creates a powered-off VM with one disk and one NIC. To populate it, attach an ISO (attach_iso_to_vm) and power it on, or use deploy_vm_from_ova / deploy_vm_from_template / vm_clone for a ready-to-run guest. Fails before creating anything if the datastore is not found. Audited to ~/.vmware/audit.db.
Args: vm_name: Name for the new VM; must not already exist. cpu: vCPU count (default 2). memory_mb: Memory in MB (default 4096). disk_gb: Primary disk size in GB (default 40). network_name: Port group for the VM's NIC (default "VM Network"). datastore_name: Target datastore name; omit to use the first accessible datastore. folder_path: vCenter VM folder path; omit to use the datacenter's root VM folder. target: vCenter/ESXi target name from config.yaml; omit to use the default target.
Returns: Status string with the new VM name, or an error naming the missing resource.
Inputs: vm_name (required), cpu, target, disk_gb, +4 more. Returns: result
vm_create_planA
[WRITE] Create an execution plan for multi-step VM operations.
Auto-triggered when operations involve 2+ steps or 2+ VMs. Validates actions, checks target existence in vSphere, and generates a plan with rollback info for each step.
Each operation is a dict with "action" key plus action-specific params. Allowed actions: power_on, power_off, reset, suspend, create_vm, delete_vm, reconfigure, create_snapshot, delete_snapshot, revert_snapshot, clone, migrate, deploy_ova, deploy_template, linked_clone, attach_iso, convert_to_template.
Example: operations=[ {"action": "power_off", "vm_name": "test-1"}, {"action": "revert_snapshot", "vm_name": "test-1", "snapshot_name": "baseline"}, {"action": "power_on", "vm_name": "test-1"} ]
Returns plan dict with plan_id, steps, summary (vms_affected, irreversible_steps, rollback_available). Show to user for confirmation before calling vm_apply_plan.
Args: operations: List of operation dicts, each with "action" + params. target: Optional vCenter/ESXi target name from config.
Inputs: operations (required), target.
vm_create_snapshotAIdempotent
[WRITE] Create a snapshot of a VM.
Args: vm_name: VM to snapshot. snapshot_name: Snapshot name. description: Optional description. memory: Include memory state (heavier, allows resume). quiesce: Quiesce guest filesystem (requires running VMware Tools). target: vCenter/ESXi target name from config.
Inputs: vm_name (required), snapshot_name (required), memory, target, +2 more. Returns: result
vm_deleteADestructive
[WRITE] Delete a VM (irreversible). VM must be powered off.
Args: vm_name: VM to delete. Must be powered off. target: vCenter/ESXi target name from config.
Inputs: vm_name (required), target. Returns: result
vm_delete_snapshotADestructive
[WRITE] Permanently delete a named snapshot, consolidating its delta disk into the parent.
Frees disk space and does NOT change the VM's current state (unlike vm_revert_snapshot, which discards changes since the snapshot). Works while the VM is powered on. Run vm_list_snapshots first for exact names — unknown names return the available list. Irreversible: confirm with the user before calling. Audited to ~/.vmware/audit.db.
Snapshot consolidation is slow for old/large delta disks (often minutes). By default (wait=False) this fires the delete and returns a task id immediately so it does not block your context — poll completion with vm_task_status. Set wait=True only for small snapshots where you want the final confirmation inline (blocks up to 30 min, then returns the task id).
Args: vm_name: Exact name of the VM owning the snapshot. snapshot_name: Exact snapshot name from vm_list_snapshots output. remove_children: False (default) = children are kept and consolidated; True = delete the entire snapshot subtree below this one as well. wait: False (default) = async, return task id immediately; True = block on consolidation. target: vCenter/ESXi target name from config.yaml; omit to use the default target.
Returns: Status string with a task id (poll via vm_task_status), or a not-found message.
Inputs: vm_name (required), snapshot_name (required), wait, target, +1 more. Returns: result
vm_guest_downloadARead-onlyIdempotent
[READ] Download a file from a VM to local machine via VMware Tools.
Requires VMware Tools running in the guest OS.
Args: vm_name: Target VM name. guest_path: File path inside the guest to download. local_path: Local destination path. username: Guest OS username (default "root"). password: Guest OS password. target: Optional vCenter/ESXi target name from config.
Inputs: vm_name (required), guest_path (required), local_path (required), target, +2 more. Returns: result
vm_guest_execA
[WRITE] Execute a command inside a VM via VMware Tools.
Requires VMware Tools running in the guest OS. Returns exit_code, stdout, stderr, and timed_out flag.
Note: VMware Guest Ops API does not capture stdout/stderr directly. To capture output, redirect to a file and use vm_guest_download: command="/bin/bash", arguments="-c 'ls -la /tmp > /tmp/output.txt'" Then download /tmp/output.txt.
Args: vm_name: Target VM name. command: Full path to program (e.g. "/bin/bash", "C:\Windows\System32\cmd.exe"). arguments: Command arguments (e.g. "-c 'whoami'"). username: Guest OS username (default "root"). password: Guest OS password. working_directory: Working directory inside guest (optional). target: Optional vCenter/ESXi target name from config.
Inputs: command (required), vm_name (required), target, password, +3 more.
vm_guest_exec_outputA
[WRITE] Execute a shell command inside a VM and capture stdout + stderr.
Automatically detects guest OS (Linux/Windows) and selects the correct shell. Output is captured by redirecting to a temp file, downloading it, then cleaning up — no manual redirection needed.
Returns exit_code, stdout, stderr, timed_out, os_family.
Args: vm_name: Target VM name. command: Shell command (e.g. "df -h", "ls /etc", "ipconfig"). username: Guest OS username (default "root"). password: Guest OS password. timeout: Max wait seconds (default 300). target: Optional vCenter/ESXi target name from config.
Inputs: command (required), vm_name (required), target, timeout, +2 more.
vm_guest_provisionA
[WRITE] Provision a VM by running a sequence of guest operations (exec / upload / service).
Combines key injection, software installation, and service startup into a single call. Steps execute in order; stops on first failure.
Step types:
exec: {"type": "exec", "command": "apt-get install -y nginx"}
upload: {"type": "upload", "local_path": "/tmp/id_rsa.pub", "guest_path": "/root/.ssh/authorized_keys"}
service: {"type": "service", "name": "nginx", "action": "start"}
Args: vm_name: Target VM name. username: Guest OS username. password: Guest OS password. steps: Ordered list of step dicts. timeout: Per-step timeout in seconds (default 300). target: Optional vCenter/ESXi target name from config.
Returns: dict with success, completed_steps, total_steps, results, error.
Example: steps = [ {"type": "upload", "local_path": "~/.ssh/id_rsa.pub", "guest_path": "/root/.ssh/authorized_keys"}, {"type": "exec", "command": "chmod 600 /root/.ssh/authorized_keys"}, {"type": "exec", "command": "apt-get install -y nginx"}, {"type": "service", "name": "nginx", "action": "enable"}, {"type": "service", "name": "nginx", "action": "start"}, ]
Inputs: steps (required), vm_name (required), password (required), username (required), +2 more.
vm_guest_uploadA
[WRITE] Upload a file from local machine to a VM via VMware Tools.
Requires VMware Tools running in the guest OS.
Args: vm_name: Target VM name. local_path: Local file path to upload. guest_path: Destination path inside the guest. username: Guest OS username (default "root"). password: Guest OS password. target: Optional vCenter/ESXi target name from config.
Inputs: vm_name (required), guest_path (required), local_path (required), target, +2 more. Returns: result
vm_list_plansARead-onlyIdempotent
[READ] List all pending/failed plans.
Returns plan summaries (plan_id, created_at, status, steps count, VMs affected). Stale plans (>24h) are auto-cleaned.
Inputs: no named parameters. Returns: result
vm_list_snapshotsARead-onlyIdempotent
[READ] List the full snapshot tree of a VM, including nested child snapshots.
Read-only, no side effects. Call this before vm_revert_snapshot, vm_delete_snapshot, or deploy_linked_clone to get exact snapshot names. Returns an empty list when the VM has no snapshots.
Args: vm_name: Exact VM name as shown in vCenter inventory. target: vCenter/ESXi target name from config.yaml; omit to use the default target.
Returns: One dict per snapshot: name, description, created (timestamp), state (poweredOn/poweredOff at snapshot time), level (0 = root, higher = nesting depth). No pagination — snapshot trees are small.
Inputs: vm_name (required), target. Returns: result
vm_list_ttlARead-onlyIdempotent
[READ] List all VMs with TTLs registered, including expiry time and status.
Returns a list of TTL entries with remaining_minutes and expired flag.
Inputs: no named parameters. Returns: result
vm_migrateA
[WRITE] Migrate (vMotion) a VM to another host, optionally with storage vMotion.
If the target host has no access to the VM's current datastore, you MUST pass to_datastore — vCenter rejects cross-host vMotion without shared storage.
Args: vm_name: VM to migrate. to_host: Target ESXi host name. to_datastore: Target datastore (required for cross-storage hosts). target: vCenter/ESXi target name from config.
Inputs: to_host (required), vm_name (required), target, to_datastore. Returns: result
vm_power_offADestructive
[WRITE] Power off a VM — graceful guest shutdown by default, hard power-off with force=True.
Graceful mode calls VMware Tools guest shutdown and waits up to 120s; if Tools is not running or shutdown stalls, the response tells you to retry with force=True. An already-off VM returns success without change. Audited to ~/.vmware/audit.db. Use vm_power_on to start a VM; vm_delete requires the VM to be off first.
Args: vm_name: Exact VM name as shown in vCenter inventory (case-sensitive). force: False (default) = graceful guest shutdown via VMware Tools; True = immediate hard power-off (risks guest filesystem damage). target: vCenter/ESXi target name from config.yaml; omit to use the default target.
Returns: Status string: shut down, force powered off, already off, or a Tools-unavailable hint.
Inputs: vm_name (required), force, target. Returns: result
vm_power_onAIdempotent
[WRITE] Power on a virtual machine.
Args: vm_name: Exact name of the virtual machine. target: Optional vCenter/ESXi target name from config. Uses default if omitted.
Inputs: vm_name (required), target. Returns: result
vm_reconfigureA
[WRITE] Change a VM's vCPU count and/or memory.
Pass only the fields you want to change; omitted fields are left untouched. Hot-add of CPU/memory requires it to be enabled on the VM and a running guest; otherwise power the VM off first (vm_power_off). Audited to ~/.vmware/audit.db.
Args: vm_name: Exact name of the VM to reconfigure. cpu: New vCPU count; omit to leave unchanged. memory_mb: New memory in MB; omit to leave unchanged. target: vCenter/ESXi target name from config.yaml; omit to use the default target.
Returns: Status string describing the applied change, or a VM-not-found error.
Inputs: vm_name (required), cpu, target, memory_mb. Returns: result
vm_revert_snapshotADestructive
[WRITE] Revert a VM to a named snapshot (loses changes since snapshot).
Args: vm_name: VM to revert. snapshot_name: Snapshot to revert to. target: vCenter/ESXi target name from config.
Inputs: vm_name (required), snapshot_name (required), target. Returns: result
vm_rollback_planADestructive
[WRITE] Rollback executed steps of a failed plan in reverse order.
Only call this after vm_apply_plan returns status='failed' and the user confirms they want to rollback. Irreversible steps (delete_vm, revert_snapshot, etc.) are skipped with a warning.
Args: plan_id: The plan ID of the failed plan. target: Optional vCenter/ESXi target name from config.
Inputs: plan_id (required), target.
vm_set_ttlA
[WRITE] Set a Time-To-Live (TTL) for a VM. The daemon auto-deletes it when expired.
The scheduler daemon must be running (vmware-aiops daemon start) for
automatic deletion. TTLs are persisted in ~/.vmware-aiops/ttl.json.
Args: vm_name: Name of the VM to auto-delete. minutes: Minutes until deletion (minimum 1). target: Optional vCenter/ESXi target name from config.
Inputs: minutes (required), vm_name (required), target. Returns: result
vm_task_statusARead-onlyIdempotent
[READ] Poll a long-running vSphere task by its id (from an async vm_delete_snapshot).
Use after vm_delete_snapshot returns a task id to check whether the consolidation has finished, instead of re-running the delete. Returns state (queued/running/success/error/ gone), progress percent, and the entity name. 'gone' means vCenter already garbage-collected a completed task — re-list the resource to confirm the final state.
Args: task_id: The task id string returned by an async write operation. target: vCenter/ESXi target name from config.yaml; omit to use the default target.
Returns: Dict with task_id, state, progress_pct, operation, entity, and error/note when relevant.
Inputs: task_id (required), target.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 44 tools
Most tools have clear, distinct purposes (e.g., deploy_vm_from_ova vs deploy_vm_from_template vs vm_clone). However, some overlap exists between vm_guest_exec and vm_guest_exec_output (both execute commands in a guest), and deploy_vm_from_template vs vm_clone (both clone a template/VM), which could cause misselection.
Naming is mostly consistent with a verb_noun pattern (e.g., list_vcenter_alarms, vm_power_on, cluster_create). Minor deviations: vm_set_ttl vs vm_cancel_ttl (inconsistent verb placement), and batch_clone_vms vs batch_linked_clone_vms (not starting with vm_ despite being VM operations).
At 44 tools, this is on the heavy side but covers a broad domain (VM lifecycle, clustering, guest operations, snapshot management). It feels excessive for a single server, but each tool addresses a specific need. The count is borderline, leaning toward too many.
Covers a very comprehensive VM lifecycle: create, deploy, clone, snapshot, power, guest ops, cluster management, alarm handling, and TTL management. Minor gaps: no direct VM rename or NIC management tool, and no datastore management (e.g., create datastore) but these are not core to the server's primary purpose.
Maintenance
Related MCP Connectors
214 tools for AI agents over one MCP endpoint: image, video, audio, 3D, data, storage, mail, GPUs.
MCP-Native LLM Orchestration Agent
Remote MCP for RunComfy: ComfyUI deployments, hosted models, LoRA training. 31 tools.
Self-hosted AI prompt library: prompts, collections, tags, teams, chains. 29 MCP tools for agents.
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to manage VMware vSphere infrastructure through 55 typed tools built on the govc CLI. It supports comprehensive operations including VM lifecycle management, snapshot control, datastore navigation, and networking configuration.5-
- AlicenseAqualityBmaintenanceRead-only VMware vCenter/ESXi monitoring. 8 MCP tools for VM inventory, host status, datastore capacity, cluster info, alarms, events, and VM details. Code-level enforced safety — no destructive operations exist in the codebase. Supports vSphere 6.5–8.0. Works with local models via Ollama/LM Studio.33506 PyPI18MIT
- AlicenseNot gradedqualityDmaintenanceEnables management of VMware vCenter and ESXi environments, including VM operations, resource management, and automation with Ollama AI and n8n workflows.4MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that gives AI agents direct access to VMware vSphere infrastructure, enabling VM lifecycle management, snapshots, datastore operations, networking, and more via 55 typed tools built on govc.-