302AI Sandbox MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| 302AI_API_KEY | Yes | Your 302AI API key, which can be found at https://dash.302.ai/apis/list |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| writeSandboxFilesA | Import files from public URLs into a sandbox. Supports batch import of multiple files. If the target file already exists, it will be overwritten. If the target directory doesn't exist, it will be automatically created. You must create a sandbox before calling this tool. |
| directRunCodeA | Automatically creates a sandbox, executes code, and immediately destroys the sandbox after execution. Optionally exports sandbox files (compresses multiple files into a zip archive if there are multiple files in the specified path, or exports a single file directly). Recommended for use cases that don't require continuous sandbox operations. |
| listSandboxFilesA | List files and directories at specified paths within a sandbox. Supports batch queries with multiple paths. This operation can be used before downloadSandboxFiles to check if the file exists. |
| downloadSandboxFilesA | Export files from a sandbox directory or file path to downloadable urls. Supports batch export of multiple directories or files. When exporting directories, only common file formats are included (documents, images, audio, video, compressed files, web files, and programming language files). |
| runCodeB | Run code on a specific sandbox. This returns text output only. For operations that generate files, you'll need to use separate file viewing and export endpoints. Default file saving path is /home/user. |
| runCommandA | Run a command line command on a specific linux sandbox. This returns text output only. For operations that generate files, you'll need to use separate file viewing and download endpoints. |
| listSandboxesB | Query the list of sandboxes associated with the current API key. If no parameters are passed, all current sandboxes will be returned. |
| killSandboxB | Destroy a sandbox by its ID. |
| createSandboxA | Create a Linux sandbox that can execute code, run commands, upload and download files, and has complete Linux functionality. After successful creation, a sandbox_id will be returned, and all subsequent operations will need to include this sandbox_id to specify the corresponding sandbox. Except for directRunCode, all other operations require the creation of a sandbox first. After successful creation, the sandbox will automatically pause. When calling other sandbox operation interfaces later, it will automatically reconnect and pause again after execution to avoid generating extra costs. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Most tools have distinct purposes, such as createSandbox for creation, killSandbox for destruction, and listSandboxes for querying. However, runCode and runCommand could be slightly ambiguous as both execute operations on a sandbox and return text output, though their descriptions clarify code vs. command execution.
Tool names follow a consistent verbNoun pattern in camelCase throughout, such as createSandbox, downloadSandboxFiles, and runCode. This predictability makes it easy for agents to understand and select tools based on their naming conventions.
With 9 tools, the server is well-scoped for managing Linux sandboxes, covering creation, execution, file operations, listing, and destruction. Each tool serves a clear role without redundancy, making the count appropriate for the domain.
The tool set provides comprehensive coverage for sandbox lifecycle management, including create, list, run, file handling, and destroy operations. A minor gap is the lack of a tool for updating sandbox configurations or states, but core workflows are fully supported without dead ends.