> ## Documentation Index
> Fetch the complete documentation index at: https://developer.box.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Choose between the Box Agents API and the Box MCP server

> Compare the Box Agents API (A2A) and the Box MCP server (MCP) to decide how your agent or application connects to Box.

Box supports two open protocols for connecting AI agents to Box: the Agent2Agent (A2A) protocol through the [Box Agents API](https://developer.box.com/ai/agents-api/index.md), and the Model Context Protocol (MCP) through the [Box MCP server](https://developer.box.com/guides/box-mcp/index). Use this page to decide which one fits your integration, or how to use both.

## 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.

The A2A project describes the protocols as complementary: MCP gives a single agent more capabilities, and A2A lets agents collaborate. For the full comparison, see [A2A and MCP](https://a2a-protocol.org/latest/topics/a2a-and-mcp/) on the A2A protocol site.

## How Box supports each protocol

| | Box MCP server | Box Agents API |
| - | - | - |
| **Protocol** | MCP | A2A v1.0 over HTTP+JSON or JSON-RPC 2.0 |
| **Endpoint** | `https://mcp.box.com` | `https://api.box.com/a2a` |
| **What you connect to** | Box tools for files and folders, search, Box AI, hubs, Doc Gen, and more | The Box Agent, or a custom agent you build in Box AI Studio |
| **Who decides the steps** | Your agent chooses which Box tools to call | The Box agent plans and runs the work |
| **Setup** | An admin enables the Box MCP server in the Admin Console and creates integration credentials | You create a platform app with the **Manage AI** scope in the Developer Console, and an admin authorizes it. Apps and agent platforms connect through the agent's Agent Card. |
| **Authentication** | OAuth 2.0 | OAuth 2.0, JWT, or Client Credentials Grant |
| **Multi-turn conversations** | Managed by your agent | Built in, with sessions identified by `contextId` |
| **What comes back** | Tool results | A task with an answer, plus optional structured citations, search results, and files the agent created |

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](https://developer.box.com/guides/box-mcp/permission-aware-access.md).

## 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.

To get started, see [Set up the MCP server](https://developer.box.com/guides/box-mcp/setup) and [Available tools](https://developer.box.com/guides/box-mcp/tools.md).

## 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.

To get started, see the [Box Agents API](https://developer.box.com/ai/agents-api/index.md).

## Use both together

The protocols work well side by side. For example, an orchestrator agent can use the Box MCP server for discrete operations, such as uploading a file or setting metadata, and use the Box Agents API to hand a broader question to a Box agent that reasons across files, folders, and hubs.

**RELATED GUIDES**
