MCP Gateway · OpenCode
Connect Box to OpenCode
Release bundles, exports and logs often end up in shared Box folders that someone has to keep in order. From the OpenCode terminal, through the Speakeasy MCP Gateway, you can list a folder's contents, set up a folder for a new release and describe and tag folders so others can find them. Tool output is blocked at the gateway rather than in OpenCode's hooks.
- Category
- Productivity
- Tools
- 21
- Authentication
- OAuth
- OpenCode
- Terminal
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.
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
- Sign in to the Box Admin Console.
- Enable the Box AI API or Box Doc Gen if users need those tools.
- Under Integrations, add credentials for the Custom Box MCP Server.
- Set the Speakeasy redirect URI and copy the Client ID and Client Secret.
- Choose access scopes and save.
Set up
Add Box to OpenCode in 4 steps
- 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.
- 02
Choose who can use Box
Give teams the
mcp:connectscope on the Box server through team access or a role. OpenCode connects to the Box server's own URL, and the server's authorization decides who can connect and which tools they can call. - 03
Connect OpenCode
Add the server to OpenCode's own mcp config block as a remote server.
Copy the server's URL from its hosted install page in Speakeasy.
Add it to the
mcpblock of your OpenCode config withtypeset toremote.Restart OpenCode and sign in when prompted.
{ "mcp": { "<server slug>": { "type": "remote", "url": "<URL from the hosted install page>" } } } - 04
Sign in and use Box from OpenCode
The first time OpenCode 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 OpenCode, limited to what the person's access allows, and every call lands in the gateway's tool logs.
OpenCode doesn't receive MCP servers from plugins. The observability package is installed separately, from a ZIP or with speakeasy-hooks install --provider=opencode, and the device agent can maintain it.
Use cases
What OpenCode users do with Box
List a folder from the shell
OpenCode lists the files, folders and web links inside a Box folder, then reads the folder's details, so you know what is already there before a script adds more.
Set up the folder for a release
Find the parent folder for your releases by name, then create the new release folder under it as part of your release checklist.
Tag and describe release folders
Give each release folder a short description and tags such as the version and environment, so people searching Box find the right build.
Tools
21 tools
Each Box tool can be allowed or denied per team and role at the MCP Gateway before OpenCode 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"
}Control
What Speakeasy can see and stop in OpenCode
The gateway covers every client the same way. The rest depends on what OpenCode 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 OpenCode. MCP-scoped policies are enabled per organization.
Prompt and tool-call blocking
OpenCode
The OpenCode plugin sends each prompt and tool call to Speakeasy, which allows or denies it before it runs.
Usage telemetry
OpenCode
Token and cost totals flow through the plugin, reported per turn.
Device agent
OpenCode
The device agent installs and maintains the observability package.
- OpenCode has no OpenTelemetry exporter, so session data comes through the plugin.
- Tool output is blocked at the gateway rather than in OpenCode's hooks.
Questions
Frequently asked questions
Does OpenCode get Box through a plugin?
Who pays for Box API calls made from OpenCode?
How do OpenCode users get Box?
Are Box calls from OpenCode logged?
Connect more