# hmk/box-mcp-server [Health: Active]

**Category:** 📂 File Systems  
**Repository:** https://github.com/hmk/box-mcp-server  
**GitHub Stars:** 11  
**npm Downloads (last month):** 270  
**Views:** 5  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/hmk-box-mcp-server

## Description
Box integration for listing, reading and searching files

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "box-mcp-server": {
    "command": "npx",
    "args": ["box-mcp-server"],
    "env": {
      "BOX_USER_ID": "",
      "BOX_JWT_BASE64": "",
      "BOX_JWT_CONFIG_PATH": "",
      "BOX_JWT": "",
      "BOX_DEV_TOKEN": ""
    }
  }
}
```

**Requires environment variables:** `BOX_USER_ID`, `BOX_JWT_BASE64`, `BOX_JWT_CONFIG_PATH`, `BOX_JWT`, `BOX_DEV_TOKEN` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What hmk/box-mcp-server does

hmk/box-mcp-server MCP server gives an MCP client access to selected Box file operations. Its documented capabilities are searching for files and reading files. The repository specifically marks PDF and Word support as available; support for other file formats is not indicated.

This is intended for workflows where an AI agent needs to find documents in a Box account and inspect their contents. It does not document file creation, updates, deletion, folder management, or general Box administration, so those operations should not be assumed.

## How it works

The package runs as an MCP process and can be launched with `npx box-mcp-server`. An MCP client starts the process and supplies authentication values through its environment. The server then uses those credentials to connect to Box and handle file search or read requests.

Authentication can use a Box developer token or JWT authorization. A developer token is described as the simplest option, but it expires after 60 minutes. JWT authorization is recommended for a persistent connection and requires configuration in the Box Developer Console, including application access settings and the ability to make API calls with the `as-user` header.

## Setup and configuration

To run hmk/box-mcp-server MCP server, configure the required Box credentials in the client’s MCP server definition or environment. JWT-based setups require `BOX_USER_ID` plus one of `BOX_JWT_BASE64`, `BOX_JWT_CONFIG_PATH`, or `BOX_JWT`.

A Claude Desktop configuration starts the package with the `npx` command and passes credentials under `env`. For JWT configuration, a local Box JWT configuration file can be Base64-encoded and assigned to `BOX_JWT_BASE64`. Box application setup requires a paid enterprise account or a free developer account, followed by creation and authorization of an application in the Box Developer Console.

For local development, the repository documents Node.js, npm, git, and dotenv as prerequisites. The development flow includes installing dependencies, running the watch script, and launching the built `dist/index.js` through the MCP Inspector.

## Tools and capabilities

The documented operations are:

- Search for files in Box.
- Read files stored in Box.
- Process PDF documents.
- Process Word documents.

Confirm those details in the implementation before building a workflow that depends on them.

## Limitations and notes

Developer-token authentication is temporary and lasts 60 minutes, making it less suitable for long-lived connections. JWT authentication has more setup requirements, including Box application authorization and public/private key configuration.

PDF and Word files are explicitly marked as supported. Other file types are marked unsupported or unspecified in the capability checklist. Client configuration examples are provided for Claude Desktop; other MCP clients may require their own configuration format.

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