Skip to main content
Box’s MCP server connects your organization’s Box content to Airia agents. Once connected, agents can search, read, and manage files and folders in Box, all while respecting the connected user’s existing Box permissions. Box is a catalogue server, so it shows up automatically for organizations in Default Mode. In Custom Mode, an admin needs to approve it on the Server Management page before it can be added to a Gateway or Deployment.

What It Can Do

See Tools and Required Scopes below for the full list of tools behind these capabilities.
Box tools always act on behalf of the connected user and respect that user’s existing Box permissions. If someone can’t access a file in Box directly, connecting Box to Airia doesn’t change that.

Prerequisites

  • A Box account on a plan that includes access to Box’s MCP server.
  • A Box Admin to complete the one-time setup below. Regular Box users can’t register the integration themselves.

One-Time Admin Setup

Box requires an admin to register Airia in the Box Admin Console before anyone in your organization can connect. This only needs to happen once per organization.
1

Open the Box MCP server integration

Sign in to the Box Admin Console as a Box Admin, click Integrations in the left sidebar, search for Box MCP server, hover over the result, and click Configure.
2

Add integration credentials

In the Additional Configuration section, click + Add Integration Credentials. Enter a name for the integration, for example Airia MCP Gateway, and click Save.
3

Copy the Client ID and Client Secret

Expand the entry you just created and copy the Client ID and Client Secret. You’ll need both when connecting Box in Airia.
4

Set the redirect URI

In the Redirect URI field of that same entry, enter:
5

Enable access scopes and save

Under Access Scopes, enable root_readwrite, ai.readwrite, and docgen.readwrite, then click Save.
docgen.readwrite requires a Box Enterprise Advanced license. If your organization is on a lower plan, you can skip it, but the Doc Gen tools won’t be usable.

Connecting Box in Airia

Once the admin setup above is done, anyone building a Gateway or Deployment can add Box as a server:
1

Add Box as a server

Add Box as a server on a Gateway or Deployment.
2

Enter the Client ID and Client Secret

Enter the Client ID and Client Secret from the admin setup step above.
3

Sign in with your Box account

Sign in with your own Box account when prompted.
Because Box uses an admin-configured OAuth app, the Client ID and Client Secret are configured in Airia at the Tenant level, so this step only happens once for your organization. Each person who connects still signs in with their own Box account, and their access is always personal to them, even when the underlying app registration is shared. See Tenant vs. Personal Level App Credentials for more on how this works.

Tools and Required Scopes

Box’s scopes are broader than most MCP servers documented here. Just three scopes cover every tool: Grant all three during the One-Time Admin Setup above so every tool below is available.
Tools marked with only work on items that meet all of the following: no external collaborators on the item itself, no shared link on the item itself, and no external collaborators or shared links on any parent folder up to the root.

User and Authentication

Files and Folders

Read-only

Write

get_download_url and get_upload_url require the agent to make a direct network request to transfer the file, which only works in code-executing environments. If your client allowlists domains, it needs upload.box.com, upload.app.box.com, upload.ent.box.com, dl.boxcloud.com, and public.boxcloud.com (these vary by Box Zone).

Collaboration

Read-only

Write

Box AI

Hubs

Read-only

Write

Doc Gen

Every tool in this category needs docgen.readwrite, which requires a Box Enterprise Advanced license regardless of which scope is granted in Airia.

Read-only

Write

Troubleshooting

Cause: docgen.readwrite requires a Box Enterprise Advanced license. Granting the scope in Airia doesn’t help if your organization’s Box plan doesn’t include it.Fix: Confirm your organization has Enterprise Advanced. If it doesn’t, the Doc Gen tools stay unavailable; every other tool still works normally.
Cause: Both tools return a URL the agent has to fetch or upload to directly, which only works in code-executing environments. If your client allowlists domains, the transfer domain may also be blocked.Fix: Confirm your client can execute code, then allowlist upload.box.com, upload.app.box.com, upload.ent.box.com, dl.boxcloud.com, and public.boxcloud.com (these vary by Box Zone).
Cause: Tools marked only work on items with no external collaborators or shared links, on the item itself or on any parent folder up to the root.Fix: Remove the external collaborator or shared link from the item and its parent folders, or point the agent at a different item that meets that condition.

Learn More