Labelbox MCP server

The Labelbox platform MCP server connects your AI agent to your workspace. Ask your agent to inspect projects, summarize labeling progress, or set up a project when you approve write access. Operators and project managers can use it to monitor progress, review quality, and identify work that needs attention. Developers can use the same tools from their coding assistants. You do not need to write code to use Labelbox tools through a compatible AI assistant. Connect from Recursion or another compatible MCP client. To configure another client, use this server URL:

https://api.labelbox.com/v1/agent-tools/mcp

You sign into Labelbox and approve the connection in your browser. You do not need an API key, client secret, or SDK installation.

Before you connect

You need:

A Labelbox account with access to a workspace.
A workspace where external MCP access is available and allowed by your administrator.
Access to Recursion, or a client that supports remote MCP over Streamable HTTP and OAuth sign-in.

Your existing roles and permissions determine what the agent can access. Approval does not add permissions to your account.

This URL connects to the Labelbox platform. The documentation MCP searches docs. To manage Recursion agents and sessions from an MCP client, see Recursion MCP.

Connect to Recursion

Use the Labelbox integration in Recursion to give your managed agents access to a Labelbox workspace. You do not need to enter an MCP URL or copy an API key. You need a developer or admin role in the Recursion organization to connect the integration and assign it to agents. The connection is shared within that organization; each agent must be granted access before it can use it.

Add the Labelbox integration

Open Recursion and select the organization where your agents run. Go to Integrations → Add integration and select Labelbox.

Choose an access level

Select Read only to inspect Labelbox data, or Read and write for workflows that change it. Choose Continue to Labelbox.The access level applies to agents using this connection. To change it later, reconnect with the access level you need.

Authorize the workspace

Sign into Labelbox if prompted. Select the workspace you want to connect and review the requested access. You can Limit access to selected projects and review Stay connected between sessions when offered.Choose Allow access to return to Recursion. Your current Labelbox permissions still apply.

Test the connection

Back in Recursion’s Integrations, confirm the Labelbox connection is Active. Open its actions menu and choose Test connection. Confirm the check succeeds before assigning access to an agent.

Give an agent access

Open your agent in Agents → Configuration. Under Tools → Integrations, choose Add integration, then select the Labelbox connection.Keep Labelbox MCP tools enabled, choose Use this access, and select Save new version. The agent’s configuration now lists the Labelbox integration and its access level.Start a session with the saved agent version to verify the connection. The agent also needs a Recursion environment before you can launch a session.

For more on agent access, versions, and reconnecting, see Recursion integrations.

Connect another MCP client

In Claude, open Customize → Connectors and add a custom connector. For a managed account, an organization owner may need to add it first.

Name it Labelbox and enter the server URL:

https://api.labelbox.com/v1/agent-tools/mcp

Keep OAuth sign-in enabled. If asked how to identify the client, select automatic registration. Leave static credentials and request headers empty.
Finish adding the connector and start sign-in. Complete Approve access in your browser.
Enable the Labelbox connector for your conversation, then verify the connection.

Availability depends on your Claude account and organization policy. See Claude’s remote connector instructions for current controls.

Open ChatGPT on the web and go to Plugins. Choose Add custom MCP server from the add menu.

Name it Labelbox and enter this server URL:

https://api.labelbox.com/v1/agent-tools/mcp

Choose OAuth authentication and automatic client registration if offered. You do not need a static client ID or secret.
Complete the setup and the Labelbox approval flow. Find the resulting plugin in Plugins and install it before using it in a conversation.
Select Labelbox with @ in a conversation, then verify the connection.

Your ChatGPT account and workspace policy must allow custom MCP connections. See OpenAI’s custom MCP instructions if the controls differ or are unavailable.

Add the following entry to ~/.cursor/mcp.json. Merge it with your existing mcpServers entries if the file already exists.

{
  "mcpServers": {
    "labelbox": {
      "url": "https://api.labelbox.com/v1/agent-tools/mcp"
    }
  }
}

Open Cursor’s MCP controls, find labelbox, and start its sign-in flow. Keep Cursor open while you complete authorization in your browser.Continue with Approve access, then return to Cursor’s Agent chat to verify the connection.See Cursor’s MCP documentation for configuration locations and client controls.

Add the remote server:

codex mcp add labelbox --url https://api.labelbox.com/v1/agent-tools/mcp

If sign-in does not start automatically, run:

codex mcp login labelbox

Complete Approve access in your browser. Start or reopen your Codex session, then use /mcp to check the server and verify the connection.See Codex’s MCP documentation for current client instructions.

Add the remote server for your user account:

claude mcp add --transport http --scope user labelbox https://api.labelbox.com/v1/agent-tools/mcp

Start an interactive Claude Code session and enter /mcp. Select the Labelbox server and authenticate.Complete Approve access in your browser, then return to Claude Code to verify the connection.The --scope user option stores the configuration for your user across projects. It does not grant Labelbox permissions.See Claude Code’s MCP documentation for current client instructions.

Use your client’s remote MCP setup instructions. Enter the Labelbox server URL and select Streamable HTTP if the client asks for a transport.

https://api.labelbox.com/v1/agent-tools/mcp

Start the client’s OAuth sign-in flow, complete Approve access, and verify the connection.Compatibility depends on the client’s OAuth implementation. Hosted clients and browser connectors can have different account requirements and setup steps.

Approve access

Sign into Labelbox

Start authorization from your MCP client. Sign into Labelbox in the browser when prompted. Use your own account rather than an impersonated session.

Select a workspace

Choose an eligible workspace for this connection. This choice applies to the MCP client and does not switch your existing browser workspace.If no workspace appears, see Troubleshooting.

Review the requested access

Check the client name and requested access. Select optional access only if you need it:

Allow project changes permits supported project setup tools, subject to your current permissions.
Limit access to selected projects restricts the connection to the projects you select.
Stay connected between sessions permits connection renewal when the client supports and requests it.

These options depend on the access requested by your client and what your workspace permits.

Allow access

Choose Allow access to approve the connection. You can cancel if you do not want to grant access.

Return to your client

Keep the client open until authorization completes. Confirm that the Labelbox server connects and its tools appear.

Verify the connection

Ask your agent:

Use Labelbox to show my connected workspace and access restrictions.

The agent should call get_caller_context and return the selected workspace and connection restrictions. Confirm that the workspace is the one you intended. A browser redirect alone does not confirm success. The client must complete authorization and receive a tool response. You can also ask:

Use Labelbox to list projects I can access in this workspace.

An empty result can be valid. Projects accessible through user groups may not appear in the list. To check a specific project, give the agent its project ID or Labelbox project URL and ask it to look up that project directly.

What you can do

Your client discovers the current tools available to your connection from the server. Available actions depend on your permissions and approved access. You can ask:

What can you do with my current Labelbox connection?

These are representative workflows, rather than a complete list of available tools:

Workflow	Example prompt
Inspect workspace and projects	”Show my workspace and summarize this project’s health.”
Inspect project data	”Which datasets and batches are attached to this project?”
Track progress and quality	”Summarize progress, throughput, and benchmarks for this project.”
Inspect workflow queues	”Show the queues in this project.”
Audit a label’s history	”Show how reviewers changed this label, step by step.”
Set up projects with write access	”Create a project with an ontology and instructions, then add a batch from my existing dataset.”
Manage project members with write access	”Invite these people to this project as labelers, then make Ana a reviewer.”

The project setup and member workflows require approved write access, workspace write availability, and the permissions for each action. In Recursion, choose Read and write when connecting; other clients may offer Allow project changes during approval. A connection limited to selected projects cannot create a new project or use other workspace-level tools.

Permissions and connection lifetime

Labelbox checks your current permissions on every tool call. The connection’s approved access and selected projects can further restrict the agent.

A connection applies to one workspace.
Project restrictions limit access; they do not grant a new role or project membership.
Your client controls its own tool confirmations and automation settings. Labelbox consent does not guarantee a confirmation before each tool call.
Review how your client handles the data returned by tools.

Clients can request different access. A basic connection may be read-only, and Stay connected between sessions may not be offered. Missing options do not necessarily indicate an error. If you approve renewal, a compatible client can renew the connection between sessions. Connections can still expire or be revoked. Without renewal, you must sign in again when access expires. To change the approved access, start a new authorization flow from your client. To switch workspaces, follow I want to connect another workspace.

Manage connections

Disconnect your client

Open workspace settings and find Connected MCP clients. This section lists your connections across workspaces. Choose Disconnect for the client you want to remove and confirm the action. The connection stops working after the disconnect succeeds. Sign out of your client or remove its server entry if you also want to clear its local configuration. Signing out of the Labelbox website does not disconnect an approved MCP connection.

Control workspace access

Workspace administrators with permission to manage the workspace can use Workspace MCP access in workspace settings.

Allow external MCP connections controls whether users can connect external clients. Disabling it disconnects existing clients.
Disconnect all clients invalidates the workspace’s existing connections without changing whether new connections are allowed.

Re-enabling access does not restore earlier connections. Users must connect and approve access again. Workspace access must also be available through Labelbox. If the administrator allows access but the workspace remains unavailable, contact support.

Troubleshooting

No workspace is available for this connection

Confirm that you signed into the correct Labelbox account and belong to the workspace. Ask a workspace administrator to check Allow external MCP connections.If access is allowed but the workspace remains absent, contact Labelbox support to check availability.

The request is invalid or expired

Return to your MCP client and start a fresh connection. Do not reuse a bookmarked consent page or a callback from an earlier attempt.

Localhost refused the connection after approval

The client may have stopped listening for the browser callback or the attempt may have timed out. Keep the client open and restart its authorization flow.For a local desktop client, complete sign-in in a browser on the same computer. A refused callback does not necessarily mean that your Labelbox session expired.

The connection was cancelled

Start authorization again from your client when you are ready to approve access. A callback from a cancelled attempt cannot complete a new connection.

Tools do not appear after approval

Check the client’s MCP connection status and authentication errors. Confirm that the server uses the platform URL at the top of this guide.If authorization did not complete, start a fresh sign-in flow. Use get_caller_context to verify the workspace after the tools appear.

My project list is empty or a project is missing

Confirm the connected workspace and selected-project restrictions. An empty result is valid when no projects match the connection’s access.Project lists may omit projects accessible through user groups. Give the agent the project’s exact ID or Labelbox project URL and ask it to look up that project directly.If that lookup fails, check your project permissions with an administrator.

A tool is missing or access is denied

Check your role permissions, approved connection access, selected projects, and workspace MCP policy. A restricted connection can have fewer tools than an unrestricted connection.Confirm permissions with your administrator. Reconnect if you need a different grant. Contact support if the expected access still fails.

Write access or Stay connected is not offered

Your client must request the corresponding access. Project changes also require workspace write availability. Check your client’s OAuth options and ask an administrator or support about workspace availability.Keep read-only access if it meets your needs. If you change the client’s requested access, start a new authorization flow. Do not edit a browser authorization URL.

My connection expired or stopped working

Reconnect from your client. Check that you still belong to the workspace and that external access remains allowed.An administrator can revoke connections or disable workspace access. Re-enabling access does not restore old grants; approve a new connection.

I want to connect another workspace

Disconnect or clear the Labelbox MCP authentication in your client, then authorize again and select the other workspace. You do not need to sign out of Labelbox in your browser.After reconnecting, ask your agent to call get_caller_context and confirm the selected workspace before using other tools.

The service is temporarily unavailable

Retry later. If the problem continues, contact Labelbox support.

For unresolved issues, include your client name, version, and a description of the failed step when you contact support. Do not share tokens, cookies, or full authorization callback URLs.

Getting started

Integrations

Label data

Manage data

Explore data

Manage models

Manage team

Access & usage

Updates

Labelbox MCP server

Before you connect

Connect to Recursion

Connect another MCP client

Approve access

Verify the connection

What you can do

Permissions and connection lifetime

Manage connections

Disconnect your client

Control workspace access

Troubleshooting

​Before you connect

​Connect to Recursion

​Connect another MCP client

​Approve access

​Verify the connection

​What you can do

​Permissions and connection lifetime

​Manage connections

​Disconnect your client

​Control workspace access

​Troubleshooting

Before you connect

Connect to Recursion

Connect another MCP client

Approve access

Verify the connection

What you can do

Permissions and connection lifetime

Manage connections

Disconnect your client

Control workspace access

Troubleshooting