Skip to main content
Glama
xxmisaoxx

Windows Sandbox MCP

by xxmisaoxx

Related Servers

Alternatives to Windows Sandbox MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to safely work on Windows developer workstations through governed, project-scoped filesystem access, durable command execution, bounded search, Windows operations, and resource-aware runtime controls. It also supports optional developer-context backends for code navigation, repository graph exploration, and memory retrieval.
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to safely perform file operations, run terminal sessions, manage processes, search content, and inspect Git repositories on a local Windows machine under configurable permission and audit controls.
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to create, drive, checkpoint, reset and delete resettable Windows and Ubuntu desktop VMs on Apple Silicon Macs, giving them real desktops to click, type and screenshot in plus shell commands, file transfer and port forwarding. All processing is local, so agents can work in isolated guests without leaving the Mac.
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to drive Windows desktop automation — opening and interacting with applications, native UI controls, keyboard/mouse input, files, processes, clipboard, and Chrome/Edge browsing via UI Automation and CDP. All actions pass through a safety policy with human approval, emergency stop, and deterministic verification.
      MIT

    TDQS

    B3.2/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools have clearly distinct roles, but some pairs (sandbox_screenshot vs sandbox_artifact, sandbox_windows vs sandbox_inspect, sandbox_collect_evidence vs individual capture tools) require careful reading of descriptions to avoid confusion.

    Naming Consistency4/5

    All tools use a consistent sandbox_ prefix and snake_case, but suffixes mix verbs and nouns (e.g., sandbox_windows, sandbox_artifact) rather than following a strict verb_noun pattern throughout.

    Tool Count4/5

    18 tools is slightly above the typical 3-15 range, but the set covers lifecycle, execution, file transfer, GUI automation, and evidence collection without obvious redundancy.

    Completeness4/5

    The surface covers core sandbox lifecycle, command execution, file upload/download, screenshot capture, UI inspection, GUI interaction, and evidence collection. Minor gaps like direct guest file management, clipboard access, or snapshot/restore can be worked around via sandbox_exec.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues