Box
Let your coding agent upload, organize, and share project files in Box with folder permissions without leaving the chat.
Overview
com.mcparmory/box is a MCP server for the Operate phase that lets coding agents manage Box files, folders, and team access controls through stdio.
What is this MCP server?
- stdio MCP server (v1.0.5) for Box file and folder operations from Claude Code, Cursor, or Codex
- Team collaboration flows with access controls suited to client folders and shared specs
- Two install paths: PyPI via uvx (mcparmory-box) or OCI Docker (ghcr.io/mcparmory/box:1.0.5)
- Published through the mcparmory registry on GitHub for repeatable agent setups
- Keeps document handoffs out of ad-hoc zip/email loops when agents generate artifacts
- Server version 1.0.5 with 2 distribution packages (PyPI mcparmory-box + OCI Docker)
- stdio transport only per server.schema.json
- Source registry: github.com/mcparmory/registry
Community signal: 25 GitHub stars.
What problem does it solve?
Agents create files constantly, but getting them into the right shared Box folder with correct permissions still means context-switching out of your agent.
Who is it for?
Indie builders and micro-teams who already use Box for clients or compliance and want agents to file deliverables without manual uploads.
Skip if: Teams on Google Drive, S3-only, or local-only repos who do not pay for Box.
What do I get? / Deliverables
After you register the server, your agent can list, upload, and organize Box content with collaboration rules applied in line with your prompts.
- Agent-driven Box file and folder operations inside chat
- Shared deliverables placed under Box access rules you specify
- Repeatable local or containerized MCP server definition (v1.0.5)
Recommended MCP Servers
Journey fit
Canonical shelf is Operate because Box is where shipped work lives: shared assets, client deliverables, and team folders that need ongoing access control—not one-off build tasks. Infra fits managed cloud storage and collaboration plumbing that solo builders wire into agents and small-team workflows after the product exists.
How it compares
MCP integration to Box storage, not an agent skill that teaches file-management methodology.
Common Questions / FAQ
Who is com.mcparmory/box for?
Solo builders and small teams who rely on Box for shared project files and want Claude Code, Cursor, or similar agents to read and write there safely.
When should I use com.mcparmory/box?
Use it during Operate (and late Ship handoffs) whenever agents must place artifacts in governed folders, sync docs with collaborators, or respect Box access levels.
How do I add com.mcparmory/box to my agent?
Add the MCP server to your agent config using stdio, either `uvx mcparmory-box` from PyPI or the `ghcr.io/mcparmory/box:1.0.5` Docker image, with Box API credentials configured per mcparmory docs.