Skip to main content
Glama
EF-Code

boxes-mcp

by EF-Code
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to boxes-mcp

No user-submitted related servers found.

    Related Servers

    • boxes-mcp

      btafoya
      A
      license
      A
      quality
      D
      maintenance
      Enables management of GNOME Boxes virtual machines through libvirt/virsh with lifecycle and snapshot operations.
      13
      8 npm
      MIT

    • libvirt-mcp

      rzippert
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables management of KVM/QEMU virtual machines on remote libvirt hosts via SSH, with tools for inspection, lifecycle management, snapshots, and cloning.
      1
      AGPL 3.0

    • libvirt-mcp-server

      coolnyx
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI models to securely query and manage virtual machines and virtualized resources via the libvirt API through the Model Context Protocol.
      1
      MIT

    • mcp-incus-vm

      RAGton
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to control and automate Incus/QEMU virtual machines via SSH, supporting mouse/keyboard, screenshots, commands, and lifecycle management.
      MIT

    • WSL Manager

      bostrot
      F
      license
      Not graded
      quality
      A
      maintenance
      Lets AI agents manage local virtual machines: create macOS and Linux VMs on Apple silicon and WSL distros on Windows, start/stop, clone, back up, and run commands inside them.
      4,010
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3/5.0

    Scored across 19 tools

    Disambiguation4/5

    Most tools map cleanly to a distinct resource+action (e.g., snapshots.list, snapshots.revert). The only potential confusion is `boxes.capabilities`, which could overlap with `boxes.info` (state info) and `boxes.display` (screen state) for an agent. The input/interaction tools (keyboard, mouse, clipboard, screenshot) are clearly separated by modality.

    Naming Consistency3/5

    Top-level lifecycle tools use consistent single verbs (start, shutdown, reboot, suspend, resume, undefine), but interaction tools shift to bare nouns (keyboard, mouse, clipboard, screenshot, capabilities). Snapshot nesting is consistent and clear. Mixing namespace prefixes (boxes.* and boxes.snapshots.*) with singular noun tools creates minor inconsistency in expected verb-phrase form.

    Tool Count4/5

    19 tools is slightly above the typical sweet spot but justified given the breadth: 5 lifecycle, 4 snapshot, 2 info, and 8 interaction/display tools. The interaction sub-surface is granular (keyboard, mouse, clipboard, drag_drop, capabilities) and could be consolidated, but each maps to a real distinct operation. It never feels bloated enough to warrant a 3.

    Completeness4/5

    Lifecycle operations are well-covered for read/start/stop, snapshots have full CRUD with revert, and interaction features (screenshot, input, clipboard) are thorough. Missing pieces include VM creation/clone, device/storage management, and define/undefine pairing is lopsided (only undefine). Snapshot and interaction workflows feel complete for the stated GNOME Boxes/libvirt scope.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources