BoxHero MCP integration for AI agents.
Connect AI agents to BoxHero through 4 structured actions, including get item, get team info, and list items. Review authentication, inputs, workflows, and s…
- ACTION CONTRACTS
- 4
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the BoxHero integration exposes
The BoxHero Agent App exposes 4 provider-backed actions for productivity and data work. Its current contract lets an authorized agent get a single boxhero inventory item by item identifier, get the linked boxhero team information and team mode, and list boxhero inventory items with optional location filters and cursor pagination. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected BoxHero account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real BoxHero capabilities.
Showing 4 of 4 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_itemREADGet a single BoxHero inventory item by item identifier.
INPUTS: item_id / location_ids
get_team_infoREADGet the linked BoxHero team information and team mode.
list_itemsREADList BoxHero inventory items with optional location filters and cursor pagination.
INPUTS: item_ids / location_ids / cursor / limit
list_locationsREADList BoxHero locations available to the linked team.
INPUT CONTRACTS
Know what the action needs before it runs.
get_item
item_idREQUIRED- The BoxHero item identifier.
location_idsOPTIONAL- The location identifiers used to calculate quantity.
list_items
item_idsOPTIONAL- The item identifiers to filter by.
location_idsOPTIONAL- The location identifiers used to calculate quantity.
cursorOPTIONAL- The cursor returned by a previous BoxHero list_items response.
limitOPTIONAL- The maximum number of items to return.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Item
Get a single BoxHero inventory item by item identifier. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_itemVerify with Get Team Info
Get the linked BoxHero team information and team mode. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_team_infoSAFETY BOUNDARY
Operate BoxHero with explicit limits
- Authorize BoxHero with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned BoxHero data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in BoxHero rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the BoxHero task completed successfully.
CONNECTION MODEL
API key
BoxHero API token sent with the Authorization Bearer header. Generate it from Settings > Integrations in the BoxHero web app.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 4
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by BoxHero.