MCP Connector

Integrate AI with Box Content

A discontinued community MCP server for Box content management - file, folder, search, metadata, and collaboration tools; migrate to Box's official server.

Works with box

Maintainer of this project? Claim this page to edit the listing.


91
Spark score
out of 100
Updated 2 months ago
Version 0.7.0
Models
universal

Add to Favorites

Why it matters

Empower AI agents to securely access and interact with your enterprise content stored in Box. This connector provides AI-powered file operations, search, and collaboration features.

Outcomes

What it gets done

01

Perform AI-powered file and hub queries.

02

Execute file operations including read, upload, and download.

03

Manage folder operations such as listing, creation, and deletion.

04

Facilitate search for files and folders within Box.

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/vb-box | bash

Capabilities

Tools your agent gets

box_tools_ai

AI-powered file and hub queries

box_tools_files

File operations including read, upload, and download

box_tools_folders

Folder operations including list, create, delete, and update

box_tools_search

Search files and folders

box_tools_collaboration

Manage file and folder collaborations

box_tools_shared_links

Shared link management

box_tools_tasks

Task and task assignment management

box_tools_comments

Comment operations

+3 tools

Overview

Box MCP

A community-maintained MCP server wrapping the Box API into 13 tool modules covering files, folders, search, metadata, collaboration, groups, users, tasks, shared links, and document generation. It supports stdio and HTTP/SSE transports with OAuth2.0 or token authentication. Do not adopt this for new integrations - it is explicitly discontinued and Box now offers an official hosted MCP server. Relevant only to existing users or those studying/forking the reference implementation.

What it does

A community-built MCP server that exposes the Box content-management API as a set of tool modules an MCP client can call: box_tools_ai for AI-powered file and hub queries, box_tools_collaboration for managing file and folder collaborations, box_tools_docgen for document generation and template management, box_tools_files for reading, uploading, and downloading files, box_tools_folders for listing, creating, deleting, and updating folders, box_tools_generic for general Box API utilities, box_tools_groups for group management, box_tools_metadata for metadata templates and instances, box_tools_search for finding files and folders, box_tools_shared_links for shared-link management, box_tools_tasks for task and task-assignment management, box_tools_users for user management, and box_tools_web_link for web-link creation - 13 tool categories in total.

When to use - and when NOT to

Do NOT adopt this for anything new: the repository carries an explicit warning that it is discontinued and no longer maintained, and Box now provides an officially supported hosted MCP server with the best experience and full functionality - migrate there instead. This project remains relevant mainly to teams already running it who need to understand its tool surface, or developers who want to study or fork the code before it's fully retired.

Capabilities

The 13 tool modules above cover the bulk of day-to-day Box operations: content search and retrieval, file/folder CRUD, collaboration and sharing, group and user administration, metadata template management, document generation, and task assignment - each documented in its own docs/box_tools_*.md file.

How to install

git clone https://github.com/box-community/mcp-server-box.git
cd mcp-server-box
uv sync
uv run src/mcp_server_box.py

Authentication is set via environment variables (in a .env file or system environment): BOX_CLIENT_ID, BOX_CLIENT_SECRET, and BOX_REDIRECT_URL for OAuth2.0 with a Box App, plus BOX_MCP_SERVER_AUTH_TOKEN to authenticate the MCP client to the server itself when using --mcp-auth-type=token. The server supports CLI flags for --transport (stdio, sse, http), --host, --port, --mcp-auth-type (oauth, token, none), and --box-auth-type (oauth, ccg, jwt, mcp_client). For Claude Desktop it can run in STDIO mode via claude_desktop_config.json pointing uv at the server's directory, or in HTTP mode by adding a custom connector under Claude Settings > Connectors with the server URL and optional client id/secret, then completing the OAuth flow. Recommended setup uses uv (installable via Homebrew on macOS, WinGet on Windows, or the astral.sh install script on macOS/Linux/PowerShell) for virtual environment and dependency management, though uv run src/mcp_server_box.py --help prints the full CLI reference on demand.

Who it's for

Teams already integrated with Box who adopted this community server before Box's own hosted MCP offering existed, and developers who want to study or fork a reference implementation of the Box API as MCP tools - not recommended as a starting point for new integrations.

Source README

Box MCP Server

Quick Start

Clone the repository:

git clone https://github.com/box-community/mcp-server-box.git
cd mcp-server-box

Optional but recommended uv installation for virtual environment and dependency management:

Homebrew (macOS)
brew install uv
WinGet (Windows)
winget install --id=astral-sh.uv  -e
On macOS and Linux
curl -LsSf https://astral.sh/uv/install.sh | sh
On Windows
powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"

Set up the virtual environment and install dependencies:

uv sync

Set environment variables:

Set the following environment variables for Box authentication in a .env file or your system environment.

For comprehensive authentication configuration options, see the Authentication Guide.

Using OAuth2.0 with a Box App
BOX_CLIENT_ID = YOUR_CLIENT_ID
BOX_CLIENT_SECRET = YOUR_CLIENT_SECRET
BOX_REDIRECT_URL = http://localhost:8000/callback

# MCP Server Authentication (for HTTP transports)
BOX_MCP_SERVER_AUTH_TOKEN = YOUR_BOX_MCP_SERVER_AUTH_TOKEN
OAUTH_PROTECTED_RESOURCES_CONFIG_FILE = .oauth-protected-resource.json

Note:

  • The BOX_MCP_SERVER_AUTH_TOKEN is used to authenticate the MCP client to the MCP server when using --mcp-auth-type=token (independent of Box authentication)

Run the MCP server in STDIO mode:

uv run src/mcp_server_box.py

Box Community MCP Server Tools

Below is a summary of the available tools:

Tools available Description
box_tools_ai AI-powered file and hub queries
box_tools_collaboration Manage file/folder collaborations
box_tools_docgen Document generation and template management
box_tools_files File operations (read, upload, download)
box_tools_folders Folder operations (list, create, delete, update)
box_tools_generic Generic Box API utilities
box_tools_groups Group management and queries
box_tools_metadata Metadata template and instance management
box_tools_search Search files and folders
box_tools_shared_links Shared link management for files/folders/web-links
box_tools_tasks Task and task assignment management
box_tools_users User management and queries
box_tools_web_link Web link creation and management

Box Community MCP Server Operations Details

Command line interface parameters

To run the MCP server with specific configurations, you can use the following command line parameters:

uv run src/mcp_server_box.py --help
usage: mcp_server_box.py [-h] [--transport {stdio,sse,http}] [--host HOST] [--port PORT] [--mcp-auth-type {oauth,token,none}] [--box-auth-type {oauth,ccg,jwt,mcp_client}]

Box Community MCP Server

options:
  -h, --help            show this help message and exit
  --transport {stdio,sse,http}
                        Transport type (default: stdio)
  --host HOST           Host for SSE/HTTP transport (default: localhost)
  --port PORT           Port for SSE/HTTP transport (default: 8005)
  --mcp-auth-type {oauth,token,none}
                        Authentication type for MCP server (default: token)
  --box-auth-type {oauth,ccg,jwt,mcp_client}
                        Authentication type for Box API (default: oauth)

For detailed information about authentication types, configurations, and use cases, see the Authentication Guide.

Claude Desktop Configuration

STDIO mode

Edit your claude_desktop_config.json:

code ~/Library/Application\ Support/Claude/claude_desktop_config.json

Add the configuration:

{
    "mcpServers": {
        "mcp-server-box": {
            "command": "uv",
            "args": [
                "--directory",
                "/path/to/mcp-server-box",
                "run",
                "src/mcp_server_box.py"
            ]
        }
    }
}

Restart Claude if it is running.

HTTP Mode

Assuming your MCP server is running on https://mcp.myserver.com/mcp

  1. Go to Claude -> Settings -> Connectors
  2. Select Add custom connector
  3. Configurations:
    1. Give it a name
    2. Enter the URL e.g. https://mcp.myserver.com/mcp
    3. Optionally enter the client id and client secret
  4. Click add
  5. Click connect. The OAuth flow should start. Complete the flow
  6. Back in Claude, click Configure. You should see all the tools available.

FAQ

Common questions

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.