How the protocols differ
The two protocols connect different things:- MCP connects an agent to tools. Your agent discovers the tools a server offers, decides which ones to call, and combines the results itself.
- A2A connects agents to each other. Your agent or application hands a task to another agent, which plans and runs the work and returns the result.
How Box supports each protocol
Both run with the caller’s Box permissions. Neither protocol gives an agent access to content that the authenticated user or service account can’t already open. For more on how identity, scopes, and content permissions apply to agents, see Permission-aware agent access.
When to use the Box MCP server
Use the Box MCP server when:- Your agent or agent platform supports MCP, and you want it to work with Box content directly.
- You want your own model to decide which steps to take, such as searching, reading a file, then writing metadata.
- You need specific Box operations, such as uploading files, managing collaborations, or generating documents with Doc Gen.
When to use the Box Agents API
Use the Box Agents API when:- Your application or agent platform speaks A2A, and you want to hand a task to a Box agent.
- You want to call a custom agent that your organization configured in Box AI Studio.
- You need multi-turn sessions or structured citations in the response.
- Your integration runs on a server and authenticates as a service account with JWT or Client Credentials Grant.
