Skip to main content
Glama
Sign In
Docker MCP Sandbox

Docker MCP Sandbox

by thedailyhub31-blip
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Docker MCP Sandbox

No user-submitted related servers found.

    Related Servers

    • Sandbox MCP

      Dhananjay-JSR
      A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to safely execute commands, run tests, and modify project files inside disposable, policy-enforced Docker sandboxes that are isolated from the host machine and its credentials.
      15
      MIT

    • Sandbox MCP

      AbhiteshPundir
      A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to safely run commands, install dependencies, test, and modify code inside disposable, policy-enforced Docker sandboxes isolated from the host, returning results and diffs.
      15
      MIT

    • Sandbox MCP

      riyasaxena32
      A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to safely execute code, run tests, and build projects inside disposable Docker sandboxes, protecting the host machine through enforced isolation, filesystem snapshots, and network controls.
      15
      MIT

    • Advanced MCP Server

      Nom-nom-hub
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Provides AI coding agents with a secure, sandboxed environment for executing coding tasks including file operations, command execution, and testing. Features session management, policy enforcement, and Docker-based sandboxing for safe code execution and development workflows.
      MIT

    • Secure Grid Genesis Execution

      Coraje187
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to safely execute Python, JavaScript, and Bash code in an isolated Docker sandbox with strict security constraints.
      1
      -
    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.5/5.0

    Scored across 11 tools

    Disambiguation4/5

    Each tool maps to a distinct resource+action pair: sandbox lifecycle (create/list/destroy), workspace file IO (read/write), command execution, and a clearly delimited git_* family. The only soft overlap is that execute_command can perform anything the git_* tools do, so an agent may bypass the structured git wrappers, but the intent of each tool is still clear.

    Naming Consistency4/5

    Ten tools follow a clean verb_noun snake_case pattern (create_sandbox, write_file, read_file, execute_command, destroy_sandbox, list_sandboxes), and the git group consistently uses a shared git_ prefix. The git_ prefix group is noun_verb rather than verb_noun, a minor convention shift but internally predictable and readable.

    Tool Count5/5

    Eleven tools is well within a comfortable range and each earns its place: five sandbox/file primitives plus five git operations that provide structured, safer alternatives to raw shell calls. No redundant or filler tools are present.

    Completeness4/5

    Sandbox lifecycle is fully covered (create, list, destroy) and the git surface covers init/status/diff/commit/log, which handles the core workflow. File handling lacks delete_file and list_directory/preview operations, and git lacks branching/checkout, but an agent can work around these via execute_command.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources