sandbox-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SMCP_CPUS | No | CPU cores limit per sandbox. | 2 |
| SMCP_HOST | No | Service listen address; recommend keeping 127.0.0.1. | 127.0.0.1 |
| SMCP_PORT | No | Service listen port; shared by /mcp and /files. | 8000 |
| SMCP_TOKEN | Yes | Bearer token for MCP access; required. Generate with `openssl rand -hex 32`. | |
| SMCP_URL_TTL | No | Validity period (seconds) for signed file URLs. | 3600 |
| SMCP_DATA_DIR | No | Directory for sandbox workspaces. | /var/lib/sandbox-mcp/data |
| SMCP_STATE_DB | No | Path to SQLite state database. | /var/lib/sandbox-mcp/state.db |
| SMCP_MEM_LIMIT | No | Memory limit per sandbox. | 2g |
| SMCP_BASE_IMAGE | No | Base Docker image for sandboxes. | ghcr.io/greenteodoro839/sandbox-mcp-base:latest |
| SMCP_PIDS_LIMIT | No | Process count limit per sandbox. | 512 |
| SMCP_JOB_TIMEOUT | No | Default timeout (seconds) for background jobs. | 3600 |
| SMCP_SIGNING_KEY | No | Separate HMAC signing key for file URLs; defaults to SMCP_TOKEN if not set. | = SMCP_TOKEN |
| SMCP_EXEC_TIMEOUT | No | Default timeout (seconds) for exec tool. | 60 |
| SMCP_MAX_SANDBOXES | No | Maximum number of simultaneous sandboxes. | 20 |
| SMCP_PUBLIC_BASE_URL | No | Public base URL for constructing signed file URLs; must be changed to your public HTTPS address. | http://127.0.0.1:8000 |
| SMCP_SANDBOX_NETWORK | No | Sandbox network mode; set to 'none' for no network. | bridge |
| SMCP_IDLE_STOP_SECONDS | No | Idle time (seconds) before stopping a sandbox container. | 7200 |
| SMCP_JOB_LOG_RETENTION | No | Retention time (seconds) for job logs. | 86400 |
| SMCP_GC_INTERVAL_SECONDS | No | GC check interval (seconds). | 300 |
| SMCP_IDLE_REMOVE_SECONDS | No | Idle time (seconds) before removing a sandbox and its files. | 604800 |
| SMCP_READ_TEXT_MAX_BYTES | No | Maximum bytes for inline read_text; larger files use download_url. | 200000 |
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 |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/GreenTeodoro839/sandbox-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server