Box in Muse: what Meta's connector can read and change
- Last verified
- Updated Published
Box sits in Meta's list of Muse connectors, and, unusually among them, it has its own Muse setup page. That page is short, so most of what follows comes from Box's documentation for its MCP server, the service AI apps use to reach Box files. Here you'll find the admin switch Box puts in front of Muse, what the server's tools can read and change, which risky tools start off, how an admin can keep Muse to reading, how access ends, and what each company says about your files. It's written for owners and office staff who keep contracts, job photos, permits or client paperwork in Box.
What the labels mean here:
| Label | Meaning on this page |
|---|---|
| Confirmed by vendor | The claim comes from Box, Meta or Zapier themselves: their docs, a company post, their terms, Box's AI principles or Meta's privacy policy. |
| Unverified | No source settles it, or the only source is about Box's MCP server for all AI apps rather than Muse specifically. |
How we built it: every source listed was read on Nov 4, 2026. Meta's side gave us five documents: the small-business announcement, its help page on connectors, Muse's terms and privacy policy, and its developer rules for connectors. Box's side gave us its LinkedIn post, its Muse setup page, four pages on its MCP server and its AI principles with the matching FAQ. Zapier's side gave us its Muse page, its usage page and its Box app page. We didn't link Muse to any Box account, which leaves every claim untested and means we can't show the screens Box displays when Muse asks for access.
Short version
- Meta names Box as a Muse connector, and Box's post says Muse can find information in documents and help manage contracts using your Box content. (Confirmed by vendor 1 6)
- Box's setup page for Muse starts with a Box admin making Muse available in the Admin Console, then connecting from Muse. (Confirmed by vendor 7)
- Box says an AI app on its MCP server works as the person who signed in and sees only files that person can already open. (Confirmed by vendor 8 11)
- Box's tool list for the server includes uploading, copying, commenting and Box AI questions, and has no tool for deleting files or folders. (Confirmed by vendor 9)
- Tools that create shared links or invite collaborators start switched off until an admin turns them on. (Confirmed by vendor 9)
- A Box admin can limit any integration to read-only tools, or switch tools off one at a time. (Confirmed by vendor 10)
- Meta may train its AI on your Muse use, including what comes from connectors, until you turn the setting off under Data controls; it starts on. (Confirmed by vendor 5)
What Muse can read and change
Box's Muse page calls the setup "Muse with Box MCP Server", and has admins find Muse under the MCP category of integrations. (Confirmed by vendor 7) Neither company lists which of the server's tools Meta's connector actually calls. (Unverified) The table follows Box's published tool list. "Off" means Box ships the tool disabled.
| What | On Box's MCP server? | Label and source |
|---|---|---|
| Files and folders: reading | File contents, details and previews, folder details and folder listings; a download link tool starts Off (Confirmed by vendor 9) | Confirmed by vendor 9 |
| Search | Keyword and metadata search for files, and folder search by name (Confirmed by vendor 9) | Confirmed by vendor 9 |
| Files and folders: changing | On: upload a file, create a folder, copy files and folders. Off: move, rename or retag, upload a new version, set metadata (Confirmed by vendor 9) | Confirmed by vendor 9 |
| Comments and tasks | Read comments, tasks and who an item is shared with; add a comment (Confirmed by vendor 9) | Confirmed by vendor 9 |
| Sharing | Off: create shared links on files or folders, invite or change collaborators, including people outside your company (Confirmed by vendor 9) | Confirmed by vendor 9 |
| Box AI | Ask questions about one file, several files or a hub, and pull fields such as dates out of documents; the "Enhanced" extract tools cost more (Confirmed by vendor 9) | Confirmed by vendor 9 |
| Hubs | Read hubs; create, copy and add items to them; editing a hub's title starts Off (Confirmed by vendor 9) | Confirmed by vendor 9 |
| Doc Gen | Read templates and mark a file as a template; generating documents in bulk starts Off (Confirmed by vendor 9) | Confirmed by vendor 9 |
Connecting it
Meta's article gives two ways in: ask Muse to link a service, or tap Connect beside it on the Connectors screen in Settings and finish any sign-in the service asks for. (Confirmed by vendor 2) Before that, a Box admin opens Integrations in the Admin Console, finds Muse, and sets its availability to all users. Box says the request can also be made to Muse in a chat. (Confirmed by vendor 7) Box describes signing in with your Box credentials and granting the AI app permission to your content. (Confirmed by vendor 8) Under Muse's terms you must be 18 or over, and the services you link, and the access you grant them, are your responsibility. (Confirmed by vendor 4)
What we couldn't pin down:
- Accounts without an admin. We found nothing on how the admin step works for a one-person or free Box account. (Unverified)
- Plans. Neither company says which Box plans can use the Muse connector. (Unverified)
- Lookalikes. We didn't find another app named Muse in Box's documentation, but we couldn't search Box's integrations catalog, which loads only in a browser. (Unverified)
- Support. Nothing we read says whether Box or Meta handles problems with the connector. (Unverified)
Permissions and approvals
Three things cap what Muse can do in Box: your own Box permissions, your Box admin's tool settings, and Muse's approval prompts.
Box says scopes set the most an app may ask for but never open files the signed-in person can't, and that it checks collaborations, folder permissions and app scopes on every request. (Confirmed by vendor 11) The scopes Box lists for the server are root_readwrite, ai.readwrite and docgen.readwrite. (Confirmed by vendor 11) Which scopes Meta's connector requests isn't published. (Unverified)
In the Admin Console, an admin can give one integration its own tool settings, separate from the company default, and set each category to off, read-only, read and write, or a custom mix. Those settings cover everyone using that integration; Box doesn't support per-user controls. (Confirmed by vendor 10) On Enterprise Advanced, guardrails can also confine uploads to chosen folders or block outside collaborators. (Confirmed by vendor 10)
Meta's connector rules class each tool as a read, a write or a sensitive write. Ordinary reads and writes ask on first use and may then be switched to Always allow; sensitive writes prompt every single time, with no standing permission possible. (Confirmed by vendor 3) We don't know which class Meta assigned to Box's tools, for example whether creating a shared link counts as sensitive. (Unverified) Keep Box writes on ask. Section 7.6 of Muse's terms expects you to keep meaningful oversight of everything Muse does, reviewing its actions promptly. (Confirmed by vendor 4)
Disconnecting
To cut Muse off, open Settings, go to Connectors and disconnect Box. Data stops flowing, but Meta warns that anything Muse used earlier can linger in Muse's memory and past conversations; asking Muse to forget interactions is the remedy it offers. (Confirmed by vendor 2) Meta's rules also tell connector makers to delete or lock away data once access is revoked. (Confirmed by vendor 3)
On the Box side, an admin controls whether people can reach an integration at all from its Availability Status tab, and Box enforces a disabled tool straight away, even mid-session. (Confirmed by vendor 10) We found no Box page showing where an individual user can see or revoke Muse's access from their own account settings. (Unverified)
What happens to your data
- Model training at Meta. Meta's policy says: "You decide whether we can use your interactions with Muse to train and improve our AI models. This setting is on when you first use Muse. You can change it at any time using the toggle in your Settings under "Data controls."" It adds that interactions can include information from connectors, and that "The same toggle in your Settings controls whether that information can be used to improve AI at Meta." (Confirmed by vendor 5) The licence in section 2.3 of Muse's terms reaches content arriving from linked services, for purposes that include improving AI, subject to your Data Controls choice. (Confirmed by vendor 4) Contracts and client files are exactly what you may not want in that pool, so set the toggle before connecting.
- Training by Box. Box's AI principles say Box won't train models on customer content without explicit authorization, and its Box AI FAQ says its model providers don't train on data sent from Box. (Confirmed by vendor 12) That covers Box AI, not what Meta does with files Muse has read.
- How much Muse fetches. According to Meta, Muse is designed to swap with a connector just the data a task calls for, unless you ask for more. (Confirmed by vendor 2) Box says no files are permanently shared with the AI app, which queries Box in real time, and that every action is logged. (Confirmed by vendor 8) Those two statements describe different ends: what Muse keeps in memory after reading a file is governed by Meta, not Box.
- Which policies govern. Meta points to the connector's separate terms and privacy policy for how that service treats what it receives. (Confirmed by vendor 2) Section 4.2 of Meta's rules forbids connector makers any secondary use, naming selling, unrelated advertising and model training. (Confirmed by vendor 3)
Box's MCP server and other routes
- Box hosts the server at mcp.box.com and signs apps in with Box OAuth. (Confirmed by vendor 11)
- Admins can review MCP activity in two reports: daily tool-call counts by user and integration, and a per-event record of what third-party integrations accessed or changed. (Confirmed by vendor 10)
| Software | In Meta's launch-post connector list? | How else it connects | Label and source |
|---|---|---|---|
| Box | Yes (Confirmed by vendor 1) | Box's hosted MCP server, which Box documents for other AI apps too (Confirmed by vendor 7 11) | Confirmed by vendor 1 7 11 |
| Zapier | Zapier's docs describe connecting it from Muse's Connectors settings; Meta's launch post doesn't name it. (Confirmed by vendor 13) | Zapier is the bridge | Confirmed by vendor 1 13 |
Zapier's Box app has actions such as creating folders, text files and shared links, adding collaborators, comments and tasks, creating managed users, and a raw API request that carries your Box sign-in. (Confirmed by vendor 14) Each MCP call through Zapier uses two tasks of your plan. (Confirmed by vendor 13) If you go this way, leave out the sharing, user and raw API actions unless you need them.
Risks to keep a person on
Approvals are the main brake
Meta's help article states that by default Muse won't take many important actions, such as sending an email, without your go-ahead, that a good number of connectors allow a retrieve-only setup, and that Settings is where you adjust when Muse asks. (Confirmed by vendor 2) That is Meta describing Muse as a whole, not Box. We found no Box or Meta source saying the Box connector offers a retrieve-only setting inside Muse. (Unverified) At the Box end, an admin can hold an integration to read-only tools. (Confirmed by vendor 10) Until you know which applies, leave Muse's approvals for Box as they are.
Links that open files to anyone
Box's shared-link and collaboration tools can create open links or add people from outside your company, and they ship switched off. (Confirmed by vendor 9) If your admin turns them on, check the recipient and link settings before approving; a contract or a customer's ID shared openly is hard to pull back.
Uploads and copies land straight away
Uploading, copying and creating folders are on by default. (Confirmed by vendor 9) They run as you, inside folders you can edit. (Confirmed by vendor 11) A copy dropped into a folder shared with clients or crews is visible to them, so name the destination folder when you ask.
Comments under your name
Muse can add comments to files. (Confirmed by vendor 9) Collaborators see them as yours, so read them first.
Box AI costs
The Enhanced Extract tools cost more than the standard ones, and Box says to use them only when the user asks. (Confirmed by vendor 9) How Box bills Box AI use that comes through Muse isn't published. (Unverified)
What Muse remembers
Removing Box from Muse leaves earlier memories and chat history in place, and the training toggle is a separate control you set yourself. (Confirmed by vendor 2 5) Section 16 of the terms makes no guarantee that Muse can undo what it did. (Confirmed by vendor 4)
Treat this page as a summary of published sources, not as legal, privacy or records-retention guidance. Box and Meta revise their documentation and admin settings regularly; open the live pages before acting on anything here.
Trade guides that cover Box
None of our trade guides covers Box in detail so far. The guides for contractors, electricians and roofers each give it a row, paired with Dropbox, for storing job files. Bookkeepers and accountants mentions it as storage another app links to. The auto repair, cleaning, landscaping, pest control and restaurant guides name it only within Meta's connector list.
FAQ
Do I need a Box admin to connect Muse?
Box's setup page starts with an admin making Muse available in the Admin Console. (Confirmed by vendor 7) How that works for a single-user account isn't documented. (Unverified)
Can I give Muse read-only access to Box?
A Box admin can restrict an integration to read-only tools. (Confirmed by vendor 10) Section 3.1 of Meta's rules asks makers using OAuth to let users limit Muse to Read Only where possible. (Confirmed by vendor 3) Whether Box's connector has that choice in Muse is not documented. (Unverified)
Can Muse delete my files?
Box's published tool list has no delete tool, though moving, renaming and new versions are there, switched off by default. (Confirmed by vendor 9)Can Meta use my Box files for AI training?
By default, yes, unless you turn off the training toggle under Data controls. Meta's policy says that toggle starts on and also covers connector information. (Confirmed by vendor 5)Changes to this page
| Date | What changed | Sources |
|---|---|---|
| Nov 4, 2026 | First published. | All sources listed on this page |
Found a mistake or a newer source? Send it through Corrections, with a link to the source, and we'll recheck the claim and record the change here.
Sources
- Source 2: Meta Help Center “How Muse works with Connectors.” meta.com Also: https://www.meta.com/help/superintelligence/1687253048996149/
- Source 11: Box Dev Docs “Give an AI agent secure, permission-aware access to enterprise documents.” developer.box.com Also: https://developer.box.com/guides/box-mcp/setup
- Source 12: Box “Box AI Principles.” box.com Also: https://support.box.com/hc/en-us/articles/45720614801171-Box-AI-Frequently-Asked-Questions
- Source 13: Zapier “Connect Zapier MCP to Muse.” docs.zapier.com Also: https://docs.zapier.com/mcp/overview/usage