shell-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SHELL_MCP_SHELL | No | Shell used inside the sandbox; this is the only shell used, with no sh fallback (equivalent to --shell). | bash |
| SHELL_MCP_SANDBOX | Yes | Name of the existing microsandbox sandbox to run commands in (equivalent to --sandbox). Flags win over environment variables. | |
| SHELL_MCP_HOST_ROOT | Yes | Absolute host path of the project folder mounted into the sandbox (equivalent to --host-root). Normalized as a Windows path, trailing separator stripped, and must exist on disk. | |
| SHELL_MCP_GUEST_ROOT | Yes | Absolute POSIX path inside the sandbox where the host folder is mounted (equivalent to --guest-root). A trailing '/' is stripped. | |
| SHELL_MCP_MAX_OUTPUT | No | Maximum number of output characters retained per call (equivalent to --max-output). | 30000 |
| SHELL_MCP_MAX_TIMEOUT | No | Maximum timeout a call may request (equivalent to --max-timeout). | 600s |
| SHELL_MCP_DEFAULT_TIMEOUT | No | Default timeout applied to shell commands (equivalent to --default-timeout). | 120s |
| SHELL_MCP_REWRITE_OUTPUT_PATHS | No | Controls rewriting of guest paths back to host paths in command output (equivalent to --no-rewrite-output-paths). Set to 0, false or no (any case) to turn rewriting off; any other value leaves it on. | on |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| shellA | Run a shell command (bash) inside an isolated Linux sandbox, not on the host machine. The host directory /app is mounted in the sandbox at /workspace; the command starts in /workspace and only files under that directory are shared with the host. The working directory persists between calls, but environment variables and shell state (aliases, functions) do not. Do not rely on cd across parallel calls: each starts in the directory current when it starts, and the last to finish sets it. Default timeout is 120 seconds, maximum 600 seconds (timeout_ms). Use run_in_background for servers and other long-running processes; it returns a job id to use with shell_output, shell_kill and shell_list. Interactive programs (editors, pagers, prompts waiting for input) are not supported. Paths in output under /workspace are shown as host paths under /app. To read or edit files, use your file tools with host paths (/app) rather than shell commands. |
| shell_outputA | Read new output from a background job started with shell, since the last call. Reports whether the job is still running and its exit code once finished. |
| shell_killA | Stop a background job started with shell and report whether it has stopped. |
| shell_listA | List background jobs started in this session, with their state and command. |
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 4 tools
The four tools have clearly distinct roles: `shell` starts commands and jobs, while `shell_output`, `shell_kill`, and `shell_list` operate specifically on background jobs. There is minimal risk of confusing foreground command execution with background job management.
All tools share the `shell` prefix, and background job operations follow a consistent `shell_<operation>` pattern. The main `shell` tool is the only slight deviation, but it is still readable and predictable.
Four tools is well scoped for a sandboxed shell server: one execution tool plus three focused background-job controls. Each tool earns its place without redundant surface area.
The tool set covers foreground execution, background job launch, output streaming, termination, and listing. Given the stated non-support for interactive programs, no obvious lifecycle gaps remain.