Skip to main content
Govern how your AI clients search, read, and change Box content by connecting Box to C1. Your MCP server catalog has two Box entries. Both expose governed MCP tools, but they come from different places:
  • Box MCP — listed as plain Box in your catalog. C1 registers Box’s own hosted MCP server (mcp.box.com) as an MCP server C1 governs. Users authorize with OAuth credentials you create in the Box Admin Console.
  • Box API — C1 hosts its own MCP server that translates the Box API into tools. Users authorize with an OAuth app you create in the Box Developer Console.
Use Box MCP for Box’s own tool set, including Box Hubs, with per-category tool controls in the Box Admin Console. Use Box API when you need users and groups, Box Sign, or retention and legal hold data, or want to start read-only and add write access through scopes. You can register both.

Connect each user with their own Box account

Per-user OAuth is the recommended method for both entries. Each person authorizes C1 with their own Box account. Every tool call then runs under that user’s Box identity, reaches only the content that user can already access, and appears in Box as that user’s activity. Don’t create a Box Server app — Box’s Client Credentials Grant or JWT server authentication — for C1. A server app acts as a service account rather than the person calling the tool, and C1 doesn’t connect to Box with one.

Box plans and the tools they support

Some Box products depend on your Box plan and on whether your Box admin has turned the product on. Box documents availability as follows (Free developer plan): Availability also varies by contract, so your enterprise may not have a product its plan normally includes. Two places in Box show it directly:
  • In the Box Developer Console, an app shows the Manage AI scope only when Box AI is available to your enterprise.
  • In the Box Admin Console, on the Box MCP Server tab under Integrations, the Box AI & Agents and Box Hubs tool categories appear only when your enterprise has those products.
Tools for a product your enterprise doesn’t have return an error from Box. Approve only the tools that match your plan.
Add a scope in C1 only after you enable it in Box. Box rejects the whole sign-in with an invalid_scope error when C1 requests a scope the Box app or integration credentials don’t have, which blocks every user of the server from connecting until you remove the scope or enable it in Box.
C1 registers as a client of Box’s hosted MCP server (Box MCP server) rather than translating the Box API itself. Your users’ AI clients only see C1-governed MCP tools, and C1 passes each tool call to mcp.box.com under the calling user’s authorized session, then returns the result. The tools are the ones Box’s MCP server provides — C1 doesn’t reshape or add to them.

Before you begin

  • AI access management must be enabled for your tenant. See Enable AI access management.
  • A Box Admin or Co-Admin account to turn on the Box MCP server, set tool access, and create integration credentials in the Box Admin Console.
In your MCP server catalog, this option is listed as Box — distinct from the Box API entry, which connects through C1’s own MCP server. If you don’t see either, contact the C1 support team to enable it for your tenant.

Turn on the Box MCP server and its tools

Box controls whether its MCP server is available and which of its tools are on, and some tools start turned off (Set up the MCP server, Manage Box MCP Server tool access).
1
In the Box Admin Console, select Integrations.
2
Search for Box MCP server.
3
Next to Box MCP server, open its status menu and choose the option that makes it available to users.
4
Open the Box MCP Server tab.
5
For each tool category your users need — Authentication & Users, Search, Files & Folders, Collaboration, and, when your plan includes them, Box AI & Agents and Box Hubs — choose Enable read-only tools, Enable read & write tools, or Custom configuration.
6
For any category you don’t want available, choose Disable all tools.
Box saves each change immediately and applies it to every user in your enterprise.Box turns these tools off by default (Box MCP tools). Choosing Enable read & write tools for their category, or turning them on individually under Custom configuration, makes them available:
  • Moving files and folders: move_file, move_folder
  • Changing file and folder properties: update_file_properties, update_folder_properties
  • Writing metadata: set_file_metadata, set_folder_metadata, update_metadata_template
  • Uploading a new file version: upload_file_version
  • Creating shared links and changing collaborations: add_file_shared_link, add_folder_shared_link, create_collaboration, update_collaboration
  • Issuing upload and download URLs: get_upload_url, get_download_url
  • Updating a hub: update_hub
C1 lists Box’s tools whether or not they’re turned on in your enterprise. A tool that’s turned off in the Box Admin Console returns an error when called, so approve tools in C1 to match the tool access you’ve set in Box.

Create Box MCP integration credentials

Box’s MCP server doesn’t support dynamic client registration, so create a client ID and secret in the Box Admin Console for C1 to use (Set up the MCP server).
1
In the Box Admin Console, select Integrations and search for Box MCP server.
2
Hover over Box MCP server and select Configure.
3
In the Additional Configuration section, select + Add Integration Credentials.
4
Enter a name such as C1 and select Save.
5
Expand the new entry.
6
Set the Redirect URI to the value that matches your C1 tenant’s domain:
  • Default instance: https://accounts.conductor.one/auth/callback
  • EU data residency instance: https://accounts.c1eu.ai/auth/callback
7
Under Access Scopes, select the scopes described in Box MCP scopes.
8
Copy the Client ID.
9
Copy the Client Secret.
The integration credentials are ready to register in C1.

Box MCP scopes

Box lists these scopes for its MCP server (Remote Box MCP server). C1 requests the required scope automatically. Add an optional scope in C1 only after you select it on the integration credentials.Scopes set the most a user’s connection can do. Users still reach only the content they can already view or edit in Box, and the tool categories you set in the Box Admin Console still apply.

Register the Box MCP server in C1

With your integration credentials ready, register the server.
1
Follow Register an MCP server and select Box from the catalog.
2
When you configure authentication, choose OAuth2 — per-user passthrough.
3
Enter your Client ID and Client Secret.
4
Optional. Add ai.readwrite to the scopes if your enterprise has Box AI and you selected it on the integration credentials.
5
Save your changes.
The first time a user calls a Box tool from their AI client, they’re prompted to sign in to Box and approve access.
The Box entry also accepts a Box access token as a bearer credential. Box access tokens expire after about an hour and C1 can’t refresh them, so use this only for short-lived testing.

How Box MCP credentials are shared

Every tool call runs under the calling user’s own Box identity, and Box attributes each action to that user. C1 also records each call in the AI tool usage audit log.

Discover and govern Box MCP tools

After you register the server, C1 discovers Box’s MCP tools. Discovered tools appear on the server’s Tools tab.Each tool starts as either Pending review or automatically Approved, depending on the option chosen when the server was set up or your tenant’s default tool settings in AI > MCPs > Settings. See Require tool approval and Default tool classification.Before anyone can call a Box tool, it must be approved, added to a toolset, and bound to an access profile. Continue to Govern tools and toolsets to set this up.
Tool discovery runs even if authentication isn’t complete, so seeing discovered tools doesn’t confirm that a user can connect. You confirm access when an approved user successfully calls a Box tool from their AI client.

Manage your Box MCP credentials

  • Rotate the client secret in the Box Admin Console under Integrations > Box MCP server > Configure, then update the secret on the server’s authentication settings in C1.
  • Change what users can do by adjusting tool access on the Box MCP Server tab, or the integration’s Access Scopes. Scope changes apply the next time a user authorizes.

Frequently asked questions about connecting Box to C1

Choose Box MCP for Box’s own tool set, including Box Hubs, controlled per category in the Box Admin Console. Choose Box API when you need users and groups, Box Sign, or retention and legal hold data, or want to start read-only. You can register both; each is governed separately in C1.
The most common cause is a scope added in C1 that isn’t enabled on the Box app or integration credentials, which makes Box reject the sign-in with an invalid_scope error. Remove the scope in C1, or enable it in Box first. A redirect URI that doesn’t exactly match the C1 value for your tenant also blocks sign-in.
Your Box plan or admin settings don’t include that product, or the connection doesn’t have the scope it needs. Check Box plans and the tools they support, then confirm Box AI or Box Hubs is available to your enterprise and the scope is granted.
Box grants the user, group, and enterprise management scopes only when the person who authorized C1 is a Box Admin or Co-Admin. Have an admin connect, or leave those tools unapproved.
Box turns those tools off by default. Turn them on in the Box Admin Console, on the Box MCP Server tab under Integrations.
Box Verified Enterprise can require a different Box sign-in address than the standard one (OAuth 2.0 without SDKs). If sign-in fails for your enterprise, contact the C1 support team.
No. C1 connects to Box with OAuth on behalf of each user. Box’s Client Credentials Grant and JWT apps act as a service account, which hides who took each action in Box.