Connect Box to V7 Go

🚧

Preview

This feature is new and evolving. Details on this page may change as we
improve it.

V7 Go connects to Box through Box's hosted MCP server, so the agent can
search and read files from chats, playbooks, and workflows.

A Box admin creates Integration Credentials on the Box MCP server
in Admin Console and pastes the Client ID and Client Secret into the
connect card.

The short version

1. In Go, open Integrations → MCP Connectors → Box — or ask the agent
   in chat to use Box. A connect card appears.
2. In the Box Admin Console, open
   Integrations, search for Box MCP server, and click
   Configure.
3. Under Additional Configuration, add Integration Credentials and
   save.
4. Add the callback URI from the card as the Redirect URI. Select
   root_readwrite and ai.readwrite. Skip docgen.readwrite unless
   the account has an Enterprise Advanced license.
5. Copy the Client ID and Client Secret into the card. Never paste
   them into chat.
6. Press Connect and complete Box's authorization popup.

Troubleshooting

• Redirect URI mismatch. Paste the card's callback URI into Additional
  Configuration, then reconnect.
• 403 after connect. The credentials omitted root_readwrite or
  ai.readwrite, or the Box user cannot see the content. Users can only
  reach files they already have permission to view in Box.
• A Developer Console custom OAuth app also works if Admin Console MCP
  credentials are unavailable: User Authentication (OAuth 2.0), same
  redirect URI, same scopes.

For messages Go shows on the connect card, see
MCP connector errors.

FAQ

Who can connect? Any Go user can paste credentials. The Box-side steps
need a Box admin.

Is the connection shared? Connections follow the sharing policy on the
connector page.

What can the agent do? Search and read files your Box user can already
see. Ask "what Box tools do you have?" for the live list.