Claude Box connectorWhat Claude can do in your Box account.
The Claude Box connector exposes 20 tools. 17 of them look through your folders and files without touching them, 3 add something to your Box. Below: what Claude finds, what it can upload, what a Box admin controls, and where the tool list stops.
Verified Trustpilot reviews · AI, automation & growth agency
What the Claude Box connector changes day to day
You stop clicking through folder trees to find one contract or one slide deck. You ask Claude in plain words, and it goes into Box itself: it searches by keyword or by metadata, opens the file, and can put a question to Box AI about one document, several, or a whole hub. The answer lands in the conversation, with citations when Box has them.
Get the answer, not the file. Someone asks what the termination clause says in a supplier agreement: Claude locates it with search_files_keyword, then asks ai_qa_single_file and reports what Box AI found, with the passage cited.
Turn a pile of PDFs into a table. With ai_extract_structured, Claude pulls the same fields out of many invoices or forms, following definitions you give it, and lays the values out for you to check.
File what you just produced. A summary written with Claude can go straight into the right folder through upload_file, and create_folder sets up the place for it first.
What it will not do matters as much. Claude never sees more than the person who connected: Box says the connection does not impersonate other users or search the whole company unless that identity already can. The public tool list shows no way to delete, move, share or comment on a file. Replacing a file with a new version is listed, yet Box ships that tool switched off until an admin turns it on. And nothing runs on its own: no tool fires when a file lands in a folder. That kind of hands-off flow belongs to an automation tool, a different job, covered by the Box n8n integration and the Box Make integration.
Five words to know before connecting Box
The Claude vocabulary this page relies on, in one minute.
- Connector
- A link you set up once between Claude and an account you already have, so Claude can work in that account while it answers you.
- Tool
- One named action the connector lets Claude take in Box. Claude picks the ones it needs on its own, and the directory sheet lists every name.
- Authorization
- The Box sign-in screen where you hand Claude the access it will use. Given once per person, and it can be withdrawn the same way.
- Approval
- The confirmation Claude waits for in the conversation before it goes ahead with something that alters your account.
- MCP
- The shared standard connectors are built on: the plumbing that lets an assistant such as Claude talk to an outside service like Box.
Connect Box to Claude in three steps
- 01
Find Box in the list
Open Claude's settings, go to Customize, then Connectors, and look for Box. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it for the organization before each member can sign in.
- 02
Sign in to Box
Click Connect on the Box row. A Box window opens and you log in there with your usual account. If the link breaks later, Disconnect and connect again; access can also be withdrawn from Box itself.
- 03
Check what Box asks for
Read the authorization screen before you accept. It belongs to Box, not to Claude, and it sets what the access covers. It may list broader rights than Claude uses day to day; the per-action approval stays the default rule.
The 20 Box tools, split by what they do
Box gives Claude 20 tools: 17 that read your account, 3 that change something in it.
Two groups: what Claude reads, and what it adds to your Box. Tool names stay exactly as Claude shows them.
- 17 read
- 3 write
What Claude reads (17)
17 toolsSearching, opening and questioning content. Your Box stays as it was.
who_am_i
Tells Claude which Box user it is working as, with that account's details. It is the quickest way to confirm the connection landed on the right login.
search_folders_by_name
Finds folders whose name matches a keyword, so Claude can locate a project space when you only remember part of what it is called. You get the matching folders back and can pick one.
list_folder_content_by_folder_id
Returns what sits inside a folder, page by page: files, subfolders and web links. From that list, Claude can open a file or go one level down into a subfolder the same way.
search_files_keyword
Looks for files by keyword, with optional filters on metadata and file extension. Claude gets back the matches and can narrow them down in the next turn.
search_files_metadata
Runs a structured query against the metadata attached to files, with conditions and an optional folder scope. Useful when your team tags documents with fields such as a client or a status.
ai_qa_single_file
Puts a question to Box AI about a single document and brings back the answer, with citations when they exist. Only the first 1 MB of the file's text is read.
ai_qa_multi_file
Same idea spread over several documents at once: Box AI answers from all of them together and cites its sources when it can, so you see which file each point comes from.
ai_qa_hub
Questions the full content of a Box hub, the curated collection your team built around a topic, and returns an answer grounded in what that hub holds, with citations where Box has them.
ai_extract_freeform
Pulls information out of files from a plain-language request, with no template needed. Box works from up to 1 MB of each file's text. When the fields are fixed in advance, the structured extraction tool is the better fit.
ai_extract_structured
Extracts key-value data using field definitions you supply, through Box AI's enhanced extraction agent. The result comes back as a tidy set of fields per file.
get_file_content
Returns the content of a file stored in Box, so Claude can quote it, summarize it or compare it with something else in the chat.
list_tasks
Shows the tasks attached to a file, with their status, message and due dates. Box task assignments become visible without leaving the chat.
list_hubs
Returns every hub your account can reach, with enough to tell them apart. It is the starting point before Claude looks inside one hub or puts a question to it.
get_hub_details
Fetches detailed information about one hub, so Claude can tell you what that collection is meant for before digging into the documents it gathers.
get_hub_items
Lists the files and folders tied to a hub, which lets Claude point you at the right document inside a curated collection instead of a whole folder tree.
get_file_details
Gives the full record of a file: its metadata, its permissions and its version details. Handy to know who can see something and how recent the copy in front of you really is.
get_folder_details
Returns the record of a folder, including its metadata, its permissions and the people who collaborate on it, so access questions get a straight answer.
What Claude adds (3)
3 toolsThree tools that put something new in Box. No source spells out their confirmation, so the general rule below applies.
upload_file
Approval: see the rulePlaces a brand new file into Box, for example a summary or a draft produced during the conversation.
upload_file_version
Approval: see the ruleReplaces an existing file with fresh contents by sending the whole new file as its next version.
create_folder
Approval: see the ruleAdds a new folder where you tell it to, ready to receive files.
What Claude checks with you before acting in Box
By default, Claude stops and asks before each action it takes on an account for you. The prompt shows up in the conversation at the moment it matters.
On Team and Enterprise workspaces, owners decide whether members may let some actions through without being asked each time. They can also narrow what a connector may do for the whole organization, keeping reading on and uploads off, for instance. Nobody overrides that from a personal account. Box adds its own layer: an agent never sees more than the person who connected, and Box admins decide which tools are on at all.
Which plans the Claude Box connector is on
None of the 819 sheets in the official directory shows plan availability. The answer connector by connector is published nowhere: a real hole in the catalog, not a gap in our reading.
What is published is the general rule. Remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile; desktop extensions install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner opens a connector for the organization before members can each sign in. For the live state of Box, the connector's sheet in the official directory is the one place to look.
Where the Box connector stops
A connector is not an automation. Claude calls these tools while it answers you, so nothing starts when a file is uploaded, shared or approved.
This connector is documented by Box alone: no Claude help article covers it. The tool list is an observed floor, not a promise, and an administrator can open actions that appear on no public sheet. The partner badge is not a security audit either, and Anthropic states on every sheet that it neither picks the tools a publisher exposes nor guarantees how they behave. For a connector whose official sources contradict each other, see the Claude gmail connector page.
Need help connecting Box to Claude?
A person reads every message.
