Box MCP: Official Server, but an Admin Must Enable It
Yes — Box has an official MCP server. The remote Box MCP server, hosted by Box at mcp.box.com and generally available since August 2025, lets any MCP-compatible AI search, read, and reason over the files and folders in your Box account — while enforcing your existing Box permissions. So if you’re searching “Box MCP,” the connection you want is real and Box built it.
One honest nuance before you get excited: the remote server has to be switched on by a Box admin in the Admin Console, so an individual user on a locked-down enterprise account can’t just connect on their own. And the deeper thing worth knowing is what MCP is at all: an MCP server hands your Box content to an AI inside a conversation you start. It’s a doorway, not a worker. Nothing watches Box for you, nothing fires when a file lands in a folder, and nothing runs while the chat is closed. Here’s exactly what the Box MCP does, how to turn it on, where it stops — and what to use when you want Box work that runs on its own.
Box is one of many — the complete list of MCP servers covers every app that ships one, grouped by category.
What the Box MCP server does
Model Context Protocol (MCP) is the open standard that lets an AI client — Claude, ChatGPT, Cursor, Copilot Studio, Mistral Le Chat, and others — talk to an outside app through a shared interface. Box hosts its server remotely, so there’s nothing to run yourself: you point a client at mcp.box.com and it acts through your Box login, seeing only what you’re already allowed to see. Box’s MCP docs cover the details.
With it connected, an AI client can:
- Find files and folders — “pull the latest signed contract in the Acme folder” answered from live Box content, not a guess.
- Query across documents with Box AI — ask a question that spans several files and get a grounded answer, with metadata extracted from the underlying documents.
- Read and summarize — have the AI open a document and summarize it, or compare two versions, without you downloading anything.
- Use Box content as context — draft a new document, a summary, or an email using what’s actually stored in Box as the source material.
It’s genuinely useful for ad-hoc work: ask a question, get an answer grounded in your real files, all while Box’s native permissions and governance decide what the AI can touch.
How to set up the Box MCP server
The remote server is the quick path — no code, no hosting — but it does start with an admin:
- A Box admin enables MCP in the Admin Console and, for custom clients, creates Integration Credentials (OAuth client ID, secret, redirect URI, and scopes like Content Actions). On many enterprise accounts this is the step that gates everything else.
- In your AI client’s connector settings, add a remote MCP server pointing at
mcp.box.com. - Authorize it against your Box account through the OAuth prompt — you’re granting the AI the same access your own user has, nothing more.
- Confirm the tools appear in the client, then start a chat and ask it to find or summarize a file.
If you’re not the admin on your Box account, step one is a message to whoever is. For everyone else, connecting Box to AI this way is a few minutes of setup.
Where the Box MCP stops
None of this is a knock on MCP — it’s just the shape of the protocol. Four limits show up the moment you want more than a conversation:
- It only works inside a chat you start. Close the window and nothing happens. The AI doesn’t watch Box; it waits for you to ask.
- No triggers. A new file uploaded to a folder, a document moving through an approval, a contract nearing its renewal date — none of these can start anything through MCP. There’s no “when this happens in Box, do that.”
- It’s one app at a time. The Box MCP knows Box. Getting a signed contract into your CRM, a Slack channel, and a billing tool means wiring up (and authing) a separate MCP server for each, then hoping your client can juggle them in one turn.
- You own the plumbing and the scopes. The admin enablement, the OAuth credentials, and the blast radius of read/write access to your content are all on your side to set up and govern.
So the Box MCP is a great way to ask your Box content questions and pull files into a chat. It is not a way to make Box run — to have work happen on a schedule or in reaction to an event, across the other tools a document touches.
Running Box work that doesn’t need a chat open
That “run on its own, across apps” gap is exactly where Carly fits. Carly connects to Box natively — no MCP server to enable, no OAuth plumbing to maintain — and to the ~260 other apps it supports natively, plus anything with a public API through your own key. The difference from MCP is the important part: Carly’s workflows are triggered and scheduled, so Box work happens whether or not anyone has a chat window open.
A few things that MCP can’t do but a Carly workflow can:
- When a new file lands in a Box folder → extract its key fields, log a row in your finance sheet, and notify the owner in Slack — automatically, the moment it arrives.
- Every morning → check for contracts in Box with a renewal date in the next 30 days and email the list to the account manager.
- When a deal closes in your CRM → create the client’s Box folder from a template, copy in the signed agreement, and post the link to the project channel.
The non-AI steps — the moving, matching, and routing between apps — are free and unlimited, the Zapier-style backbone of the workflow. The AI steps (drafting, summarizing, deciding) start at $35/month. You describe the outcome in plain language and Carly wires up the Box connection and everything downstream.
If you just want to interrogate your files from a chat, Box’s official MCP server is the right tool. If you want Box to actually do things — on a trigger, on a schedule, across every app a document flows through — that’s the job MCP wasn’t built for, and it’s the one Carly was.
FAQ
Does Box have an official MCP server?
Yes. Box hosts a remote MCP server at mcp.box.com, generally available since August 2025, that gives MCP-compatible AI clients access to search, Box AI, and your files and folders — with your existing Box permissions enforced.
Is the Box MCP server free to connect, and what does it require? Connecting the remote server is free; you’re authorizing an AI client against your existing Box account and permissions. The catch is that a Box admin has to enable MCP in the Admin Console first, so on a managed enterprise account you may need an admin to turn it on before you can connect.
Can the Box MCP trigger automations? No. MCP is request/response inside an AI chat — it has no triggers and nothing runs when the conversation is closed. For event- or schedule-driven Box work across apps, you need a workflow tool like Carly rather than an MCP server.
Can I connect Box to AI without coding or hosting a server? Yes. You don’t have to touch MCP at all. Carly connects to Box for you and lets you build the automation in plain language — describe what you want to happen and it wires up the file storage and the other apps involved, with no server to host and no code to write.
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
