Migration MCP Tools

Reference for MCP server tools used during VMware-to-OpenStack migration — VMware discovery, OpenStack provisioning, and the migration engine tool.

Migration MCP Tools

VMware migration leverages three MCP servers that expose infrastructure operations as tools callable by InfrastructureAI agents and the Migration Monitor dashboard. All communication uses JSON-RPC 2.0 over HTTP.

VMware MCP Server (8 Tools)

Connects to your vCenter via the vSphere REST API. Supports vCenter 7.x and 8.x.

Tool Description
vmware_list_vms List all virtual machines with name, power state, host, CPU, memory, disk capacity, IP, guest OS, and tools status
vmware_get_vm Get detailed information for a specific VM by ID or name
vmware_set_vm_power_state Power on, power off, or reset a VM
vmware_list_hosts List all ESXi hosts with CPU, memory, connection state, and VM count
vmware_list_clusters List compute clusters with host count and DRS/HA status
vmware_list_datastores List datastores with capacity, free space, and type (VMFS/NFS/vSAN)
vmware_list_networks List virtual networks (port groups, distributed port groups, segments)
vmware_get_vm_metrics Get performance metrics (CPU, memory, disk I/O, network) for a VM

Used during migration:

  • vmware_list_vms — VM discovery, source spec extraction (vCPU, RAM) for flavor matching
  • vmware_set_vm_power_state — Power off source VM during cutover phase
  • vmware_list_networks — Network mapping between VMware port groups and OpenStack networks

OpenStack MCP Server (54 Tools)

Full CRUD access across all OpenStack services. Enables AI agents to provision, manage, and decommission resources without CLI access or SDK installation.

Compute — 13 Tools

Tool Description
openstack_list_vms List all instances with status, addresses, flavor, image, and host
openstack_get_vm Get detailed instance information
openstack_server_create Create a new instance (name, flavor, image/volume, network, keypair)
openstack_server_delete Delete an instance
openstack_server_start / stop / reboot / rebuild Instance lifecycle management
openstack_list_server_events Server event audit log
openstack_get_server_faults Fault details for failed instances
openstack_list_flavors List available flavors with vCPU, RAM, and disk specs
openstack_list_availability_zones List compute availability zones
openstack_get_hypervisor_stats Aggregate hypervisor capacity and utilization

Networking — 18 Tools

Full CRUD for networks, subnets, routers, floating IPs, ports, and security groups.

Images — 3 Tools

List, get, and delete Glance images.

Block Storage — 5 Tools

Full CRUD for Cinder volumes and volume types.

Identity and Keys — 5 Tools

Project management, quota queries, and keypair operations.

Infrastructure Summary — 1 Tool

openstack_get_infrastructure_summary — comprehensive overview of the entire OpenStack environment in a single call.

ORC GitOps — 8 Tools

Declarative resource management via the OpenStack Resource Controller (ORC) — create and delete resources through GitOps manifests.

Used during migration:

  • openstack_list_flavors — flavor matching (find the closest flavor for source VM specs)
  • openstack_server_create — create target instance with matched flavor and boot volume
  • openstack_get_vm — poll instance status until ACTIVE
  • openstack_server_delete — cleanup during reset
  • openstack_list_vms — inventory polling for the Migration Monitor dashboard

Migration Engine Tool

The migration engine exposes a single MCP tool that orchestrates the full migration pipeline:

vmware_migrate_vm

Parameter Type Default Description
source_vm string required VM name or managed object reference ID
target_flavor string auto-matched OpenStack flavor (auto-selected if omitted)
target_network string default network Target OpenStack network
target_keypair string default keypair SSH keypair for the target instance
power_off_source boolean true Power off the source VM after migration
dry_run boolean false Discover and plan only — do not execute

Response:

{
  "source_vm_name": "web-server-prod-01",
  "source_vm_moref": "vm-1234",
  "target_instance_id": "a1b2c3d4-...",
  "target_instance_name": "migrated-web-server-prod-01",
  "migration_state": "completed",
  "pipeline": "B (open source)",
  "disks_migrated": [
    {
      "source_vmdk": "[datastore1] web-server/web-server.vmdk",
      "target_volume_id": "e5f6g7h8-...",
      "size_gb": 100
    }
  ],
  "duration_seconds": 847
}

How Agents Use These Tools

During a migration operation, InfrastructureAI agents coordinate across all three MCP servers:

  1. Scout polls vmware_list_vms and openstack_list_vms continuously, writing inventory changes to the FFO knowledge graph
  2. Sage queries FFO for VM dependencies and plans migration waves — databases before application servers, shared storage before consumers
  3. Wrangler invokes vmware_migrate_vm for each VM in the wave, monitors progress, handles failures with retry or rollback
  4. The Migration Monitor dashboard polls all three MCP servers for real-time visualization

All agent actions flow through MCP — no direct API access, no stored credentials in agent code, no SSH. Every tool invocation is logged and auditable.