Boxes MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BOXES_MCP_DATA_FILE | Yes | Path to the inventory JSON file used by the MCP server (as shown in the client config example). | |
| BOXES_MCP_MEDIA_DIR | Yes | Path to the directory where media files (photos) are stored and served from. | |
| BOXES_WEBHOOK_SECRET | No | Optional: secret used to verify signed webhook HMAC signatures when running the webhook receiver. | |
| BOXES_EXPORT_REQUEST_URL | No | Optional: URL of an approved Boxes export endpoint to use with the request_export tool. | |
| BOXES_EXPORT_ALLOWED_HOSTS | No | Optional: comma-separated hostname allowlist for export endpoint HTTPS requests. | |
| BOXES_EXPORT_REQUEST_TOKEN | No | Optional: authentication token for the export endpoint. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_inventoryA | Search object names, descriptions, tags, locations, and custom fields in the local Boxes mirror. |
| get_inventory_objectA | Get one inventory record by its stable Boxes MCP ID. |
| list_contentsA | List records directly inside a space or box using an external or stable parent ID. |
| inventory_totalsA | Return record counts, quantity, and declared value grouped by object type and currency. |
| documentation_auditB | Find item records missing selected claim-documentation fields in the local mirror. |
| get_sync_statusA | Return import, image, and webhook freshness for the private local mirror. |
| request_exportA | Request a full account export through a provider-approved endpoint configured by the user. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose: search, get single, list by parent, aggregate totals, audit gaps, sync status, and export. No overlap in functionality, so an agent can reliably select the right tool.
All tool names follow a consistent verb_noun pattern (search_inventory, get_inventory_object, list_contents, inventory_totals, documentation_audit, get_sync_status, request_export). This makes the set predictable and easy to navigate.
Seven tools is a well-scoped number for an inventory mirror server. Each tool addresses a specific need without bloat, and the count is within the ideal 3-15 range.
The tool set covers search, retrieval, listing, totals, audit, sync status, and export—covering the key workflows for a read-only mirror. The only minor gap is the lack of a direct 'trigger sync' or 'refresh' tool, but the presence of sync status and export mitigates this.