Connect to Box changedthird-party/claude-desktop/connectors-box
Nearest release: v2.1.274, published an hour after upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 16 Sep 2026 21:29 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 20 Oct 2026 18:07 UTC.
Upstream edited
Recorded here
Lines+46added
Lines−48removed
From line
10
where the diff opens
First seen
16 Sep 2026
this site's first read of the page
Recorded edits4to this page, all time
The whole hunk
from line 10, old and new numbered
/
from line 10
1010
1111## Set up the Box server
1212
13<Steps>
14 <Step title="Create the client in Box">
15 In the Box Admin Console, create integration credentials for the Box MCP server as described in Box's [remote MCP server guide](https://developer.box.com/guides/box-mcp/remote), with `http://127.0.0.1:53280/callback` as the redirect URI, and copy the generated client ID and client secret.
16 </Step>
13**1. Create the client in Box**
1714
18 <Step title="Install the secret helper script on every device">
19 Write a script that prints the client secret as the JSON object `{"clientSecret": "…"}` and nothing else on stdout (the full contract is under [Where the client secret goes](/docs/third-party/claude-desktop/mcp-sign-in#where-the-client-secret-goes)). On macOS, save the script (for example at `/usr/local/bin/box-mcp-secret`) and mark it executable:
15In the Box Admin Console, create integration credentials for the Box MCP server as described in Box's [remote MCP server guide](https://developer.box.com/guides/box-mcp/remote), with `http://127.0.0.1:53280/callback` as the redirect URI, and copy the generated client ID and client secret.
2016
21 ```bash theme={null}
22 #!/bin/sh
23 printf '{"clientSecret":"%s"}' "YOUR_BOX_CLIENT_SECRET"
24 ```
17**2. Install the secret helper script on every device**
2518
26 On Windows, save it as a `.cmd` file, for example `C:\Program Files\Corp\box-mcp-secret.cmd`:
19Write a script that prints the client secret as the JSON object `{"clientSecret": "…"}` and nothing else on stdout (the full contract is under [Where the client secret goes](/docs/third-party/claude-desktop/mcp-sign-in#where-the-client-secret-goes)). On macOS, save the script (for example at `/usr/local/bin/box-mcp-secret`) and mark it executable:
2720
28 ```bat theme={null}
29 @echo off
30 echo {"clientSecret":"YOUR_BOX_CLIENT_SECRET"}
31 ```
21```bash theme={null}
22#!/bin/sh
23printf '{"clientSecret":"%s"}' "YOUR_BOX_CLIENT_SECRET"
24```
3225
33 A secret written into the script is readable by anyone who can read the file. Where your devices have a secret store or vault CLI, have the script read the secret from there instead.
26On Windows, save it as a `.cmd` file, for example `C:\Program Files\Corp\box-mcp-secret.cmd`:
3427
35 Distribute the script through your device management to the same absolute path on every device, in a location users can't modify. An entry holds one path for the whole organization, so if your fleet mixes macOS and Windows, add one entry per platform with its own name and script path, and assign each to the matching group of users with [per-group permission policies](/docs/third-party/claude-desktop/admin-console#per-group-permission-policies).
36 </Step>
28```bat theme={null}
29@echo off
30echo {"clientSecret":"YOUR_BOX_CLIENT_SECRET"}
31```
3732
38 <Step title="Add the server in the Enterprise Admin Console">
39 In the Enterprise Admin Console ([claude.ai](https://claude.ai) → **Organization settings**), open the **Connectors** page under **Desktop 3P**. Under **Managed MCP servers**, click **Add → Blank** and fill in the entry:
33A secret written into the script is readable by anyone who can read the file. Where your devices have a secret store or vault CLI, have the script read the secret from there instead.
4034
41 | Field | Value |
42 | - | - |
43 | **Name** | `Box` |
44 | **Transport** | **Streamable HTTP** |
45 | **URL** | `https://mcp.box.com` |
46 | **OAuth** | **Bring your own client** |
47 | **Client ID** | The client ID from step 1 |
48 | **Client secret helper script** | The script's absolute path from step 2, for example `/usr/local/bin/box-mcp-secret` |
49 | **Authorization server** | `["https://api.box.com"]` |
35Distribute the script through your device management to the same absolute path on every device, in a location users can't modify. An entry holds one path for the whole organization, so if your fleet mixes macOS and Windows, add one entry per platform with its own name and script path, and assign each to the matching group of users with [per-group permission policies](/docs/third-party/claude-desktop/admin-console#per-group-permission-policies).
5036
51 Click **Save changes**. Users' apps pick up the new entry as described under [Configuration updates](/docs/third-party/claude-desktop/admin-console#configuration-updates). Devices need outbound HTTPS access to `mcp.box.com`, `account.box.com`, and `api.box.com`.
37**3. Add the server in the Enterprise Admin Console**
5238
53 If you manage configuration through MDM or a bootstrap server instead, the equivalent entry can carry the secret inline:
39In the Enterprise Admin Console ([claude.ai](https://claude.ai) → **Organization settings**), open the **Connectors** page under **Desktop 3P**. Under **Managed MCP servers**, click **Add → Blank** and fill in the entry:
5440
55 ```json theme={null}
56 {
57 "name": "Box",
58 "transport": "http",
59 "url": "https://mcp.box.com",
60 "oauth": {
61 "clientId": "YOUR_BOX_CLIENT_ID",
62 "clientSecret": "YOUR_BOX_CLIENT_SECRET",
63 "authorizationServer": ["https://api.box.com"]
64 }
65 }
66 ```
67 </Step>
41| Field | Value |
42| - | - |
43| **Name** | `Box` |
44| **Transport** | **Streamable HTTP** |
45| **URL** | `https://mcp.box.com` |
46| **OAuth** | **Bring your own client** |
47| **Client ID** | The client ID from step 1 |
48| **Client secret helper script** | The script's absolute path from step 2, for example `/usr/local/bin/box-mcp-secret` |
49| **Authorization server** | `["https://api.box.com"]` |
6850
69 <Step title="Have users connect">
70 Each user opens **Customize → Connectors** in Claude Desktop, clicks **Connect** next to **Box**, and signs in to Box in the browser.
71 </Step>
72</Steps>
51Click **Save changes**. Users' apps pick up the new entry as described under [Configuration updates](/docs/third-party/claude-desktop/admin-console#configuration-updates). Devices need outbound HTTPS access to `mcp.box.com`, `account.box.com`, and `api.box.com`.
52
53If you manage configuration through MDM or a bootstrap server instead, the equivalent entry can carry the secret inline:
54
55```json theme={null}
56{
57 "name": "Box",
58 "transport": "http",
59 "url": "https://mcp.box.com",
60 "oauth": {
61 "clientId": "YOUR_BOX_CLIENT_ID",
62 "clientSecret": "YOUR_BOX_CLIENT_SECRET",
63 "authorizationServer": ["https://api.box.com"]
64 }
65}
66```
67
68**4. Have users connect**
69
70Each user opens **Customize → Connectors** in Claude Desktop, clicks **Connect** next to **Box**, and signs in to Box in the browser.
7371
No line in this hunk matches that.