aliyun-agent-sandbox-mcp
Related Servers
Alternatives to aliyun-agent-sandbox-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables any MCP-capable agent to create, connect, pause, and destroy isolated Alibaba Cloud Bailian (Model Studio) cloud sandboxes, and inside them run Python code and shell commands and read, write, list, and delete files. Sandbox templates can also be listed, inspected, created, and removed, with the current sandbox tracked automatically so calls can omit the ID.MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to securely execute Python and JavaScript code in sandboxed environments, with file management and package installation.755 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables AI clients to manage and execute development commands within isolated Railway sandboxes, providing a remote shell, file read/write, and sandbox lifecycle management for running tests, builds, and repository operations.-
- AlicenseNot gradedqualityDmaintenanceProvides AI agents with cloud-based execution environments through Alibaba Cloud's Wuying infrastructure, enabling browser automation, file operations, and terminal access in secure, serverless cloud environments.7MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to operate a persistent Linux sandbox in the cloud, running commands, managing files, using Git, and publishing artifacts through a Streamable HTTP MCP endpoint.-
- AlicenseAqualityDmaintenanceEnables AI agents to create, modify, and deploy web projects through the AICre8 platform's sandbox environment. It supports project management, code generation, and direct shell command execution for streamlined web development.78 npmMIT
TDQS
Scored across 14 tools
Tool families are clearly separated: sandbox lifecycle (status/create/list/info/kill/set_timeout), execution (run_code vs run_command, distinguished by Jupyter kernel vs shell), and file operations. The only mild overlap is sandbox_status (server config, no network) versus sandbox_info (state of a specific sandbox), but the descriptions make the distinction explicit.
Names group into predictable prefixes: sandbox_* for lifecycle, file_* for filesystem work, and run_* for execution, with consistent snake_case throughout. Minor deviations exist (run_code/run_command are not prefixed, and sandbox_status/sandbox_info use a noun rather than a verb), but the pattern remains readable and predictable.
Fourteen tools map cleanly onto three coherent concerns (sandbox lifecycle, code/command execution, file management), with no redundant entries. Each tool covers a distinct operation an agent would plausibly need.
The surface covers the full sandbox lifecycle (create, list, inspect, extend TTL, kill), two execution modes, and a near-complete filesystem set (read, write, list, mkdir, remove, rename). Gaps are minor: no local-to-sandbox file upload/download, no binary or archive transfer, and no pause/resume of a sandbox.