box-mcp
Box MCP
Use the active Box MCP connection for operations and verification. Before choosing a workflow, discover available tools through the client's tool search or MCP tools/list; runtime schemas govern names, inputs, and outputs. If a capability is unavailable, explain the blocker rather than silently switching to CLI, REST, or another identity. SDK application development and custom MCP servers are outside this skill's scope.
Connect and diagnose
For an existing connection, call who_am_i to establish the Box user ID and login. Reuse that identity until reconnection or an authorization change requires another check.
When setup is needed:
- Identify the client and follow its supported-platform guide, preferring its Box integration or connector flow.
- For a custom connection to
https://mcp.box.com, follow the setup guide. Unlisted integrations require admin-generated credentials, the client's redirect URI, and appropriate scopes. Preserve existing client configuration and use its credential storage; keep secrets out of chat, committed files, and command history. - Complete client authorization, discover tools, and verify the intended user with
who_am_i. Connection-only setup needs no content mutation.
For missing or disabled tools, check discovery, integration availability, scopes, actor permissions, and product entitlements; absence alone does not establish the cause. Box omits admin-disabled tools from discovery, but listed tools can still fail permission or entitlement checks or be disabled mid-session. In admin tool settings, a custom integration or platform-app configuration overrides enterprise defaults. Refresh discovery after an authorized settings change; reopen clients that retain a stale catalog. Do not widen access to bypass a denial.