Box MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | Environment: development or production. Default is development. | development |
| AUTH_TYPE | No | Authentication method: oauth or ccg. Default is oauth. | oauth |
| LOG_LEVEL | No | Logging level: debug, info, warn, error. Default is info. | info |
| AUTH_TOKEN | No | Bearer token for HTTP transport authentication | |
| BOX_CLIENT_ID | No | Box app client ID | |
| MCP_TRANSPORT | No | Transport: stdio or http. Default is stdio. | stdio |
| MCPSERVER_PORT | No | Port for HTTP server. Default is 3000. | |
| BOX_CLIENT_SECRET | No | Box app client secret | |
| BOX_ENTERPRISE_ID | No | Box enterprise ID (required for CCG authentication) |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| box_save_documentsB | Save multiple documents to Box storage with automatic folder creation |
| box_read_documentB | Read document content without saving locally |
| box_manage_foldersC | Create, move, rename, or delete folders by path or ID |
| box_explore_storageC | Return a tree structure of folders/files starting at a path |
| box_search_contentC | Search Box for files and folders with optional filters |
| box_share_contentC | Create shared links and/or add collaborators to files or folders |
| box_analyze_documentC | Use Box AI to analyze a document (summarize, Q&A, extract, translate) |
| box_update_shared_linkC | Update shared link settings for a file or folder |
| box_remove_shared_linkB | Remove shared link from a file or folder |
| box_update_collaboratorsB | Update collaborator roles or remove collaborators on a file/folder |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| share_file | Create a shared link for a Box file with customizable permissions |
| analyze_document | Use Box AI to analyze a document with specific questions or tasks |
| organize_folder | Organize files in a folder by creating subfolders and moving files |
| bulk_upload | Upload multiple files to Box with folder organization |
| collaboration_setup | Set up collaboration on a Box file or folder with specific users |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Box File | Access to a specific Box file by ID |
| Box Folder | Access to a specific Box folder by ID |
| Box Search | Search Box content with query parameters |
| Box Storage Info | Current user's Box storage quota and usage |
| Recent Files | Recently accessed files in Box |
| Root Folder Tree | Complete folder structure from root |
TDQS
Scored across 10 tools
Most tools target distinct operations, but box_share_content overlaps with box_update_shared_link, box_remove_shared_link, and box_update_collaborators since sharing can involve both links and collaborators. box_manage_folders is also broad and could be confused with box_explore_storage for folder operations.
All tools share a consistent box_ prefix and mostly follow a verb_noun pattern. Minor inconsistencies exist such as box_save_documents vs box_read_document (plural mismatch) and the generic box_manage_folders instead of a specific verb like create/update/delete.
Ten tools is well-scoped for a Box storage MCP server covering document operations, folder management, search, sharing, and AI analysis. Each tool earns its place without overwhelming the agent.
The tool set covers core storage workflows: save, read, organize, explore, search, share, and analyze. Gaps include no direct file deletion (only folders) and no explicit file download or versioning, but agents can work around most limitations.