DOCUMENT WORKFLOWS / Box
Box hosted MCP
Connects assistants to Box search, files, metadata and document workflows under an authenticated identity and administrator-controlled tools.
“Hosted Model Context Protocol (MCP) server”
01 / THE REASONING
Why this made the selection.
- Separates account identity, application scopes and content permissions.
- Documents individual tool defaults and administration requirements.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- https://developer.box.com/guides/box-mcp
- https://developer.box.com/guides/box-mcp/setup
- https://developer.box.com/guides/box-mcp/permission-aware-access
- https://developer.box.com/guides/box-mcp/tools
- https://support.box.com/hc/en-us/articles/43847256139923-Managing-Box-MCP-Servers
- Round 2 reread of acquired publisher setup and permission evidence; see immutable wave review.
Our findings
- The permissions reference separates scopes from file access; broader scopes cannot grant otherwise inaccessible content.
- The tool table enables some writes by default and requires administrative activation for others.
- Current admin guidance says all plans; the older GA announcement said Business and above. Plan-specific AI, Sign and DocGen limits remain.
- MCP lane cross-review compared retained publisher setup/capability evidence with this proposed record before integration; no installation or authenticated calls were performed.
- Box evaluates collaboration, inherited folder access and application scopes on each request; service accounts do not gain enterprise-wide access automatically.
Not established by this review
- Authentication, live tool execution, hosted implementation and security isolation were not tested.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Connect a server deliberately.
- Enable the chosen integration in Box Admin Console.
- For a custom client, create credentials, register its redirect URI and select only needed scopes.
- Connect through OAuth; confirm the identity, accessible folders and enabled tools before making changes.
- Choose the intended user or service account and collaborate that identity only onto required folders; use dedicated integration credentials and minimum scopes.
Before you start
- A Box account and administrator-enabled integration.
- Custom clients need protected OAuth client credentials.
Documented configuration example
Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.
{
"mcpServers": {
"box-hosted": {
"type": "http",
"url": "https://mcp.box.com"
}
}
} 04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
https://developer.box.com/guides/box-mcp
Supports: summary, upstreamDescription, whySelected, bestFor, limitations, review, install, access, compatibility, transports, configExample
https://developer.box.com/guides/box-mcp/setup
Supports: summary, upstreamDescription, whySelected, bestFor, limitations, review, install, access, compatibility, transports, configExample
https://developer.box.com/guides/box-mcp/permission-aware-access
Supports: summary, upstreamDescription, whySelected, bestFor, limitations, review, install, access, compatibility, transports, configExample
https://developer.box.com/guides/box-mcp/tools
Supports: summary, upstreamDescription, whySelected, bestFor, limitations, review, install, access, compatibility, transports, configExample
https://support.box.com/hc/en-us/articles/43847256139923-Managing-Box-MCP-Servers
Supports: summary, upstreamDescription, whySelected, bestFor, limitations, review, install, access, compatibility, transports, configExample