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

# Merlin MCP

The Merlin MCP server lets you use [Merlin](https://docs.encord.com/platform-documentation/GettingStarted/encord-merlin.md) from your own AI tools. Use natural language in Claude, Cursor, Codex, or any MCP-compatible client to work with your Projects, Ontologies, data, Workflows, and analytics.

## Prerequisites

* An Encord account (cloud). Merlin uses OAuth via WorkOS and is not available on on-premises or air-gapped deployments.
* A supported MCP client, such as Claude, Cursor, or Codex.

## Connect your AI agent to the Merlin MCP server

> [!NOTE]
>
> **Choose your region's endpoint.** Merlin is available in two regions. Use the URL that matches where your Encord organization's data is hosted:
>
> * **EU:** `https://mcp.encord.com/mcp`
> * **US:** `https://mcp.us.encord.com/mcp`

> [tab] Claude Code
>
> Run the following command in your terminal:
>
> ```bash EU theme={"dark"}
> claude mcp add --transport http encord-merlin https://mcp.encord.com/mcp
> ```
>
> ```bash US theme={"dark"}
> claude mcp add --transport http encord-merlin https://mcp.us.encord.com/mcp
> ```
>
> The first time you call a Merlin tool, Claude Code opens a browser to sign in with your Encord account.

> [tab] Claude Desktop
>
> **For Team/Enterprise plans:**
>
> 1. An organization admin must first add the connector in [**Admin settings** > **Connectors**](https://claude.ai/settings/connectors) with the URL `https://mcp.encord.com/mcp` or `https://mcp.us.encord.com/mcp`.
> 2. Members then add the same connector under [**Settings** > **Connectors**](https://claude.ai/settings/connectors).
> 3. Restart Claude Desktop for the changes to take effect.
>
> **For Individual plans:**
>
> Add the server to your `claude_desktop_config.json`:
>
> ```json EU theme={"dark"}
> {
>   "mcpServers": {
>     "encord-merlin": {
>       "type": "http",
>       "url": "https://mcp.encord.com/mcp"
>     }
>   }
> }
> ```
>
> ```json US theme={"dark"}
> {
>   "mcpServers": {
>     "encord-merlin": {
>       "type": "http",
>       "url": "https://mcp.us.encord.com/mcp"
>     }
>   }
> }
> ```

> [tab] Claude Web
>
> **For Team/Enterprise plans:**
>
> 1. An organization admin must first add the connector in [**Admin settings** > **Connectors**](https://claude.ai/settings/connectors) with the URL `https://mcp.encord.com/mcp` or `https://mcp.us.encord.com/mcp`.
> 2. Members then add the same connector under [**Settings** > **Connectors**](https://claude.ai/settings/connectors).
> 3. Refresh [claude.ai](https://claude.ai) for the changes to take effect.
>
> **For Individual plans:**
>
> 1. Go to [claude.ai/customize/connectors](https://claude.ai/customize/connectors).
> 2. Click **Add custom connector**.
> 3. Paste the server URL above and confirm: `https://mcp.encord.com/mcp` or `https://mcp.us.encord.com/mcp`.
> 4. Complete the browser sign-in to authorize access.

> [tab] Cursor
>
> [Click here to configure automatically](cursor://anysphere.cursor-deeplink/mcp/install?name=encord\&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vbWNwLmVuY29yZC5jb20vbWNwIn0%3D) to add Merlin to Cursor.
>
> Or add the following to your Cursor MCP configuration:
>
> ```json EU theme={"dark"}
> {
>   "mcpServers": {
>     "encord-merlin": {
>       "type": "http",
>       "url": "https://mcp.encord.com/mcp"
>     }
>   }
> }
> ```
>
> ```json US theme={"dark"}
> {
>   "mcpServers": {
>     "encord-merlin": {
>       "type": "http",
>       "url": "https://mcp.us.encord.com/mcp"
>     }
>   }
> }
> ```

> [tab] Codex
>
> Run the following commands in your terminal:
>
> ```bash EU theme={"dark"}
> codex mcp add encord --url https://mcp.encord.com/mcp
> codex mcp login encord
> ```
>
> ```bash US theme={"dark"}
> codex mcp add encord --url https://mcp.us.encord.com/mcp
> codex mcp login encord
> ```

> [tab] Other
>
> Merlin uses the standard MCP streamable-HTTP transport. Point any MCP-compatible client to:
>
> ```EU theme={"dark"}
> https://mcp.encord.com/mcp
> ```
>
> ```US theme={"dark"}
> https://mcp.us.encord.com/mcp
> ```
>
> The client runs an OAuth authorization flow against WorkOS on first use. Every WorkOS-backed login method (SSO, email, etc.) is supported.

## Authentication

Merlin authenticates using **OAuth**. When your AI tools first call a Merlin tool, they open a browser window and prompt you to sign in with your Encord credentials. The session is managed by WorkOS. Merlin itself never stores your credentials.

MCP authorizations last for up to 14 days. After an authorization expires, your AI tool prompts you to authorize access again.

> [!NOTE]
>
> You must sign in as an Encord user whose account was created (or backfilled) after Merlin launched. If your sign-in succeeds but tool calls are rejected, contact your workspace admin.

> [!NOTE]
>
> If you belong to any Workspace that requires MFA, sign in to Encord and complete MFA in the same browser session before authorizing Merlin. This requirement applies even when you use Merlin with another Workspace that does not require MFA.

## Using Merlin with multiple Workspaces

Every action Merlin takes is scoped to one Workspace. If you belong to only one Workspace, it's used automatically. If you belong to several, your AI tool may ask which one to use, then keeps using it until you ask to switch. You can only use Workspaces you're a member of that have an active subscription.

Example:

"Show me my available Workspaces."

"Switch my active Workspace to Data Operations."


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.