Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Box to Claude Code

Let Claude upload, organize, and share files in Box. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Box to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Box, you add a Box MCP server: a small hosted service that exposes Box's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Box account. No API keys pasted into config files.

claude mcp add --transport http box https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Box once connected?

Full read-write Box access lets Claude upload and update files, create and reorganize folders, generate or revoke shared links, add comments, and apply metadata, all once you approve. The filing, tidying, and sharing that used to mean manual clicks happen where the content already lives.

  • Upload a new file or save a new version into the right folder
  • Create and reorganize folders, then move or rename files into them
  • Generate or revoke a shared link with the access level you choose
  • Add a comment to a file to leave context for collaborators
  • Apply or update metadata so content stays searchable and tagged
  • Delete an outdated file after you confirm the action

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Box access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Box API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Box changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Box connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Box connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Box account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Box's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Box?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Box account it signs in with. Revoking access is one click in Box.

More on the Box connector

Box connector for claude.aiGoogle Drive + Claude CodeDropbox + Claude CodeSharePoint + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us