# box/mcp-server-box-remote [Official] [Health: Active]

**Category:** 📂 File Systems  
**Repository:** https://github.com/box/mcp-server-box-remote/  
**GitHub Stars:** 6  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/box-mcp-server-box-remote

## Description
The Box MCP server allows third party AI agents to securely and seamlessly access Box content and use tools such as search, asking questions from files and folders, and data extraction.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "mcp-server-box-remote": {
    "url": "https://mcp.box.com"
  }
}
```

## Documentation

## What box/mcp-server-box-remote does

box/mcp-server-box-remote gives MCP-compatible agent platforms access to Box content and Box AI through a hosted endpoint. It is designed for use with clients and platforms that can connect to remote MCP servers, including Claude, Copilot Studio, and Mistral Le Chat.

The service keeps the source content in Box while allowing authorized agents to query it. Access is controlled through OAuth, so users grant permissions from the client connection flow rather than supplying content directly to another storage system.

## How it works

Clients connect to `https://mcp.box.com` and authorize access using Box OAuth 2.0. The connection uses a bearer access token, with the client typically handling the authorization flow and redirect. Client credentials come from either the predefined Box MCP Server integration in the Box Admin Console or an OAuth application created in the Box Developer Console.

The remote service is an OAuth-protected resource backed by Box’s authorization server. OAuth discovery metadata is available at the Box MCP endpoint, while authorization server metadata is published by Box. Requests to Box APIs require a valid access token.

## Setup and configuration

To configure box/mcp-server-box-remote, first enable or configure the Box MCP server under Admin Console → Integrations. This is the preferred setup path. Some connection flows, including certain registry-based setups, may instead require a custom OAuth app created in the Developer Console.

For a custom app, configure the required redirect URI and scopes, then collect the client ID and client secret. In the MCP client, add the remote endpoint, choose a name, and provide the OAuth details requested by that client. The redirect URI supplied by the client must also be added to the Box app configuration.

Client-specific connection instructions are provided in Box’s remote MCP server guide. OAuth setup details may differ between clients and deployment platforms.

## Tools and capabilities

box/mcp-server-box-remote provides capabilities in three broad areas:

- Identifying the authenticated Box user.
- Reading file content and listing folders.
- Searching for files and folders.
- Asking questions across files with Box AI.
- Extracting metadata and other information with Box AI tools.

The available tool set can change, so consult the remote Box MCP documentation for the current list and detailed behavior.

## Limitations and notes

This is a hosted remote service, not a local deployment. The README directs users seeking a self-hosted or local version to a separate project, so this listing should be selected when a Box-hosted endpoint is acceptable.

A valid OAuth authorization and access token are required. Box API use remains subject to Box’s Terms of Service, and the exact permissions depend on the configured application scopes and the authorization granted by the user. Client support for remote MCP connections and OAuth may vary, so follow the connection guidance for the specific platform.

_Full upstream README: https://allmcps.com/mcp/box-mcp-server-box-remote/readme_