Server facts
302_sandbox_mcp MCP Server
Project
- Author
- 302ai
- Repository
- github.com/302ai/302_sandbox_mcp
- License
- Not specified
- Category
- Developer Tools
Tech
- Runtime / language
- Not specified
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 21
- Last commit
- Data as of
Tags
- 302ai
- mcp
- sandbox
- server
Overview
Sandbox workflows in 302_sandbox_mcp cover both ongoing work and isolated code runs. For ongoing work, createSandbox returns an identifier used to target later operations, listSandboxes retrieves environments associated with the current API key, and killSandbox removes a selected environment. Created sandboxes pause automatically, reconnect for subsequent operations, and pause again afterward. For a self-contained task, directRunCode handles creation, execution, and immediate destruction, with optional file export. The separate runCode and runCommand tools operate on an existing sandbox and return textual results rather than generated files.
File handling uses dedicated tools alongside execution. After a sandbox exists, writeSandboxFiles imports content from publicly accessible URLs or base64 data, accepts multiple files, replaces existing targets, and creates missing destination directories. listSandboxFiles checks directory contents or file paths, including multiple paths in one request. downloadSandboxFiles turns selected files or directories into download URLs and supports batch exports; directory exports include only the common format categories specified by the tool. This separates command output from file retrieval when an assistant needs to collect generated artifacts.
302_sandbox_mcp setup notes
- 302_sandbox_mcp records stdio only; confirm a network transport upstream before planning remote access.
- 302_sandbox_mcp has no recorded license; confirm reuse terms in its repository.