hmk/box-mcp-server
A Box model context protocol server to search, read and access files
Platform-specific configuration:
{
"mcpServers": {
"box-mcp-server": {
"command": "npx",
"args": [
"-y",
"box-mcp-server"
]
}
}
}Add the config above to .claude/settings.json under the mcpServers key.
You will need:
BOX_USER_ID and one of the following:
BOX_JWT_BASE64 (recommended)BOX_JWT_CONFIG_PATHBOX_JWTUsing a JWT Config allows persistent connection to Box.
You will need a paid Box enterprise account, or you can sign up for a free developer account (make sure you are signed out of Box before clicking that link).
Visit the Box Developer Console and create a new application. Make sure the authorization type is JSON Web Token.
Go to Configuration > Add and Manage Public Keys and Generate a Public/Private Keypair. If you have not already, Box prompt you to set up 2 factor authentication and Authorize the application as an administrator in your box account. You will need to:
App + Enterprise Access, andmake API calls using the as-user header optionvia the Box Application's Configuration page. Make sure to reauthorize the application if you are modifying these settings.
To encode your JWT in Base64, you can use the following command in your terminal:
cat /path/to/your/box-jwt-config.json | base64Replace /path/to/your/box-jwt-config.json with the actual path to your JWT configuration file. This will output the Base64 encoded JWT which you can then use in your environment variables.
{
"mcpServers": {
"box": {
"command": "npx",
"args": ["box-mcp-server"],
"env": {
"BOX_JWT_BASE64": "YOUR_BASE64_ENCODED_JWT",
"BOX_USER_ID": "123456"
}
}
}
}Using a developer token is the easiest way to integrate with Box, but will
Loading reviews...