Manage Box files with AI
Locate a file, check its current state and verify an authorised change. Tell the difference between a sent invitation and access the recipient can already use.
Manage Box files with AI by identifying the right document before asking for a change. Two installation guides can have identical names while one is still a design draft and the other has been approved for customers. Folder, version and audience are more reliable clues than the name alone.
The box-mcp guide starts with the tools actually available to your account. It can check metadata, read the present state and look for evidence that a change reached its destination. If a transfer times out, checking before another attempt can prevent a duplicate file or invitation.
What it does
- Find a file in a specified part of a workspace
- Distinguish two versions using their folder and metadata
- Check whether an invitation has become effective access
- Verify the parent and version of an uploaded document
- Recognise when a search result covers only part of the collection
Install and use
- Use a compatible agent with an authorised Box MCP connection. Identify the intended folder, file and recipient where relevant. A transfer also needs a client allowed to reach the destination.
- Ask, “Find the approved installation guide in the release folder. Show me whether our reviewer already has access before changing anything.”
- Inspect the returned file and current role. If you authorise an update, ask the agent to read the state again and distinguish a pending invitation from a completed change.
FAQ
Source
Made by Box. Original skill: box-mcp, published on GitHub under the MIT licence.
View on GitHub