How to Connect Cline to Box: Official MCP Integration Guide
Connecting Cline to Box enables autonomous coding agents to browse, search, and edit files inside secure Box enterprise folders. This guide walks through registering a Custom App in the Box Developer Console, connecting Cline to the hosted Box MCP server, and centralizing agent workspace storage using Fast.io.
Understanding the Cline and Box Integration Model
An AI coding agent like Cline can write code at high speed, but it remains trapped in a local sandbox unless you connect it to your team's live file systems. Connecting Cline to Box lets your autonomous coding agent browse, search, and edit files inside secure Box enterprise folders. By establishing this connection, your agent can read API definitions, scan design specs, and write code modifications directly to your cloud storage repository.
Box now supports one integration path: the remote Box MCP server at https://mcp.box.com. The community-maintained self-hosted Python server, box-community/mcp-server-box, was archived on 30 April 2026 and its README directs users to migrate to the hosted server. Do not start a new integration on it.
Connecting to the hosted endpoint requires registering a Box application for OAuth, authorizing it in the Box Admin Console, and adding a remote server entry to Cline's local configuration settings. Once active, Cline can call Box tools directly from its workspace panel. This setup enables collaboration between humans and software agents, ensuring files remain persistent across developer sessions.
How to Register a Box App for the Hosted MCP Server
Before Cline can reach your Box content, you need a Box application that the hosted MCP server can authenticate against, and a Box administrator has to authorize it.
To register the application, perform the following steps:
Log in to the Box Developer Console.
Click Create New App and select Custom App.
Choose User Authentication (OAuth 2.0) as the authentication method. Browser-based OAuth is the flow the hosted server uses, and it keeps each developer inside their own Box permission set rather than granting a shared service account.
Under Application Scopes, check the read and write permissions for files and folders to grant your agent file modification rights.
Navigate to App Access Level and select App + Enterprise Access to let the agent reach files across your organization, or App Access for a scoped sandbox.
Copy the Client ID and Client Secret from the Configuration tab.
A Box Administrator must then authorize the application before it can request access tokens. Copy the Client ID from your Developer Console, navigate to Apps in the Box Admin Console, select Custom Apps, click Add App, enter the Client ID, and authorize the integration.
How to Connect Cline to the Hosted Box MCP Server
With the app authorized, you connect Cline to https://mcp.box.com by editing Cline's configuration file, cline_mcp_settings.json. This file is separate from other editor settings and stores all external tool definitions.
Locate cline_mcp_settings.json based on your operating system:
macOS:
~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.jsonWindows:
%APPDATA%\Code\User\globalStorage\saoudrizwan.claude-dev\settings\cline_mcp_settings.jsonLinux:
~/.config/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
Add the remote server entry to the mcpServers object. Because the server is hosted, you declare a URL and a transport rather than a local command:
{
"mcpServers": {
"box": {
"type": "streamableHttp",
"url": "https://mcp.box.com",
"disabled": false,
"autoApprove": []
}
}
}
Save the file and open the Cline panel in Visual Studio Code. Cline connects to the endpoint and starts the OAuth flow in your browser. Sign in with your Box account and approve the requested scopes. One detail catches people out: the callback URL your client uses has to be pre-registered in the Box application's OAuth 2.0 Redirect URI list, because Box does not support dynamic client registration. Add https://vscode.dev/redirect for VS Code before you connect, or the flow fails with an error from Box.
Once the flow completes, Cline displays the active Box tools. It can now search folders, read files, and write updates, allowing the agent to fetch context from your Box content.
If you find a guide that tells you to clone box-community/mcp-server-box and run it with uv, check the date. That repository is archived and read-only, and Box's own README on it now points to the hosted server as the supported path.
Connect Cline to Box workspaces via Fast.io
Give your Cline agent access to Box files in a secure, collaborative workspace with automatic semantic indexing and unified remote MCP access. Start your 14-day free trial.
Centralizing Agent Workspace Storage with Fast.io
Connecting straight to Box works well for a single developer, but it introduces bottlenecks for collaborative teams. Every developer needs their own authorized app and their own OAuth session, and an administrator has to approve each one. Additionally, high-frequency file reads and writes from an active agent can consume local network bandwidth and quickly draw down Box API rate limits.
To resolve these issues, teams can use Fast.io as a centralized workspace. Fast.io is a collaborative cloud workspace platform built for agentic teams. Rather than running a local server wrapper for every cloud storage provider, developers can use Fast.io's Cloud Import feature. This allows you to import folders from Box, Google Drive, OneDrive, and Dropbox directly into a shared Fast.io workspace using secure OAuth authentication, with no local hardware requirements.
Once files are imported, Fast.io acts as your persistent, intelligent storage layer. If you enable Intelligence Mode on your workspace, the platform automatically indexes all imported files for semantic search and Q&A. The coding agent can then access these files through a single, consolidated remote MCP endpoint. This unified endpoint means you configure one connection inside Cline, and your agent gets access to Box and other cloud files.
Furthermore, Fast.io protects your files by keeping a per-file version history and an append-only audit log. If an agent writes incorrect code, you can restore previous versions with a single click. Every organization starts with a 14-day free trial, which requires a credit card. Plans are structured to scale with your team's needs, offering Starter, Business, or Growth tiers. For detailed plans, visit the pricing page.
Frequently Asked Questions
Where is the official Box MCP server?
Box hosts an officially supported remote MCP server at https://mcp.box.com. The older community project, box-community/mcp-server-box, was archived in April 2026 and its README directs users to the hosted server instead, so new integrations should use the remote endpoint.
How do I authorize a Box app for my coding agent?
To authorize your Custom App, copy the Client ID from the Box Developer Console. Then, navigate to Custom Apps in the Box Admin Console, click Add App, enter your Client ID, and authorize the application to enable JWT access tokens.
Can Cline run files inside a sandboxed Box folder?
Cline executes terminal commands in your local computer or container workspace, not within the Box cloud. The Box MCP server acts as a bridge for file transfers. To run code, Cline downloads the files from Box, runs them locally, and uploads the results back to Box.
Related Resources
Connect Cline to Box workspaces via Fast.io
Give your Cline agent access to Box files in a secure, collaborative workspace with automatic semantic indexing and unified remote MCP access. Start your 14-day free trial.