Box
Upload, download, and manage files and folders in Box.
About
Box ships in the w6w first-party pack. It declares 10 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.box- Version
- 0.1.2
- Author
- w6w
- Licence
- MIT
- Categories
- Storage
Overview
Box handles file and folder management inside a workflow — uploading, downloading, browsing folder contents, creating shared links, and searching across a Box account. It authenticates via OAuth2 scoped to the account’s fixed application scopes, and the download action follows Box’s own redirect to whichever regional content host serves the file, so a workflow doesn’t need to special-case that URL itself.
Uploads are sent as Box’s documented multipart layout, with the file’s metadata written before its content, matching what Box’s own API requires and avoiding the ordering error Box’s docs warn about.
Health reporting keeps three separate questions apart: is Box’s service up, via its public status page; is the current connection’s credential still valid; and whether request quota remains — the last of which Box does not expose, so it is declared absent rather than guessed. A live credential check is never treated as proof there’s no outage, and vice versa.
Build with Box
Three routes to the same 10 actions. The Workflow tab is generated from Box's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Box's real ids.
{
"manifestVersion": "2",
"name": "box-example",
"steps": [
{
"id": "create-folder",
"uses": {
"app": "io.w6w.box",
"action": "create-folder",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"name": "<name>"
}
}
]
}Here are some of the things you can do
-
Create Folder
performcreate-folder -
Create Shared Link
performcreate-shared-link -
Download File
readdownload-file -
Get File
readget-file -
Get Folder
readget-folder
+5 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Box, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Box. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "upload-file",
payload: {
fileName: "<value>",
content: "<value>",
// parentId: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action upload-file --payload '{"fileName":"<value>","content":"<value>"}'Give an AI agent Box — without giving it Box's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.box#create-folder",
"input": {
"name": "<name>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Box connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Box's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Box itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Box declares its own checks, so its health is a property of the app rather than something the host guesses at.
Box platform status
Atlassian Statuspage rollup for status.box.com, with per-component detail. Unauthenticated and unsigned.