Box logo

Box

Browse, search, inspect, and read text files from a connected Box account through MCP.

Install Box

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "box": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-box"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

Box MCP server connects AI clients to Box enterprise cloud storage through tools for folder browsing, file search, metadata inspection, text retrieval, and account details. It can run locally as a stdio MCP server or remotely through the Pipeworx gateway. Use it when an agent needs to locate Box content, inspect file properties, read supported text files, or report storage usage. The integration is unofficial and is not affiliated with Box.

Use cases

  • Browse folders and identify Box files
  • Search Box content by keyword
  • Inspect metadata for a selected document
  • Read supported text files into an agent workflow
  • Report the connected user's Box storage usage

Key features

  • Folder and root-directory listing
  • File and folder search by name or content
  • Detailed file metadata retrieval
  • Text extraction with truncation reporting
  • Connected-user and storage information

Tools5

What Box lets your agent do. Expand a tool for its parameters.

Verified live~589 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

5/5 checks healthy over the last 38d

What it can do

From the 5 tools this server returned when we ran it.

Makes network requests · 3Read-only tools · 5
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age135 days
Maintainers1

Observed 2026-10-17 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 2d ago via OSV.dev · @pipeworx/mcp-box (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads409Package downloads in the last 30 days.
Last commit4d agoMost recent push to the default branch.
Tools exposed5Callable tools this server registers over MCP.
Directory activity4 viewsConfig copies, upvotes, and views on AllMCPs.

How Box works

What Box MCP server does

Box MCP server gives an MCP-compatible agent read access to a connected Box account. Its tools cover five common tasks: browsing folders, searching by name or content, retrieving file metadata, reading text files, and checking the connected user's profile and storage usage.

The integration is designed for discovery and inspection rather than file management. It does not expose tools for uploading, editing, moving, deleting, or sharing files.

How it works

The package can be reached in two ways. A remote connection uses the Pipeworx gateway at https://gateway.pipeworx.io/box/mcp. That endpoint lists the Box-specific tools together with shared Pipeworx gateway tools. The shared tools can route questions across the wider Pipeworx catalog, while the Box tools operate on the connected Box account.

A local installation runs as a stdio MCP process and exposes only the Box pack's tools. It communicates through standard input and output and can be started with npx -y @pipeworx/mcp-box.

The gateway also supports direct HTTP tool calls. These require a Pipeworx key and use bearer-token authorization. The remote service must have a connected Box account before its tools can access data.

Setup and configuration

For an MCP client that supports remote URLs, add the gateway endpoint:

config.json
{
  "mcpServers": {
    "box": {
      "url": "https://gateway.pipeworx.io/box/mcp"
    }
  }
}

For local stdio use, configure the package as follows:

config.json
{
  "mcpServers": {
    "box": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-box"]
    }
  }
}

The gateway route requires signing in to Pipeworx, connecting Box, and using a Pipeworx key. The local process does not require a Pipeworx gateway account.

Tools and capabilities

  • box_list_folder lists items in a specified folder or the Box root when no folder ID is supplied. Results include item IDs, types, names, byte sizes, and modification times.
  • box_search searches file and folder names and content. Results can be limited to files or folders and include basic identifying and timestamp fields.
  • box_get_file returns metadata for a file, including its name, size, description, creation and modification times, parent folder name, shared-link URL, and extension.
  • box_get_file_text retrieves text from a file by ID. It is intended for plain text, Markdown, CSV, and similar formats.
  • box_get_user returns the signed-in user's ID, name, email, total storage allocation, and used storage.

Limitations and notes

box_get_file_text is not suitable for binary formats such as Office documents, PDFs, or images; those may produce unreadable bytes. Returned text is limited to approximately 100,000 characters and indicates when truncation occurs.

The remote pack endpoint includes shared Pipeworx meta-tools in addition to the Box tools. The local stdio mode exposes only the Box pack. The gateway and local modes use the same Box tool set, but the gateway adds cross-catalog routing through shared tools.

This is an independent, unofficial Box integration. It is not published, endorsed, or affiliated with Box. The package is licensed under MIT.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Box

Box is an MCP server that connects AI clients to Box enterprise cloud storage. Its main tools list folders, search files and folders, retrieve file metadata, read supported text files, and return the connected user's profile and storage usage. It runs locally over stdio or remotely through the Pipeworx gateway.

Install it as a local stdio server with `npx -y @pipeworx/mcp-box`, then add that command and package argument to your MCP client's server configuration. You can instead configure the Pipeworx remote endpoint at `https://gateway.pipeworx.io/box/mcp`.

Yes, Box works with Cursor through the remote MCP URL or the local stdio configuration. The remote setup uses the Pipeworx gateway and requires a connected Box account; the local setup runs the package with `npx`.

No, its text retrieval tool is intended for plain-text, Markdown, CSV, and similar text formats. PDF, Office, and image files are binary and may return unreadable bytes. Retrieved content is capped at approximately 100,000 characters.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewBox AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/box?style=directory)](https://allmcps.com/mcp/box)
HTML Embed
<a href="https://allmcps.com/mcp/box"><img src="https://allmcps.com/api/badge/box?style=directory" alt="Box on AllMCPs" /></a>