mcp-box
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | HTTP bind address | 127.0.0.1 |
| PORT | No | HTTP port | 3333 |
| BOX_API_KEY | Yes | Box dashboard API key; never sent to the MCP client | |
| ALLOW_WRITES | No | When false, deny non-read tools | true |
| BOX_BASE_URL | No | API base | https://ascii.dev/api/box/v1 |
| MCP_BOX_MODE | No | isolated or trusted | isolated |
| MCP_BOX_AUDIT_PATH | No | Optional audit JSONL path |
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 |
|---|---|
| box_createA | Create a Box cloud computer. Isolated mode always uses noEnv. Waits until ready when possible. |
| box_listB | List boxes for the account. |
| box_getA | Get box state. Desktop URLs are redacted in the summary field. |
| box_execC | Run a shell command in a ready box. timeoutSeconds is capped at 60. |
| box_exec_backgroundA | Start a long command via nohup under .mcp-box-jobs// and return immediately. |
| box_job_statusB | Poll background job state from .mcp-box-jobs// files. |
| box_read_fileA | Read a file relative to the box workdir. |
| box_write_fileB | Write a file relative to the box workdir. |
| box_download_artifactA | Download an artifact as base64 (max ~2MB). Prefer box-side tools for larger files. |
| box_desktopB | Get a secret-bearing desktop/noVNC URL. Never log the full URL. |
| box_stop_and_waitA | Stop a box and wait until archived. Requires confirm:true. force requires trusted mode. |
| box_resumeA | Resume an archived box and wait until ready. |
| box_forkA | Fork a box from its latest snapshot. Isolated forks always use noEnv. |
| box_interruptA | Best-effort interrupt of prompt work on a box (not shell background jobs). |
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 14 tools
Each tool targets a distinct operation: lifecycle (create/list/get/resume/stop/fork), execution (exec/exec_background/job_status/interrupt), file access (read/write/download), and desktop. The overlap between exec and exec_background is clear from their descriptions—one is synchronous with a timeout, the other is asynchronous via nohup.
All tools share the 'box_' prefix and use lowercase verbs or verb_noun patterns (e.g., box_create, box_read_file, box_stop_and_wait). The naming is uniformly descriptive and follows a recognizable convention throughout.
14 tools is well-scoped for a cloud computer management server, covering lifecycle, command execution, job handling, file operations, and desktop access without being excessive. Each tool serves a distinct purpose and earns its place.
The surface covers the major workflows: box lifecycle (create, get, list, resume, stop, fork), command execution (foreground, background, interrupt, job status), and file operations (read, write, download). Minor gaps exist, such as no explicit delete/destroy tool and no direct retrieval of background job stdout/stderr, but agents can work around these with existing tools.