Box Content Official Remote MCP Server
Box's hosted MCP (mcp.box.com) exposes the enterprise content cloud โ file search, folder listings, text extraction and Box AI Q&A โ to agents over OAuth 2.1.
ไธญๆ็ฎไป
Box ๅฎๆน่ฟ็จ MCP ๆๅกๅจใAI ไปฃ็ๅฏ้่ฟ OAuth ๆ็ดขๆไปถใ่ฏปๅๆๆกฃๅ ๅฎน๏ผๅนถไฝฟ็จ Box AI ๅฏนๅ ๅฎนๅบๆ้ฎใ
Maintainer of Box Content? Claim or update this listing โ
Or add to ~/.cursor/mcp.json:
{
"mcpServers": {
"box": {
"url": "https://mcp.box.com"
}
}
}claude mcp add --transport http box https://mcp.box.com
Or add to .vscode/mcp.json:
{
"servers": {
"box": {
"type": "http",
"url": "https://mcp.box.com"
}
}
}- Open Settings โ Connectors (Integrations) โ Add Custom Connector.
- Paste the endpoint URL:
https://mcp.box.com - Complete the browser OAuth 2.1 login flow when prompted.
Bridge the remote endpoint into stdio with mcp-remote in claude_desktop_config.json:
{
"mcpServers": {
"box": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.box.com"
]
}
}
}Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"box": {
"serverUrl": "https://mcp.box.com"
}
}
}Add to ~/.kiro/settings/mcp.json (or .kiro/settings/mcp.json in your workspace), then reopen Kiro's Agent panel to pick up the server:
{
"mcpServers": {
"box": {
"url": "https://mcp.box.com"
}
}
}Add to ~/.codex/config.toml โ Codex reads remote HTTP servers from [mcp_servers.*] tables:
[mcp_servers.box] url = "https://mcp.box.com"
Add to cline_mcp_settings.json (Cline โ MCP Servers โ Configure), or paste it via Cline's MCP marketplace file:
{
"mcpServers": {
"box": {
"type": "streamableHttp",
"url": "https://mcp.box.com"
}
}
}Add to ~/.gemini/settings.json under mcpServers โ httpUrl for Streamable HTTP, url for legacy SSE:
{
"mcpServers": {
"box": {
"httpUrl": "https://mcp.box.com"
}
}
}๐งฐ Box Content MCP Tools & Schema (5)
| Tool | Safety | Description | Parameters |
|---|---|---|---|
| search_files ~74 tok | ๐ข Read | Full-text search across files and folders. | query*: stringfileTypes: array |
| list_folder_items ~49 tok | ๐ข Read | List items in a folder. | folderId*: string |
| get_file_content ~52 tok | ๐ข Read | Download extracted text content of a file. | fileId*: string |
| box_ai_ask ~75 tok | ๐ข Read | Ask Box AI a question about one or more files. | question*: stringfileIds*: array |
| box_ai_extract ~77 tok | ๐ข Read | Extract structured fields from a file with Box AI. | fileId*: stringfields*: array |
๐ก๏ธ Security, Quality & Context Token Audit
Every tool definition (name + description + input schema) is injected into your LLMโs context on every request โ Estimate per-call LLM token cost โ
- No prompt-injection or hidden-character anomalies detected in tool descriptions
- Streamable HTTP primary endpoint (current 2025-03-26 transport)
- OAuth 2.1 with PKCE S256 enforced
- Official first-party endpoint operated by the vendor
- Manually verified by RemoteMCP.net
๐ OAuth 2.1 & Security
- Auth type
- OAuth 2.1
- Dynamic Client Registration
- โ Supported
- PKCE S256
- โ Supported
- Scopes
root_readonlyai.readwrite- Protected resource metadata
- https://mcp.box.com/.well-known/oauth-protected-resource (expected location)
๐งฉ Recommended Agent Skills
๐ Box Content MCP Endpoint Overview & Security Guide
Box Content MCP โ Remote MCP Server
Box's remote MCP turns an enterprise content lake into an agent data source โ full-text file search, folder traversal, extracted text reads, plus Box AI endpoints that can answer questions across documents or extract structured fields.
Official Box Content MCP Endpoint & Transport Architecture
- Endpoint URL:
https://mcp.box.com - Transport: Streamable HTTP
Streamable HTTP is the current MCP transport (2025-03-26 spec): a single URL accepts JSON-RPC POSTs and may stream responses over SSE, so one endpoint serves both simple and streaming workloads. Box Content MCP does not publish a separate legacy SSE endpoint, so your client must speak Streamable HTTP.
Authentication, Scopes & Permission Boundaries
Box Content MCP uses OAuth 2.1 โ the first request returns a 401 Unauthorized challenge with a WWW-Authenticate header pointing at the authorization metadata. Compliant clients (Cursor, Claude, VS Code, ChatGPT) handle the whole flow โ PKCE and Dynamic Client Registration, so no manual client setup is needed โ and simply open a browser consent screen.
All 5 cataloged tools are read-only โ Box Content MCP cannot mutate your account data, which makes it safe to connect broadly.
Common Troubleshooting & Connection Tips
- 401 Unauthorized on connect โ that's expected; the server is OAuth-protected. Let your client complete the browser consent flow, or inspect the endpoint in our OAuth debugger to see the exact
WWW-Authenticatechallenge. - "Session expired" / stale
Mcp-Session-Idโ just re-sendinitialize; stateless clients can ignore session headers entirely. - AI features require a Box plan with Box AI enabled.
- Folder/file permissions mirror your Box account โ the agent sees what you see.
๐ How to Connect
- Copy the Box Content MCP endpoint URLThe remote endpoint is https://mcp.box.com.
- Add it to your MCP clientClaude Code:
claude mcp add --transport http box https://mcp.box.com. Cursor: add"box": { "url": "https://mcp.box.com" }undermcpServersin ~/.cursor/mcp.json. Other clients work similarly. - Complete the OAuth consentOn first connection your client opens a Box consent screen in the browser. Approve it to grant access; the token is stored by the client and refreshed automatically.
- Verify with the online inspectorPaste https://mcp.box.com into remotemcp.net/inspector, run initialize and tools/list, and confirm Box Content MCP's 5 tools respond.
โ FAQ
What is the Box Content MCP remote MCP endpoint?
The primary endpoint is https://mcp.box.com. It is an official first-party server operated by Box, speaking the Streamable HTTP transport.
How do I authenticate with Box Content MCP?
Box Content MCP uses OAuth 2.1. When your client first connects it receives a 401 challenge, discovers the authorization server via RFC 9728 metadata, and opens a browser consent screen. Dynamic Client Registration is supported, so compliant clients register themselves automatically.
I'm getting a 401 Unauthorized from Box Content MCP โ what's wrong?
A 401 means your client hasn't completed (or has lost) the OAuth authorization. Remove and re-add the server in your client to restart the consent flow, and check that your browser session can reach the provider's login page. If the 401 arrives without a WWW-Authenticate header, run it through our OAuth debugger to see what's missing.
Which MCP clients work with Box Content MCP?
Any client that supports remote MCP servers: Cursor, Claude Code (`claude mcp add --transport http box https://mcp.box.com`), VS Code Copilot, ChatGPT connectors, Windsurf, Kiro (`~/.kiro/settings/mcp.json`), and Claude Desktop via the `mcp-remote` bridge.
What tools does Box Content MCP expose?
5 tools are cataloged in this directory โ including `search_files`, `list_folder_items`, `get_file_content` and more. Use our online inspector to fetch the live tool list straight from the endpoint.
๐ Connect Guides
๐ Embed Status Badge in README
Related Servers
Notion's official hosted MCP server. Agents can search your workspace, read and create pages, and query databases over Streamable HTTP or SSE.
Linear's official remote MCP server. Agents can search, create and update issues and query your team's workflow over Streamable HTTP or SSE.
Slack's hosted remote MCP server. Slack's official remote MCP lets agents search channels, read conversation history, post messages and manage canvases inside your Slack workspace. It is protected by OAuth 2.1; compliant clients complete a browser consent flow with PKCE.
Todoist's official remote MCP server. Agents can add, complete and search tasks, manage projects and sections over OAuth 2.1.