Code Sandbox MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CODE_SANDBOX_AUDIT_LOG | No | Path to audit log file. Default is platform-specific (e.g., %LOCALAPPDATA%\code-sandbox-mcp\audit.jsonl on Windows). | |
| CODE_SANDBOX_MAX_TIMEOUT | No | Maximum command timeout in seconds (default 120). | |
| CODE_SANDBOX_IDLE_TIMEOUT | No | Idle timeout in seconds (default 180). | |
| CODE_SANDBOX_MAX_LIFETIME | No | Maximum lifetime of a sandbox session in seconds (default 600). | |
| CODE_SANDBOX_MAX_SESSIONS | No | Maximum number of concurrent sessions (default 3). | |
| CODE_SANDBOX_AUDIT_ENABLED | No | Set to 'false' to disable audit logging (default 'true'). | |
| CODE_SANDBOX_DEFAULT_TIMEOUT | No | Default command timeout in seconds (default 30). |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_sandboxA | Create a disposable offline JavaScript sandbox using the fixed server profile. |
| write_filesC | Write UTF-8 text files beneath /workspace using an in-memory archive. |
| list_filesB | List regular files and directories beneath /workspace without following links. |
| read_fileB | Read a bounded UTF-8 text file beneath /workspace. |
| delete_filesA | Delete selected regular files; deleting /workspace or directories is forbidden. |
| run_javascriptC | Run an existing JavaScript file with fixed Node arguments and no shell. |
| destroy_sandboxB | Force-remove a sandbox. Repeated calls are safe and idempotent. |
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 7 tools
Each tool targets a distinct operation: sandbox lifecycle, file management, and execution. No overlap in purposes, making selection unambiguous for an agent.
All tools follow a consistent verb_noun pattern in snake_case (e.g., create_sandbox, list_files, run_javascript), making the set predictable and easy to navigate.
Seven tools is well-scoped for a sandbox management server, covering creation, destruction, file operations, and execution without unnecessary bloat.
The set covers core sandbox lifecycle and file operations. Minor gaps like renaming files or inspecting sandbox metadata exist but do not severely hinder common workflows.