Sandbox Env MCP Server

What the code does

We read the source, 19 h ago · rules 3dff92dd89df

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

            self.exec_oneoff(name, f"rm -rf {shlex.quote(tmp_dir)}")

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

        proc = subprocess.run(cmd, capture_output=True, timeout=connect_timeout)

      - "${DOCKER_SOCK_PATH:-/var/run/docker.sock}:/var/run/docker.sock"

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add sandbox-env-mcp -- uvx sandbox-env-mcp

{
  "mcpServers": {
    "sandbox-env-mcp": {
      "args": [
        "sandbox-env-mcp"
      ],
      "command": "uvx"
    }
  }
}

[mcp_servers.sandbox-env-mcp]
command = "uvx"
args = ["sandbox-env-mcp"]

{
  "mcpServers": {
    "sandbox-env-mcp": {
      "args": [
        "sandbox-env-mcp"
      ],
      "command": "uvx"
    }
  }
}

{
  "mcpServers": {
    "sandbox-env-mcp": {
      "args": [
        "sandbox-env-mcp"
      ],
      "command": "uvx"
    }
  }
}