1. Conduid
  2. Developer Tools
  3. box/mcp-server-box-remote
MCP server · Developer Tools

box/mcp-server-box-remote

by · github.com/box/mcp-server-box-remote

Securely connect AI agents to your enterprise content in Box

Unclaimed MIT last commit a year ago devtools
InstallView source
51Fair

Scored 6 months ago · breakdown

About box/mcp-server-box-remote

box/mcp-server-box-remote is an MCP server published by box in the Developer Tools category: securely connect AI agents to your enterprise content in Box.

The repository has 6 stars and 8 forks, with the last commit a year ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

From source
git clone https://github.com/box/mcp-server-box-remote

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about box/mcp-server-box-remote

Powered by Claude · Grounded in docs

I know everything about box/mcp-server-box-remote. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

Static checks derived from the repository 6 days ago. Heuristics on the source, not an audit.

  • ✓README presentThe repository ships documentation.
  • ✓License declaredUsable under a stated license.
  • !Tests presentNo tests found. Behaviour changes may go unnoticed between versions.
  • !Dependencies pinnedNo lockfile. Installs can pull different code over time.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

1 check has not been run yet.

README

Box MCP Server (Remote)

Securely connect MCP-compatible agents to your Box content and Box AI—without moving data out of Box.

Endpoint: https://mcp.box.com

Overview

The remote Box MCP server lets AI agent platforms (e.g., Copilot Studio, Claude, Mistral Le Chat) connect to Box to securely query and use Box data and AI-powered tools, while keeping content protected. Authorization is handled via OAuth so users can grant controlled access from within the client they’re using.

Learn more in the remote Box MCP server guide

Looking for the self-hosted/local version? See box-community/mcp-server-box.

Capabilities

The remote Box MCP server provides tools across several areas, such as:

  • User info (e.g., identify the authenticated user)
  • File and folder operations (read content, list folders, search files/folders, etc.)
  • Box AI tools (Q&A across files, metadata extraction, etc.)

For the complete and most up-to-date set of supported tools, see the remote Box MCP server documentation.

Setup

To connect an MCP client to the remote Box MCP server, you’ll first configure an OAuth app in Box, then use its credentials in your client. The preferred path is to use the predefined Box MCP Server integration in the Admin Console, but in certain flows (e.g., the GitHub MCP registry), you may need to create your own OAuth app in the Developer Console instead.

1. Configure an OAuth app in Box

Choose one of the following options:

  • Admin Console flow (preferred): Enable or configure the Box MCP server from Admin Console → Integrations.
  • Developer Console flow: Create an OAuth app with the proper redirect URI and scopes.

For detailed instructions, see the remote Box MCP server guide.

2. Connect from your MCP client

Most clients or platforms let you add a remote MCP server by URL and will guide you through the OAuth flow. Here are some of the details you’ll typically need to provide:

  • Endpoint URL: https://mcp.box.com
  • Name: a name of your choice (e.g., box-remote-mcp)
  • Authorization: Bearer token (via OAuth 2.0)
  • Client ID and Client Secret: obtained from your app’s credentials (Admin Console for the predefined Box MCP Server integration, or Developer Console if you created your own OAuth app)
  • Redirect URI: provided by your client and must be added to your app configuration (via the Admin Console or Developer Console, depending on your flow)

See the remote Box MCP server guide for client-specific connection examples (Claude, Copilot Studio, Le Chat).

OAuth & Discovery

The remote Box MCP server is an OAuth‑protected resource backed by Box’s authorization server:

For implementation details, see the Box authentication guide.

Using tokens with the Box API

All Box API calls require a valid Access Token. Example:

curl https://api.box.com/2.0/users/me \
  -H "authorization: Bearer <ACCESS_TOKEN>"

Terms

Use of the Box MCP server and Box APIs is subject to the Box Terms of Service:
https://www.box.com/legal/termsofservice

Support & Docs

README fetched from the repository 6 days ago. The original is authoritative.

Questions

About box/mcp-server-box-remote

How do I install box/mcp-server-box-remote?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is box/mcp-server-box-remote safe to use with an AI agent?

Its trust score is 51 out of 100 (fair). It passes 2 of the 5 static security checks run so far; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is box/mcp-server-box-remote still maintained?

The last commit was a year ago. That's long enough that you should check whether the maintainer is responding to issues before depending on it.