Skip to main content
Glama
WeZZard

vm-relay

by WeZZard
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to vm-relay

No user-submitted related servers found.

    Related Servers

    • CUA MCP Server

      duvoai
      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
      -

    • claw-server

      ogradyliam5
      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

    • screenbox

      dklymentiev
      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.
      23
      AGPL 3.0

    • Hyper-V Sandbox MCP Server

      ilkuru
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to safely test and debug PowerShell, CMD/BAT scripts, and system utilities inside isolated Hyper-V virtual machines, with snapshot rollback, host-to-guest file transfer, PowerShell Direct execution, and autonomous self-correction on failures.
      1
      Apache 2.0
    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

    A3.9/5.0

    Scored across 3 tools

    Disambiguation4/5

    The three top-level tools are clearly separated: relay performs actions, relay_status is a read-only status view, and relay_review verifies evidence packages. The main ambiguity is that relay's probe and console-resolve actions overlap somewhat with relay_status, but the descriptions make the distinction reasonably clear.

    Naming Consistency4/5

    All tools share the 'relay' prefix and use underscore separation, so the naming is predictable. The main tool is simply 'relay' while the other two are 'relay_<noun>', which is a minor inconsistency but not confusing.

    Tool Count3/5

    Three tools is a low but plausible top-level count. However, relay is overloaded with many sub-actions (acquire, stage, run, image, extract, finish, release, console operations), so the actual action surface is much larger than the count suggests and would benefit from more top-level decomposition.

    Completeness5/5

    The relay action surface covers the full VM lifecycle: acquire, stage, run, image retrieval, extraction, finish, release, and console operations. relay_status and relay_review fill the status and verification gaps, so there are no obvious dead ends for the stated VM evidence workflow.

    Resources