microsandbox-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| sandbox_runA | Create an ephemeral sandbox, run a shell command, return the output, and destroy the sandbox. Best for quick one-off tasks like running a script, checking a command, or testing code. |
| sandbox_createA | Create and boot a persistent named sandbox with full configuration. The sandbox stays running until explicitly stopped. |
| sandbox_listA | List all sandboxes with their status. |
| sandbox_inspectA | Get detailed information about a specific sandbox including full configuration. |
| sandbox_stopA | Stop a running sandbox. Use force to kill with SIGKILL instead of graceful SIGTERM. |
| sandbox_removeA | Remove a sandbox. Must be stopped unless force is true. |
| sandbox_execA | Execute a command inside a running sandbox and return stdout/stderr/exit code. |
| sandbox_shellA | Execute a shell command or script string inside a running sandbox. Interprets pipes, redirects, and shell syntax. |
| sandbox_fs_readA | Read a file from the sandbox filesystem and return its contents as text. |
| sandbox_fs_writeA | Write content to a file inside the sandbox. Creates parent directories as needed. |
| sandbox_fs_listB | List directory contents inside the sandbox. |
| sandbox_fs_mkdirA | Create a directory with parent directories inside the sandbox. |
| sandbox_fs_removeC | Remove a file or directory inside the sandbox. |
| sandbox_fs_statA | Get file or directory metadata (kind, size, mode, modified time) inside the sandbox. |
| volume_createA | Create a named persistent volume. Volumes survive sandbox restarts and can be shared across sandboxes. |
| volume_listA | List all named volumes. |
| volume_removeB | Remove a named volume. |
| check_installedA | Verify that msb and libkrunfw are available on the system. Returns installation status. If not installed, the server can attempt to install them. |
| sandbox_metricsA | Get live resource usage metrics (CPU, memory, disk, network) for a running sandbox. |
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 19 tools
Each tool targets a distinct operation with clear prefixes (sandbox_, volume_, check_installed). The subtle overlap between sandbox_exec and sandbox_shell is resolved by their descriptions (command vs shell syntax).
All tool names follow a consistent verb_pattern: sandbox_<action> for sandbox tools, volume_<action> for volume tools, and check_installed conforms to verb_noun. No mixing of conventions.
19 tools cover sandbox lifecycle, filesystem operations, and volume management comprehensively. While slightly above the typical 3-15 range, the count is justified by the breadth of functionality.
The tool set covers the full sandbox lifecycle (create, run, exec, shell, stop, remove), filesystem operations, monitoring via metrics, and volume management. No obvious gaps for the domain.