Skip to main content
Back to the Box MCP server

MCP Gateway · Claude Cowork

Box icon

Connect Box to Claude Cowork

Some Box work runs to dozens of files: reviewing a deal room, cleaning up a project folder, compiling a report from many sources. In Cowork, Claude can work through a whole folder as one task through the Speakeasy MCP Gateway, then save the result back to Box. Speakeasy can deny a prompt before the step runs, and the session export shows who ran each job.

Category
Productivity
Tools
21
Authentication
OAuth
Claude Cowork
Cowork tab in Claude Desktop

Behind the MCP Gateway

Run Box MCP behind the MCP Gateway

One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Box call inspected and logged.

Deploy on MCP Gateway

Before you start

What Box needs first

A Box Admin or Co-Admin does the Box side of the setup.

  • You need a Box Admin or Co-Admin account for the enterprise.
  • Box AI tools need an eligible Box AI plan or purchased Box AI Units. Doc Gen needs an Enterprise Advanced license.
  • Box meters and bills API calls made with the integration credentials.

In Box

  1. Sign in to the Box Admin Console.
  2. Enable the Box AI API or Box Doc Gen if users need those tools.
  3. Under Integrations, add credentials for the Custom Box MCP Server.
  4. Set the Speakeasy redirect URI and copy the Client ID and Client Secret.
  5. Choose access scopes and save.
Full Box setup guide in the docs

Set up

Add Box to Claude Cowork in 4 steps

  1. 01

    Add Box from the catalog

    An admin finds Box in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.

    Box uses OAuth. Servers that support dynamic client registration get their OAuth configuration applied automatically.

    Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.

  2. 02

    Choose who can use Box

    Give teams the mcp:connect scope on the Box server through team access or a role. Claude Cowork connects to the Box server's own URL, and the server's authorization decides who can connect and which tools they can call.

  3. 03

    Connect Claude Cowork

    Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork.

    New MCP servers join the project's default plugin automatically. Each server's overview page shows which plugin it is published to, with Publish or Update to change it.

    Add the importing admin's GitHub username as a marketplace collaborator and accept the invite. Only that admin needs it.

    In Claude Organization settings > Plugins & skills, select Add > Sync from GitHub and pick the organization's plugin repository. The Claude GitHub App must be installed on it.

    Mark the observability plugin Required, and set the plugin that carries this server to Available to install or Installed by default.

    In the Cowork tab's Monitoring settings, set the OTLP endpoint, protocol and headers.

  4. 04

    Sign in and use Box from Claude Cowork

    The first time Claude Cowork connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.

    Box needs its own OAuth grant, so each person connects it once. Until they do, Box calls fail while the rest of the gateway keeps working.

    From then on, Box's tools appear in Claude Cowork, limited to what the person's access allows, and every call lands in the gateway's tool logs.

Cowork reads the synced repository, so a new session picks up plugin changes. Members who receive plugins through Cowork don't need a GitHub invitation.

Use cases

What Claude Cowork users do with Box

Review a folder of documents

Cowork goes file by file through a folder, reads each document and leaves a comment on the ones that need changes, so owners see the feedback in Box.

list_folder_content_by_folder_idget_file_contentcreate_file_comment

Clean up a project folder

At the end of a project, Cowork renames files to one convention, adds descriptions and tags, and labels the folder so it is easy to find in a year.

list_folder_content_by_folder_idupdate_file_propertiesupdate_folder_properties

Compile a report from many files

Cowork searches Box for the quarter's updates, pulls the text from each one and uploads a single combined summary to the team folder.

search_files_keywordget_file_contentupload_file

Tools

21 tools

Each Box tool can be allowed or denied per team and role at the MCP Gateway before Claude Cowork sees it.

who_am_i

Returns detailed information about the currently authenticated Box user. This tool provides comprehensive user profile data including basic identification, contact information, role details, and account settings.

Example input

Get current user information

{}

search_folders_by_name

Searches for folders by name within Box using keyword matching. This tool helps locate specific folders by their names and can be scoped to search within a particular parent folder. Returns basic folder information including ID, type, and name for each matching folder.

Example inputs (5)

Basic folder search

{
  "folder_name": "Project Documents",
  "limit": 30
}

Search within specific parent folder

{
  "folder_name": "2024 Reports",
  "ancestor_folder_id": "123456789",
  "limit": 50
}

Search for folders with partial name match

{
  "folder_name": "Finance",
  "limit": 20
}

Limited results search

{
  "folder_name": "Marketing Campaign",
  "ancestor_folder_id": "987654321",
  "limit": 10
}

Search in root directory and limit results by date

{
  "folder_name": "Shared Resources",
  "created_at_range": "2023-01-01T00:00:00Z,2023-12-31T23:59:59Z"
}

list_folder_content_by_folder_id

Lists files, folders, and web links contained in a folder. Returns a paginated list of items with at least fields. Fields (id, type, name, etag) are always returned. Use folder_id "0" for the root folder.

Example inputs (3)

Basic folder listing

{
  "folder_id": "0",
  "limit": 50
}

List with specific fields

{
  "folder_id": "123456789",
  "fields": [
    "id",
    "name",
    "type",
    "size",
    "modified_at",
    "created_by"
  ],
  "limit": 100
}

Paginated listing

{
  "folder_id": "987654321",
  "fields": [
    "id",
    "name",
    "type",
    "path_collection"
  ],
  "limit": 30,
  "offset": 60
}

search_files_keyword

Searches for files using keywords and supports metadata filters, file extension filtering (without dots), and field selection. Maps to Box's searchForContent API with comprehensive filtering capabilities.

Example inputs (5)

Basic keyword search (returns core fields only)

{
  "query": "contract agreement",
  "limit": 50
}

Advanced search with additional fields

{
  "query": "quarterly report",
  "file_extensions": [
    "pdf",
    "docx"
  ],
  "ancestor_folder_id": "123456789",
  "fields": [
    "createdAt",
    "modifiedAt",
    "size",
    "createdBy"
  ]
}

Searching by date

{
  "query": "quarterly report",
  "file_extensions": ["pdf", "docx"],
  "ancestor_folder_id": "123456789",
  "created_at_range”: "2023-01-01T00:00:00Z,2023-12-31T23:59:59Z",
  "fields": ["createdAt"]
}

Search with metadata filters and additional fields

{
  "query": "invoice",
  "file_extensions": [
    "pdf"
  ],
  "limit": 30,
  "fields": [
    "contentCreatedAt",
    "pathCollection",
    "metadata"
  ],
  "mdfilters": [
    {
      "scope": "enterprise",
      "templateKey": "invoiceTemplate",
      "filters": {
        "amount": {
          "gt": 1000,
          "lt": 5000
        },
        "status": "approved",
        "department": "finance"
      }
    }
  ]
}

Multi-template metadata search with custom fields

{
  "query": "project document",
  "fields": [
    "modifiedBy",
    "sharedLink",
    "tags",
    "permissions"
  ],
  "mdfilters": [
    {
      "scope": "enterprise",
      "templateKey": "projectTemplate",
      "filters": {
        "priority": "high",
        "deadline": {
          "gt": "2024-01-01"
        }
      }
    },
    {
      "scope": "global",
      "templateKey": "reviewTemplate",
      "filters": {
        "reviewer": "john.doe@company.com"
      }
    }
  ]
}

get_file_content

Extracts and returns file content for files under 50MB. Prefers the markdown representation (preserves document structure for better LLM use) and falls back to extracted text when markdown is not available.

list_tasks

Lists all tasks associated with a specific file. This tool retrieves task information including task details, message, status, and completion rule, due date from the Box platform.

Example input

List tasks for a file

{
  "file_id": "1234567890"
}
See all 21 tools

Control

What Speakeasy can see and stop in Claude Cowork

The gateway covers every client the same way. The rest depends on what Claude Cowork exposes to Speakeasy.

Tool logs

Gateway

Every Box call is logged with the person and the client that made it.

Access by role

Gateway

People reach only the Box tools their team or role allows.

Request and response blocking

Gateway

A risk policy scoped to Box can reject a tool request before it reaches the server, or withhold a result from Claude Cowork. MCP-scoped policies are enabled per organization.

Prompt blocking

Claude Cowork

Agent hooks send each prompt to Speakeasy, which allows or denies it before the step runs.

Session telemetry

Claude Cowork

Cowork's OTLP export ties sessions to people and feeds observability.

Anthropic inference hooks

Claude Cowork

On Claude Enterprise, prompts can be checked before inference (beta).

  • Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies.
  • Personal Claude accounts can't be governed in Cowork.

Questions

Frequently asked questions

Which Box scopes does Cowork get?
The access scopes the Box admin chose when creating the integration credentials. Speakeasy roles can then narrow which of the 21 Box tools a team can call.
Do Cowork sessions pick up Box plugin changes?
Yes. Cowork reads the synced plugin repository, so a new session picks up plugin changes.
How do Claude Cowork users get Box?
An admin adds Box from the Speakeasy MCP Catalog and grants access by team or role. Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork. Each person then sees only the Box tools their access allows.
Are Box calls from Claude Cowork logged?
Yes. Box calls go through the MCP Gateway, which logs each tool call and attributes it to the person and the client that made it.

Connect more

Box in other clients

AI everywhere.

Control here.