Skip to main content
Glama
DevilTea

agent-vm-mcp

by DevilTea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to agent-vm-mcp

No user-submitted related servers found.

    Related Servers

    • Universal AI Bridge

      LMPrado-DZ23
      A
      license
      A
      quality
      A
      maintenance
      Enables any MCP-compatible AI, whether in the browser or running locally, to create and edit projects, run terminal commands and long-running jobs, and optionally use Docker, all guarded by a policy engine, workspace jail, authentication, and audit logging.
      23
      MIT

    • Universal Host Manager MCP

      Abktya
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients such as ChatGPT and Claude to administer Linux or macOS hosts through authenticated Streamable HTTP, including running shell commands, reading and writing files within a workspace, listing directories, and retrieving system metrics.
      1
      MIT

    • microvm-mcp

      perbu
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables workspace-authorized creation and operation of isolated Firecracker microVMs over MCP or HTTP, letting users execute commands in full Debian guests, manage VM lifecycle, and transfer files without affecting the host process.
      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

    B3.3/5.0

    Scored across 27 tools

    Disambiguation4/5

    Tool purposes are largely distinct: exec vs process_start vs agent_start have explicit boundary guidance, and agent_* lifecycle tools map to unique operations. Minor overlap remains between capabilities and agent_capabilities, and agent_get/agent_read are somewhat close, but descriptions clarify intent.

    Naming Consistency3/5

    A clear noun_verb/prefix pattern dominates (workspace_*, agent_*, process_*), but there are deviations: exec, read_file, import_file, present_file, apply_patch, and command_info use a different verb-first style, and the bare capabilities tool mixes conventions.

    Tool Count2/5

    27 tools is heavy for a VM execution server, exceeding the 25-tool threshold. The large agent_* cluster plus separate process_* lifecycle families adds surface area and cognitive load, though each tool does earn some place.

    Completeness4/5

    Strong lifecycle coverage: file read/import/present, workspace CRUD, process start/read/write/kill/list, and full agent start/get/read/prompt/suspend/resume/stop. Minor gaps exist, such as no file write/delete counterpart to read_file and no explicit directory-creation or move operation.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources