Your files, in your bucket.
Uploads, assets, backups and exports in Appbricx storage or your own R2 or S3 bucket, with permissions per file.
StorageProject bucket
r2 · acme-files tested, files moved
- Files, assets, backups and exports
- 4 areas
- Cloudflare R2, Amazon S3 or S3-compatible
- Your bucket
- Who may read, update and delete
- Per file
- For agents, never credentials
- storage tool
What you get
Every file, one place
Uploads and assets in folders, with backups and exports beside them.
Your bucket, moved safely
R2, S3 or compatible, per workspace or project. Deleted files stay deleted.
Permissions per file
Read, update and delete for users, roles, workspaces or the public.
Agents manage files
The MCP storage tool lists, reads, uploads and moves. Never credentials.
Upload, share and list
// components/ContractUpload.tsx, with @appbricx/ui
const app = useAppHandle();
const { id } = await app.upload(file, {
permissions: { read: ["users"] },
});
// server/contracts.ts: only legal, not through rows
await ctx.files.setPermissions(id, {
read: ["role:legal"],
by_reference: false,
});
// your agent, over MCP
storage { "action": "list", "area": "files", "prefix": "contracts/" }
Questions
Can I use my own bucket?
Yes. A workspace, or a single project, can keep its files in Cloudflare R2, Amazon S3 or any S3-compatible service. Saving tests the bucket first, and existing files are copied over in the background.
Can a deleted file come back after a move?
No. While files are copied, reads fall back to the old place and deletes reach both, and copies left by earlier moves are pruned. A deleted file stays deleted.
Can my agent see the bucket's credentials?
No. The MCP storage tool lists, reads, uploads and moves files and sets their permissions. The bucket and its keys are set by a workspace owner or admin in the console, never by an agent.
Ship it with your agent.
claude mcp add --transport http appbricx https://appbricx.com/api/mcp