---
title: "Box hosted MCP: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/mcp-servers/box-hosted/
description: "Connects assistants to Box search, files, metadata and document workflows under an authenticated identity and administrator-controlled tools."
---

# Box hosted MCP: review, setup & limitations · Undominated.ai

> Connects assistants to Box search, files, metadata and document workflows under an authenticated identity and administrator-controlled tools.

[← Explore all mcp servers](/mcp-servers/)

DOCUMENT WORKFLOWS / Box

# Box hosted MCP

Connects assistants to Box search, files, metadata and document workflows under an authenticated identity and administrator-controlled tools.

 [See setup guidance ↓](#setup)[Original source ↗](https://developer.box.com/guides/box-mcp)

SOURCE REVIEW

 Reviewed 2026-10-14
 Evidence 5 linked sources
 Publisher Box
 Licence Not established
 [Read what was—and wasn’t—checked ↓](#review)

“Hosted Model Context Protocol (MCP) server”

 [Box · upstream description ↗](https://developer.box.com/guides/box-mcp) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - Separates account identity, application scopes and content permissions.
- Documents individual tool defaults and administration requirements.

### A good fit for

 - Reviewing documents already accessible to a Box user.
- Controlled metadata, folder and document workflows.

### Weigh up before choosing

 - Custom clients need integration credentials; the admin guide says dynamic client registration is unsupported.
- The tool reference includes file content and mutations; do not infer read-only or zero-content-exposure guarantees from overview wording.
- The local community server is deprecated. Hosted availability does not establish access to every plan-specific tool.
- The docgen.readwrite scope requires an eligible Enterprise Advanced licence, and identity permissions still constrain the maximum scope granted to an integration.

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.

[Upstream setup instructions ↗](https://developer.box.com/guides/box-mcp)
 - 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"
 }
 }
} Copy configuration ↗

### Compatibility

Remote MCP clients with Streamable HTTP support

### Transports

Remote HTTP

### Hosted service

 - Reads accessible files and can perform enabled content, metadata, signing or document operations within granted permissions.

### Cost model

Current admin guidance distinguishes published-app OAuth usage from charged custom/API usage; AI, Sign and DocGen retain plan charges.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Publisher setup and capability reference ↗](https://developer.box.com/guides/box-mcp) Checked 2026-10-14 https://developer.box.com/guides/box-mcp Supports: summary, upstreamDescription, whySelected, bestFor, limitations, review, install, access, compatibility, transports, configExample
- [Publisher setup and capability reference ↗](https://developer.box.com/guides/box-mcp/setup) Checked 2026-10-14 https://developer.box.com/guides/box-mcp/setup Supports: summary, upstreamDescription, whySelected, bestFor, limitations, review, install, access, compatibility, transports, configExample
- [Publisher setup and capability reference ↗](https://developer.box.com/guides/box-mcp/permission-aware-access) Checked 2026-10-14 https://developer.box.com/guides/box-mcp/permission-aware-access Supports: summary, upstreamDescription, whySelected, bestFor, limitations, review, install, access, compatibility, transports, configExample
- [Publisher setup and capability reference ↗](https://developer.box.com/guides/box-mcp/tools) Checked 2026-10-14 https://developer.box.com/guides/box-mcp/tools Supports: summary, upstreamDescription, whySelected, bestFor, limitations, review, install, access, compatibility, transports, configExample
- [Publisher setup and capability reference ↗](https://support.box.com/hc/en-us/articles/43847256139923-Managing-Box-MCP-Servers) Checked 2026-10-14 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

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### Airtable MCP Server ↗ Hosted Airtable server exposing bases, records, tables, interfaces and automations as tools over Streamable HTTP. Every connection is scoped to authorised bases and the server enforces existing Airtable permissions, so a read-only base stays read-only through MCP.](/mcp-servers/airtable/)[### Aiven MCP Server ↗ Manages Aiven PostgreSQL, Kafka, applications and other services from an MCP client, through Aiven's hosted OAuth endpoint or a local npx package, with read-only, scope and secret-exposure switches.](/mcp-servers/aiven/)[### Algolia MCP Server ↗ Algolia's managed MCP offerings: Public MCP exposes application-scoped search and recommendations on selected indices for customer-facing agents; Productivity MCP gives user-scoped, read-only exploration and analytics; DevEx MCP serves version-matched API client snippets to coding agents without touching data.](/mcp-servers/algolia/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Inspect resource evidence](/tools/)
- [Choose a host](/agents/)
- [Inspect reusable workflows](/skills/)
- [Use Undominated data](/api/)
