Box MCP Server (Remote)

Add to your client

Copy the config for your MCP client and paste it into its config file.

{
  "mcpServers": {
    "box-mcp-server-remote": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.box.com",
        "--header",
        "Authorization: Bearer <oauth-token>"
      ]
    }
  }
}

Before you start

• A Box account (free, Business, or Enterprise) with access to the content you want the agent to use
• A Box OAuth 2.0 app configured in the Box Developer Console (or Admin Console) with a Client ID, Client Secret, and redirect URI — used to authorize the MCP connection
• An MCP client that supports remote MCP servers with OAuth (e.g. Claude, Copilot Studio, Mistral Le Chat), or the mcp-remote proxy (Node.js 18+) for clients without native remote/OAuth support

About Box MCP Server (Remote)

Tools & capabilities (12)

When to use it

• Use it when you want an AI agent to answer questions grounded in your actual Box documents (contracts, reports, policies) instead of uploaded copies
• Use it when extracting structured fields (invoice totals, dates, parties) from documents into metadata templates at scale
• Use it when an agent needs to search, organize, move, or share Box content as part of a workflow
• Use it when enterprise governance requires content to stay inside Box's security boundary rather than being copied to a third party
• Use it when building agents in Claude, Copilot Studio, or Mistral Le Chat that need permission-aware access to company content
• Use it when generating documents from templates via Box Doc Gen or querying across a curated Box Hub

Quick setup

1. 1Create or identify an OAuth 2.0 app in the Box Developer Console and note the Client ID, Client Secret, and redirect URI
2. 2In your MCP client, add a remote MCP server pointing at https://mcp.box.com (or use the platform's prebuilt Box connector)
3. 3For clients without native remote/OAuth support, proxy with `npx mcp-remote https://mcp.box.com`
4. 4Trigger the OAuth flow — a Box login/consent screen opens in the browser — and approve access
5. 5Restart the client and confirm Box tools (e.g. who_am_i) are listed
6. 6Call who_am_i to verify the connection runs as the expected Box user

Box MCP Server (Remote) FAQ