Schema | mcp-linux-sandbox

mcp-linux-sandbox

Describes the environment variables required to run the server.

Name	Required	Description	Default
`SANDBOX_MAX`	No	Maximum concurrent containers. Beyond it the least-recently-used is evicted (rm -f; the volume stays, so files survive).	2
`MCP_SIGN_KEY`	Yes	Signing key for download links. Generated by env.sh and stored in mcp-sandbox.env.
`SANDBOX_HOME`	No	Install directory for the MCP server. Defaults to ~/mcp-linux-sandbox.
`SANDBOX_IDLE`	No	Recycle idle containers after this many seconds. Cleanup only: lowering it loses apt packages sooner, nothing else.	300
`MCP_PUBLIC_BASE`	Yes	Public base URL for the MCP server, e.g. https://your.host:8443. Must be set in mcp-sandbox.env; install.sh refuses to run while it is still the placeholder.
`SANDBOX_LINK_TTL`	No	Download links are HMAC-signed with an expiry, so a leaked URL is bounded in time and scope.	3600
`SANDBOX_MIN_FREE`	No	Refuse to start a sandbox when the volume filesystem is nearly full. Checked at container creation only — it will not stop a single large write.	2 GiB
`SANDBOX_IMAGE_MAX`	No	Attached images are also sent to the model (~2 MB ≈ 20k tokens); oversized files fall back to a link.	1.5 MiB
`SANDBOX_INLINE_MAX`	No	Attached images are also sent to the model (~2 MB ≈ 20k tokens); oversized files fall back to a link.	48 KiB
`SANDBOX_MAX_TIMEOUT`	No	Ceiling on the model's timeout_seconds.	900

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.

Server capabilities have not been inspected yet.

Functions exposed to the LLM to take actions

Name	Description
No tools

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

This server cannot be deployed

ActivityMaintained

ResponsivenessNo issues