Using vmware-monitor with mcp-agent

April 29, 2026 · View on GitHub

mcp-agent is an MCP-native agent framework by LastMile AI. This guide shows how to configure vmware-monitor for read-only VMware monitoring in mcp-agent workflows.

Code-level safety: vmware-monitor contains zero destructive code — safe to use in automated pipelines without risk of accidental infrastructure changes.

Prerequisites

Install vmware-monitor
```
uv tool install vmware-monitor
```

Configure credentials

mkdir -p ~/.vmware-monitor
cat > ~/.vmware-monitor/config.yaml << 'EOF'
targets:
  my-vcenter:
    host: vcenter.example.com
    username: readonly-user@vsphere.local
    password_env: VMWARE_MONITOR_PASSWORD
    verify_ssl: false
EOF

echo "VMWARE_MONITOR_PASSWORD=your_password" > ~/.vmware-monitor/.env
chmod 600 ~/.vmware-monitor/.env

Verify setup
```
vmware-monitor doctor
```

Adding to mcp-agent

Add to your mcp_agent.config.yaml:

mcp:
  servers:
    vmware-monitor:
      command: vmware-monitor
      args:
        - mcp
      env:
        VMWARE_MONITOR_CONFIG: ~/.vmware-monitor/config.yaml

Requires uv tool install vmware-monitor (v1.5.15+). A ready-to-use template is available at examples/mcp-configs/mcp-agent.yaml.

Full example config

# mcp_agent.config.yaml
execution_engine: asyncio

mcp:
  servers:
    vmware-monitor:
      command: vmware-monitor
      args: [mcp]
      env:
        VMWARE_MONITOR_CONFIG: ~/.vmware-monitor/config.yaml

anthropic:
  model: claude-sonnet-4-6

Available MCP Tools (7 read-only tools)

Tool	Description
`list_virtual_machines`	List VMs with power state, CPU, RAM, IP. Supports `limit`, `sort_by`, `power_state`, `fields`
`list_esxi_hosts`	List hosts with CPU cores, memory, ESXi version, uptime
`list_all_datastores`	List datastores with capacity, free space, type
`list_all_clusters`	List clusters with host count, DRS/HA status
`get_alarms`	Get active alarms with severity and description
`get_events`	Get recent vCenter/ESXi events
`vm_info`	Get detailed VM info including snapshot list

All tools accept an optional target parameter to switch between environments.

Usage Examples

Example 1: Scheduled health report pipeline

# daily_report.py
from mcp_agent.app import MCPApp
from mcp_agent.agents.agent import Agent

app = MCPApp(name="vmware-daily-report")

async with app.run() as vmware_app:
    agent = Agent(
        name="monitor",
        instruction="You are a VMware monitoring agent. Generate concise health reports.",
        server_names=["vmware-monitor"],
    )
    async with agent:
        report = await agent.send(
            "Generate a daily health summary: "
            "active alarms, top 5 VMs by memory usage, "
            "datastores above 75% capacity"
        )
        print(report)

Example 2: Automated alarm triage

Agent: [calls get_alarms] → 5 active alarms
Agent: [calls vm_info for each alarmed VM]
Agent: Summary:
  - 2 CRITICAL: disk latency on vm-db-01, vm-db-02 (same datastore → storage issue)
  - 2 WARNING: memory pressure on vm-analytics (expected, batch job running)
  - 1 WARNING: CPU on esxi-03 (14 VMs, consider rebalancing)

Example 3: Capacity planning data collection

result = await agent.send(
    "Collect capacity data: "
    "total VMs by host, datastore utilization percentages, "
    "cluster DRS/HA status. Format as JSON for reporting."
)