Managing Box MCP Servers

Remote MCP Server is a standardized way for AI Agents to connect and interact with third-party applications like Box, enabling seamless access to content and AI capabilities across platforms. The Box MCP Server acts as a bridge that allows leading AI Agent platforms—such as Copilot Studio and Claude Enterprise—to securely query and utilize Box data and AI-powered tools without exposing raw file content. Through OAuth authorization, users can grant AI Agents controlled access to their Box accounts, enabling intelligent document handling, advanced search, and multi-file AI queries directly within these external AI environments. It exposes existing Box API functionality as a defined set of tools and endpoints, offering an alternative access method for AI Agents rather than introducing new capabilities. 
How these tools are invoked and used—including the specific operations, workflows, and agent integrations—is determined by the application developer or any third-party agent leveraging them; Box does not operate, manage, or control those external applications or agents.

Learn More

To learn more about the tools offered, or explore Box MCP Remote and local servers along with their use cases, visit the developer documentation here.

For Box Admins

Box enables you to manage and add Box MCP Servers to enable seamless connectivity between Box and third-party AI Agents. 
To access and manage predefined Box MCP Servers:

1. In the left sidebar of your Admin Console, click Integrations.
2. Use Categories filter and choose MCP or search for a predefined Box MCP server in the search field search at the top of the window.
3. Beside the selected MCP server, click the state, then select the state you want to enable.

To create a new, unlisted Box MCP server:

1. In the left sidebar of your Admin Console, click Integrations.
2. Use Categories filter and choose MCP or search for a predefined Box MCP server in the search field search at the top of the window.
3. Hover on the Custom Box MCP Server application, then click Configure.
4. In the Additional Configuration section, click + Add Integration Credentials.
5. Copy the generated Client ID and Client Secret.
6. Enter the Redirect URI provided by the external MCP Client.
7. Under Scopes, ensure that Manage AI is selected.
8. See this article and add Integration credentials for customer-instance integrations.

Adding a Box MCP Server on the Client Side

To connect to Box from the AI Agent platform, you need:

• Endpoint URL: https://mcp.box.com
• Client ID and Client Secret: Box generates these in the Integration Credentials section of your Admin Console when configuring the Box MCP Server, above.
• OAuth endpoints: these are the same as for the Box Platform and also exposed according to RFC 8414.
  Exact steps may vary depending on the AI platform.  Refer to your platform’s documentation for client-side setup instructions.  Note that the Box MCP Server currently does not support Dynamic Client Registration.

Adding a Box MCP Server on Copilot Studio side

 Detailed steps and guidance are available in the official Microsoft documentation: Add an MCP Server in Copilot Studio.

To add an MCP server as Tool in Copilot Studio, follow the steps below:
1.    Create a new agent in Copilot Studio:

• Log in to Copilot Studio with a valid account and follow the steps to create a new agent, adding the name and description of your choice.  If you're not familiar with the process of creating agents in Copilot studio, you can follow Microsoft’s support article here.

2.    Add the Box MCP Server as a Tool:

• Go to the Tools page for your agent and select Add a tool.
• Select Model Context Protocol and select the Box MCP Server from the list of available MCP Connector.
• Authorize the connection, entering any information that is needed.
• When you're done, select Add to agent or Add and configure to proceed.

3.    Publish and deploy your agent: 

• Publish your agent and make it available in the channels and to the users of your choice.  If you're not familiar with the process of publishing and deploying agents in Copilot studio, follow Microsoft’s support article here.

Adding a Box MCP Server on the Azure API Center's Enterprise Registry side

 
Create an OAuth 2.0 app in the Azure API Center

If you’re unfamiliar with the process, follow this documentation: Create an OAuth 2.0 app.

To obtain the Credentials from the Box side:

1. In the left sidebar of your Admin Console, click Integrations.
2. In the Box Integrations & Clients tab, scroll down to Individual Integration Controls.
3. Use Categories filter and choose MCP or search for a predefined Box MCP server in the search field search at the top of the window.
4. Hover on the Custom Box MCP Server application, then click Configure.
5. In the Additional Configuration section, click + Add Integration Credentials.
6. Copy the generated Client ID and Client Secret.
7. Enter the Redirect URI provided by the Azure API Center’s Enterprise Registry.
8. Under Scopes, ensure that Manage AI is selected.
9. To add Integration credentials for customer-instance integrations, see this article.

To add an MCP server in Azure API Center's Enterprise Registry, follow the instructions in the official Microsoft documentation: Add an MCP Server in Azure API Center's Enterprise Registry. 

Using Box AI Features with the MCP Server 

When using Box AI in third party applications, the best experience and highest quality results are achieved by accessing the applications through the Box MCP Server.  Using the Box MCP Server ensures full functionality, improved performance, and a seamless user experience.

To manage Box AI API access for Managed Users:  

1. In the left sidebar of your Admin Console, click Box AI.
2. In the Box AI window, click Settings.
3. Ensure that AI API and Official Box Integrations is enabled for all users is selected.
4. If required, ensure that you provided consent to the Box AI terms of usage.

Pricing

The MCP Server is available on all Box plans.

API calls are free only if both of the following conditions are met:

• You are using an app published in the Box Integrations Center, and
• You log in with your own Box account (OAuth).

This is the standard end-user use case (e.g., ChatGPT, Claude, Figma, etc.).

When API calls are charged

API calls are charged in all other cases, for example:

• Non-published Box Platform apps
• Custom integrations or automations
• Use of additional integration credentials from the Box MCP Server
• Service account or scaled/shared workflows

How API Calls Are Charged

If your use case falls into the charged category above, API usage is metered as follows:

You can only use MCP tools that are included in your current Box plan. 

Note

Box AI, DocGen, and Sign are features included in specific Box plans and are subject to plan availability and limits. AI tools require a Box AI-enabled plan, DocGen and Sign depend on plan availability.

MCP Server Activity Report

The MCP Server Activity report provides an overview of the tool usage through your MCP server. 

Specify the date range of the report and run it, or enter usernames/group name and integration name to narrow down the results.

Data columns

MCP ServerActivity report contains the following columns:

• Date
• Integration ID
• Integration name
• Integration client ID
• User name
• User email

For Box Users

Here is a list of integrations that let you use the Box MCP Server directly within supported platforms.