chatgpt-box-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | Host to bind for HTTP mode. Defaults to '127.0.0.1'. | 127.0.0.1 |
| MCP_PORT | No | Port to bind for HTTP mode. Defaults to '3000'. | 3000 |
| BOX_API_KEY | Yes | Your Box by ASCII API key. Read from the MCP server's environment. Required for all operations. | |
| MCP_TRANSPORT | No | Transport for the MCP server. Defaults to 'stdio'. Set to 'http' for local HTTP mode. | stdio |
| MCP_HTTP_TOKEN | No | Bearer token required when binding to a non-loopback address in HTTP mode. |
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_listA | Find the user's Box environments and inspect their current lifecycle states. |
| box_getA | Inspect one Box environment after create, stop, resume, or fork operations. |
| box_createA | Provision a paid Box Linux environment owned by the configured Box account. This changes external state and starts billable runtime. |
| box_stopA | Stop a Box and snapshot its disk. force=true may irreversibly lose changes since the last successful snapshot and should only follow a refused normal stop. |
| box_resumeA | Resume an archived Box, restarting billable runtime on a fresh machine. |
| box_forkA | Create a new paid Box from an existing snapshot. The source Box is not modified. |
| box_execute_commandA | Run a shell command inside a Box and wait up to 60 seconds. The command may modify files, install software, access configured credentials, or affect external systems. Use box_job_start for longer work. |
| box_read_fileB | Read a file relative to the Box work directory. Results are capped for model safety. |
| box_write_fileA | Create or replace a file relative to the Box work directory. Existing content at the path is overwritten. |
| box_list_eventsC | Inspect recent lifecycle and work events emitted by a Box. |
| box_open_desktopA | Create a secret-bearing desktop streaming URL for the user to inspect the Box. Do not log, persist, or share the returned URL. |
| box_job_startA | Start a long-running shell job in a Box. The job runs independently after this tool returns and may modify the machine or external systems. |
| box_job_statusA | Check whether a background job is running, succeeded, failed, or was cancelled. |
| box_job_logsB | Read the tails of stdout and stderr for a background job. |
| box_job_cancelA | Send SIGTERM to a running background job and its process group. Partial file or external changes are not rolled back. |
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 15 tools
Each tool targets a distinct aspect of Box management: lifecycle operations (list, get, create, stop, resume, fork), file operations (read, write), command execution (execute_command, job_start), job monitoring (status, logs, cancel), plus events and desktop access. No two tools overlap in purpose.
All tools follow a consistent box_verb_noun pattern, e.g., box_list, box_create, box_read_file, box_job_status. The naming is uniform and predictable, making it easy to infer what each tool does from its name alone.
15 tools is a well-scoped count for a full-featured Box management server. Each tool covers a distinct necessary functionality without bloat, staying within the ideal range for a comprehensive tool set.
The tool set covers the full lifecycle of a Box environment including creation, inspection, stopping, resuming, and forking, plus file operations, command execution, background job management, events, and desktop access. No obvious gaps are present for the stated domain.