mait.sh1.132.1

Private beta: features and content may change. No warranty; use at your own risk.

Install and configure mcp-libvirt

Check that MCP Libvirt is installed, connect it to your agent and read a server without changing anything.

Beta
OverviewGet startedUse casesToolsProblems and fixesAll components
Steps

Five steps from install to your first host read.

MCP Libvirt is an MCP tool: you check it is installed, connect it to your agent, and then ask in plain language. This first run only reads, so it is safe on a host you share. Linux, amd64 or arm64. On macOS and Windows, MCP Libvirt runs in the managed Linux environment that AIDC Launch provides.

  1. Capturedmcp-libvirt 0.11.4
    Check the version
    $ mcp-libvirt version
    mcp-libvirt 0.11.4
    Step 1 of 5

    Check that it arrived

    The MAIT image ships mcp-libvirt and updates it with the image. Check that it runs.

    An error about a missing libvirt.so.0 means the libvirt client library is not installed. See mait-image.

    What you get

    The version command answers, with the build you are on.

  2. mcpServers entry
    {
  "mcpServers": {
    "libvirt": {
      "command": "mcp-libvirt",
      "args": ["serve"],
      "env": { "LIBVIRT_REQUIRE_EXPLICIT_CONNECTION": "1" }
    }
  }
}
    Step 2 of 5

    Connect it to your agent

    Any client that accepts an mcpServers launch entry uses this shape. Place it where your client keeps server configuration and restart the client.

    The server connects with its own credentials, such as an SSH key for a qemu+ssh address, so put them in the environment that launches it and let only people who may use those credentials reach the service. Leave MAIT_LOG_FORMAT unset. If you reach your tools through the registry, add libvirt once with mcp_registry_add and the tools carry the libvirt__ prefix (registry guide).

    What you get

    A client that starts the service on its own, and an agent that can use its 63 tools.

  3. Capturedmcp-libvirt 0.11.4
    YouConnect to our hypervisor so we can look at it.
    Tool calllibvirt_connection_create { "uri": "<the libvirt address of the host>", "connectionId": "guide-demo" }
    What happensStatus connected: a connection slot named guide-demo now exists in this session, and later calls name it with connectionId.
    AgentI am connected to the host as guide-demo.
    Step 3 of 5

    Open a connection to a host

    Every request acts on one host, named by a connection you open first. Without LIBVIRT_REQUIRE_EXPLICIT_CONNECTION in the entry above, a call that names no connection goes to an implicit default one, from LIBVIRT_DEFAULT_URI or else qemu:///system. Give your agent the libvirt address of the host, such as qemu+ssh://operator@hypervisor.example/system.

    What you get

    A named connection. It belongs to this session and ends with it.

  4. Capturedmcp-libvirt 0.11.4
    YouWhat kind of machine is this host, and what do we already manage on it?
    Tool callhost_node_info { "connectionId": "guide-demo" }
    What happensOne socket with 6 cores and 12 threads on an x86_64 processor at 1,099 MHz, about 30 GiB of memory, of which about 5.4 GiB is free.
    Tool calldomain_list { "connectionId": "guide-demo" }
    What happensAn empty list: this session has created and adopted no machines yet. Machines the host already runs are not in the list unless includeUnmanaged is set.
    AgentThe host has 12 threads and about 30 GiB of memory, with about 5.4 GiB free. We have no machines in our working set yet.
    Step 4 of 5

    Read the host

    Ask what the host is and what you already manage on it. Both are reads.

    The empty list is the working set at work: it holds the machines this session created or adopted, not everything on the host. Pass includeUnmanaged to a read to look at the rest; changing one still needs adoption first.

    What you get

    A picture of the host, and no change to it.

  5. Capturedmcp-libvirt 0.11.4
    YouThat is all I needed. Disconnect.
    Tool calllibvirt_connection_drop { "connectionId": "guide-demo" }
    What happensStatus dropped.
    AgentThe connection is closed. Nothing on the host changed.
    Step 5 of 5

    Close the connection

    Ask the agent to drop the connection when it is done. Dropping it releases only the session's tracking: machines, disks and networks stay on the host.

    What you get

    A clean end, and the knowledge that ending a session never deletes a machine.

Result

A connection that reads and a host that stayed as it was.

MCP Libvirt is installed, connected to your agent and able to read a host. Everything that creates, starts or deletes something comes next, one at a time, and works on the machines the session owns.

Next

Where to go next.