Skip to content
Box MCP Server

Box MCP Server

by Box
Added to Onei
Repository Docs
Files & Storage

Summary

Box's official remote MCP server at mcp.box.com: governed AI-agent access to enterprise files, folders and Box AI within existing permissions.

Features

  • Hosted remote endpoint at https://mcp.box.com, no self-hosting required
  • Search, folder operations, Box AI and document knowledge tools
  • Operates strictly within the permissions already configured in Box
  • Admin-gated: requires Admin Console enablement and OAuth Integration Credentials
  • Documented support for Claude Code, Cursor, GitHub Copilot, OpenAI AgentKit and more

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it.
  3. Restart the agent — the "Box MCP Server" tools will be available.
{
  "mcpServers": {
    "box-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.box.com"
      ]
    }
  }
}

Description

The official Box Model Context Protocol server, a hosted endpoint at https://mcp.box.com that gives AI agents governed access to content stored in Box. You connect a client or agent platform to that URL — for the standard integration you do not run Box's MCP server yourself, and the older self-hosted build is deprecated.

What it exposes

Search across a Box instance, folder operations, Box AI capabilities and document knowledge — enough for an agent to find relevant files, extract insights from several documents at once, and apply metadata without a custom integration being written first. The complete tool index is published as a machine-readable document at https://developer.box.com/llms.txt.

Permissions model

This is the part that makes Box MCP viable in a regulated organisation: the server operates strictly within the permissions already configured in Box. An agent sees what the authenticated user sees, and nothing else, so existing governance keeps applying rather than being reimplemented at the agent layer.

Setup

An administrator must first enable MCP in the Box Admin Console and create Integration Credentials — an OAuth client ID and secret, a redirect URI, and scopes such as Content Actions. Only then can client applications connect. That admin gate is worth planning for: an individual developer cannot switch this on alone.

Client support

Box documents connections from the Anthropic Messages API, Claude Code, Cursor, GitHub Copilot, Groq, LangSmith Agent Builder, Microsoft Foundry Tools and OpenAI AgentKit, plus end-user platforms including ChatGPT, Claude, Copilot Studio and Figma.

Alternatives

MCP: Docusign MCP Server

by Docusign

Featured

Docusign's official hosted MCP server: query, send and track agreements from any MCP client using your own account permissions.

Productivity

MCP: Ramp

by Ramp

Ramp's official remote MCP server for corporate spend — read transactions, bills and reimbursements, and with the right role edit, approve and lock cards.

Payments & Commerce

MCP: WorkOS

by WorkOS

WorkOS's official remote MCP server — run your WorkOS dashboard from an agent: organizations, users, SSO connections, Directory Sync, AuthKit branding and audit log streams.

Developer Tools

MCP: Sourcegraph

by Sourcegraph

Sourcegraph's MCP server — cross-repository keyword and semantic code search, go-to-definition, find-references, commit and diff search, and Deep Search, served from your own instance.

Developer Tools
Browse all MCP servers →