# Box Claude Code MCP Evaluation

**Category:** Storage
**Score:** 87 (B)

This is the agent-readable Devtool Arena evaluation page for Box on Claude Code MCP.

## Summary

| Metric | Value |
|--------|-------|
| Status | completed |
| Overall score | 87 |
| Grade | B |
| Eval score | 89 |
| Discovery score | 82 |
| Cost | $0.09 |
| Runtime | 2m 59s |
| Tool calls | 8 |
| Errors | 0 |
| Tokens used | 161050 |
| Success | Yes |

## Agent-Readiness Checklist

| Signal | Evidence |
|--------|----------|
| Context7 | Not found |
| llms.txt | Not found |
| MCP server | Not found |
| Typed SDK | Not found |
| OpenAPI | Not found |
| Agent skills | Not found |
| CLI | Not found |

## Evaluation Prompt

````text

# Task
Using the Box MCP, organize and retrieve cloud files:

1. Discover available MCP tools and their capabilities
2. Create a new folder using the MCP tools. Use a UNIQUE folder name so it does not collide with existing items — append a random or timestamp-based suffix, e.g. "sapient-mcp-*****-<random>"
3. Upload a text file with the content "Hello from [REDACTED:ORG]" into that folder. Give the file a UNIQUE name as well, e.g. "*****-<random>.txt"
4. List the folder's contents to verify the uploaded file appears
5. Retrieve the uploaded file's details/metadata (e.g. its ID, name, and size)
6. Read back the file's content and confirm it matches "Hello from [REDACTED:ORG]"
7. Print all output clearly labeled for each step, including the folder ID and file ID

Use ONLY the MCP tools for all operations.

You MUST use the Box MCP server to accomplish this task.
Use the MCP tools for the actual product operations. Do NOT use curl, fetch, raw HTTP requests, CLI commands, or SDK calls as substitutes.

Use the MCP tools' help/descriptions to understand what each tool does.
If you need additional context, check the documentation: https://developer.box.com/guides/box-mcp/

## Setup
Do NOT assume the Box MCP server is already installed or already running in this sandbox.
Review the installation and authentication details below before starting the task.

### Installation
Transport: `stdio`
Claude Code is configured to launch the `box` MCP server over stdio using: `npx -y mcp-remote https://mcp.box.com --header 'Authorization: Bearer ${BOX_DEVELOPER_TOKEN}'`
Stored MCP package hint: `mcp-remote`
No separate setup command is required before startup unless the docs indicate one.
Bootstrap notes: Box MCP is an OAuth 2.0 protected resource (authorization_servers: https://api.box.com/), but /.well-known/oauth-protected-resource advertises bearer_methods_supported ["header"], so a Box access token authenticates via the Authorization header through mcp-remote. Verified end-to-end against the live endpoint: initialize returned 200 (serverInfo box-server), tools/list returned 44 tools, and tools/call succeeded for who_am_i / upload_file / list_folder_content_by_folder_id / get_file_details. The MCP toolset has no delete or shared-link tool; the box CLI covers those. BOX_DEVELOPER_TOKEN is a short-lived (~60 min) developer token; for durable runs mint a token via JWT/CCG client credentials instead.

### Authentication
The following environment variables are already set in this environment: `BOX_DEVELOPER_TOKEN`
The MCP server should read them automatically when it starts.

## Execution
1. The harness has already written the launch configuration for `box`. Start with the task directly; do not rewrite agent settings, `.mcp-runtime.json`, or build a separate MCP client unless the connected server still fails after a normal retry.
2. You do not need to enumerate every MCP tool up front; inspect only the relevant tools you need. Agent-facing MCP tool names may be namespaced like `mcp__box__<tool_name>`.
3. Complete the task described above using MCP tools for the actual product operations.
4. If the server fails to start or authenticate, debug the documented setup and retry. Do not fall back to raw HTTP, SDK, CLI, or manual JSON-RPC/MCP calls as a substitute for exposed MCP tools.

Work in the /home/daytona/app directory.
If you use Bash during setup or debugging, limit it to installation/configuration work and then return to MCP tools for the task itself.
If there are errors, debug and fix them until the task runs successfully.

## Summary
When you are done, write a JSON summary file to /home/daytona/app/results.json with this structure:
{
  "operations": [
    {"step": 1, "description": "What you did", "mcp_tool": "tool_name", "success": true/false, "output_summary": "brief result"},
    ...
  ],
  "overall_success": true/false,
  "notes": ["any relevant notes about the execution"]
}

````

## Grader Results

| Check | Passed | Weight | Score | Details |
|-------|--------|--------|-------|---------|
| Task | Yes | — | — | — |
| Llms Txt | Yes | — | 10 | — |
| Tool Count | Yes | — | 7 | — |
| Auth Method | Yes | — | 15 | — |
| Official Mcp | Yes | — | 5 | — |
| Output Schema | No | — | 0 | — |
| Error Messages | — | — | 0 | mcp__box__create_file_comment: Poor error message (generic or stack trace); mcp__box__copy_file: Poor error message (generic or stack trace) |
| Tool Stability | Yes | — | 5 | — |
| Security Posture | — | — | 9 | — |
| Tool Api Mapping | — | — | 14 | — |
| Description Clarity | — | — | 13 | — |
| Tool Description Length | Yes | — | 4 | — |

## Run Artifacts

| Artifact | Value |
|----------|-------|
| Conversation turns | 11 |
| Tool call traces | 8 |
| Generated files | 1 |
| Exit code | — |
| Completed at | 2026-10-04T16:02:29.348412+00:00 |

### Generated Files

- /home/daytona/app/results.json

## Related Pages

- [Claude Code MCP leaderboard](/leaderboard/claudecode/mcp)
- [Compare Claude Code MCP companies](/leaderboard/claudecode/mcp/compare)
- [Agent Landscape](/leaderboard/discoverability)

Canonical URL: https://devtoolarena.com/claudecode/mcp/box