mcp-sandbox-computer-vm-for-ai
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FLY_TOKEN | No | Fly API token for the Fly Machines backend. Alternative to FLY_API_TOKEN. | |
| FLY_REGION | No | Region for newly created Fly Machines. | |
| E2B_API_KEY | No | E2B API key for the E2B backend. | |
| FLY_APP_NAME | No | Fly App that owns sandbox Machines. | |
| FLY_API_TOKEN | No | Fly API token for the Fly Machines backend. Alternative to FLY_TOKEN. | |
| MODAL_TOKEN_ID | No | Modal token ID for the Modal backend, overriding default authentication. | |
| MODAL_TOKEN_SECRET | No | Modal token secret for the Modal backend, overriding default authentication. | |
| KILNTAINERS_AUTH_TOKEN | No | Bearer token for /mcp HTTP endpoint. Set to a random hex string to protect the MCP server. |
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 |
|---|---|
| terminal_executeA | Execute a shell command in an isolated Debian Linux sandbox. Commands run in bash. Each call is independent — no state (shell variables, working directory) persists between calls (however filesystem does persist). Use the working_directory parameter or chain commands with && to control execution context. To write files or pass data without shell escaping, use the stdin parameter (e.g., command="cat > file.txt" with content in stdin). Commands time out after 120 seconds by default (override with the timeout parameter for long-running operations). |
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 1 tool
There is only one tool, so there is no possibility of confusing it with another tool. Its purpose is clearly defined as executing shell commands in a sandboxed Linux environment.
The single tool name terminal_execute follows a clear verb_noun pattern and accurately reflects its function. With only one tool, there are no naming inconsistencies or conflicting conventions.
A one-tool server is minimal, but terminal_execute is a broad and powerful primitive that can handle filesystem operations, package management, script execution, and more. The count feels slightly thin but is justifiable for a sandbox execution server.
Arbitrary shell command execution covers the full range of expected sandbox operations, including reading, writing, modifying, and deleting files, as well as running processes and installing software. The stdin and timeout parameters further fill practical gaps.