SSyncDev

UTM Watch MCP Server

Records per-VM CPU, memory, disk and network history for UTM on a Mac, and lets an agent read it to explain slowdowns.

Local server

What is the UTM Watch MCP Server?

Someone tells you a VM felt sluggish yesterday afternoon. UTM can only tell you it was running. The UTM Watch MCP server fills that gap: it gives an agent read-only access to a recorded history of every UTM virtual machine on your Mac, so the question "why was it slow?" has data behind the answer.

What gets recorded

UTM Watch is a menu bar app first. It names each VM and tracks, without installing anything in the guest:

  • CPU and memory, read from the VM's host process
  • Disk fill level, read from the disk image itself
  • Network traffic on the VM's virtual interface
  • Ping to each VM, to your router and to the internet, plus Wi-Fi or Ethernet link quality

That last item is what makes diagnosis possible. With network path and VM load side by side, you can tell a busy guest from a weak Wi-Fi link. Both of UTM's backends, Apple Virtualization and QEMU, are covered, with macOS, Linux and Windows guests. History is kept in a SQLite file under your Application Support folder.

Tools for the agent

The bundled utmwatch-mcp binary speaks stdio and never changes anything. A sensible order is to start broad and narrow down.

Tool Use it to
find_incidents Locate slow periods when no time was reported
summarize Get a VM-by-VM account of a time range
get_moment See everything captured at one instant
get_metrics Pull one metric over time for a VM, the Mac or the network
list_events List starts, stops, memory pressure, CPU limits, link changes, sleep and wake
get_status Read the latest sample
list_macs List Macs in a fleet

When several Macs report to one hub, every tool takes an optional mac argument. Leave it out and the tool answers for the local machine from its own database, which keeps working even if the hub is down.

Installing and connecting

You need an Apple silicon Mac; macOS 14 is the floor, though only macOS 26 has been tested. Install the app into Applications using the shell installer or the DMG. The DMG build is not notarized, so macOS blocks the first launch until you allow it under Privacy & Security. On first run the app asks for three permissions: other apps' data, control of UTM, and local network access. Deny one and you get less detail rather than a broken app.

For Claude Code, register the binary inside the app bundle at /Applications/UTMWatch.app/Contents/MacOS/utmwatch-mcp. Access for the UTM Watch MCP server can be switched off in the app's settings.

Caveats worth knowing

Only shared (NAT) networking is measured; bridged VMs show no network figures. After each update, macOS treats the app as new and permissions often need granting again, and until they are, VMs appear without names or disk usage. The project is independent of UTM itself. For broader observability, compare it with Grafana or the Prometheus Connector, or browse all monitoring servers.

Recorded tools

Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.

ToolWhat it does
find_incidentsFind when VMs were slow; the starting point when no time was reported.
summarizeSummarise what happened over a time range, VM by VM.
get_momentReturn everything recorded at a single moment.
get_metricsReturn one metric over time for a VM, the Mac or the network.
list_eventsList VM starts and stops, memory pressure and swap, VMs at their CPU limit, link changes, and sleep and wake.
get_statusReturn the latest sample for every VM, the Mac and the network.
list_macsList every Mac in the fleet, on a Mac that has joined one.

How to install the UTM Watch MCP Server

{
  "mcpServers": {
    "utm-watch": {
      "command": "/Applications/UTMWatch.app/Contents/MacOS/utmwatch-mcp"
    }
  }
}

Install the UTM Watch app into /Applications first. Apple silicon Macs only.

Frequently asked questions

No. The MCP server is read-only and works over the recorded history. It reports on VMs but does not control them.