Skip to main content
The Labelbox MCP server gives an AI assistant tools for your Labelbox workspace: it can inspect projects and their data, and summarize labeling progress and quality. It works with Recursion. Add it to the MCP client that already uses the Recursion MCP endpoint, and one conversation can read your labeling work and start agent sessions on it.
For the Labelbox MCP server, you need a Labelbox account with access to a workspace where external MCP access is available and allowed by an administrator, and an MCP client that supports Streamable HTTP with OAuth sign-in, such as Claude Code, Codex, or Cursor. For Recursion, you need an API key, and starting a session needs an agent, an environment, and the Developer or Admin role. See Connect to the Recursion MCP and Sessions.

​
Connect the Labelbox MCP server

Add this server address to your MCP client:
Start Claude Code, enter /mcp, select the server, and authenticate.
Your browser opens. Sign in to your Labelbox account, choose the workspace this connection uses, review the requested access, and choose Allow access. Keep the client open until it reports the server as connected. The connection works with the permissions your Labelbox account already has; approving it adds none. A connection may be read-only. Whether you can also allow project changes depends on the access your client requests and on what your workspace permits. For Claude, ChatGPT, and other clients, the access options, and how to disconnect a client, see the Labelbox MCP server guide.

​
Check both connections

Start a new session in your client and ask:
The first answer names the workspace you chose. The second lists the agents in your Recursion organization. If either is missing, see What can go wrong.

​
Use them together

With both servers connected, your client can read from one and act in the other. For example:
Your client calls the Labelbox MCP server’s tools first, then starts the session through the Recursion MCP endpoint. Open Sessions in the console to follow the agent’s work. See Sessions. Another prompt to try:
  • “Which datasets and batches are attached to this project? Start a session that checks them against our data checklist.”
What your client passes into a session is kept with that session’s history. See Data handling before you send workspace content.

​
Agents that run in Recursion

The Labelbox MCP server signs you in through your browser, so you connect it to your MCP client, as on this page. It isn’t a server you add to an agent’s own MCP servers: an agent that runs in Recursion reaches a server with a token stored in a vault. See MCP servers. To give such an agent context from your Labelbox workspace, have your client read it and pass it in the session’s first message, as in the prompt above.

​
What can go wrong

The most common problems:
  • No workspace is offered during sign-in. You signed in to a different account, or the workspace doesn’t allow external MCP connections. Ask a workspace administrator to allow them. If they’re allowed and the workspace is still missing, contact support as the guide below describes.
  • The tools don’t appear after you approve. The client stopped waiting before authorization finished. Keep the client open, start its sign-in again, and check its MCP status.
  • A tool is missing or access is denied. Your permissions are checked on every call, and a connection limited to selected projects offers fewer tools. Check your role and the access you approved, then connect again if you need more.
  • The Recursion tools don’t appear, or calls return 401 unauthorized. The API key isn’t set where the client started, or it expired. See Connect to the Recursion MCP.
For every other connection problem with the Labelbox MCP server, see the troubleshooting section of the Labelbox MCP server guide.

​
Next steps

Labelbox MCP server guide

Set up other clients, choose access options, and manage connections.

Connect to the Recursion MCP

Connect the docs server and the authenticated endpoint with an API key.

Sessions

Start, steer, and follow the sessions your client creates.

MCP servers

Give an agent that runs in Recursion tools from a server that takes a token.