Skip to main content
Glama

Related Servers

Alternatives to vm-relay

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      C
      maintenance
      Enables AI coding agents to work inside a disposable Windows guest desktop, where they can run shell commands, launch applications, inspect and operate native GUI controls, perform browser DOM actions, and transfer files. Fresh observations, PNG screenshots, and hashed artifacts let agents verify results without touching the host desktop.
      18
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables autonomous desktop automation by delegating tasks to vision-based agents operating within cloud-based virtual machine sandboxes. It allows users to manage VMs, execute complex computer tasks, and receive text-based screen summaries across Linux, Windows, and macOS environments.
      2
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables a Copilot Studio agent to operate a dedicated, disposable Windows VM by running commands, PowerShell scripts, file operations, and background jobs over authenticated HTTPS.
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      Enables AI agents to record desktop workflows from human demonstrations, save them as validated semantic skills, and replay them in an isolated Linux sandbox with deterministic verification and evidence-driven self-healing.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides AI agents with isolated virtual desktops containing a real Chromium browser, enabling them to see, click, type, and navigate like a human, with features like snapshots and remote control.
      24
      AGPL 3.0

    TDQS

    A4.1/5.0

    Scored across 18 tools

    Disambiguation4/5

    Tools cover distinct phases: discovery (search/probe/capabilities/tools), lifecycle (acquire/stage/finish/release/status), execution (run/exec/script/code), evidence (image/extract), and console. A few read-state tools (probe vs status) and execution variants could be confused, but descriptions draw clear boundaries.

    Naming Consistency5/5

    All tools use a relay_ prefix and snake_case, with no mixed casing or inconsistent styles. The suffixes vary by action, but the naming convention is highly predictable across the set.

    Tool Count4/5

    18 tools is slightly above the typical 3-15 sweet spot, but the surface spans discovery, lifecycle, execution, evidence, console, and status for a complex VM relay. Most tools have a clearly necessary role.

    Completeness5/5

    Covers full VM lifecycle from image discovery and acquisition through staging, execution, evidence extraction, and finish/release, plus console and status. No obvious dead ends for the one-task-per-enclosure workflow.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues