> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://developer.deel.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://developer.deel.com/_mcp/server.

# Connecting clients

> Configure your AI client to connect to the Deel MCP server

The Deel MCP server is compatible with any client that implements the Model Context Protocol over HTTP transport. This page provides setup instructions for common AI clients.

The server URL for all clients is:

```
https://api.letsdeel.com/mcp
```

## Client setup

#### Cursor

Add the following to your `~/.cursor/mcp.json` file. To learn more, see the Cursor [documentation](https://docs.cursor.com/context/model-context-protocol).

```json
{
  "mcpServers": {
    "deel": {
      "url": "https://api.letsdeel.com/mcp"
    }
  }
}
```

Cursor supports OAuth2 natively. When you first use a Deel tool, Cursor redirects you to the Deel authorization screen to grant access.

#### VS Code

Add the following to your `.vscode/mcp.json` file in your workspace. To learn more, see the VS Code [documentation](https://code.visualstudio.com/docs/copilot/chat/mcp-servers).

```json
{
  "servers": {
    "deel": {
      "type": "http",
      "url": "https://api.letsdeel.com/mcp"
    }
  }
}
```

VS Code Copilot handles the OAuth2 flow automatically when you connect to the server.

#### Claude Desktop

Add the following to your `claude_desktop_config.json` file. On macOS, this file is located at `~/Library/Application Support/Claude/claude_desktop_config.json`. On Windows, it is at `%APPDATA%\Claude\claude_desktop_config.json`.

```json
{
  "mcpServers": {
    "deel": {
      "url": "https://api.letsdeel.com/mcp"
    }
  }
}
```

Claude Desktop handles the OAuth2 authorization flow when you first interact with the Deel MCP server.

#### ChatGPT

You can enable MCP servers on ChatGPT if you have a Pro, Plus, Business, Enterprise, or Education account. Follow the [OpenAI documentation](https://platform.openai.com/docs/guides/developer-mode) for instructions. Use the following parameters when setting up your custom connector:

* **Server URL**: `https://api.letsdeel.com/mcp`
* **Connection mechanism**: OAuth

ChatGPT manages the OAuth2 flow through its connector interface.

#### Other

MCP is an open protocol supported by many clients. Refer to your client documentation for specific configuration steps. Use the following parameters:

* **Server URL**: `https://api.letsdeel.com/mcp`
* **Transport**: HTTP with SSE
* **Authentication**: OAuth2 (preferred) or Bearer token

If your client supports OAuth2, configure it to use the OAuth connection mechanism. If your client does not support OAuth2, pass a personal access token in the `Authorization` header:

```json
{
  "mcpServers": {
    "deel": {
      "url": "https://api.letsdeel.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_PERSONAL_ACCESS_TOKEN"
      }
    }
  }
}
```

See the [authorization](/mcp/authorization) page for details on obtaining a token.

## Verifying your connection

After configuring your client, verify the connection by asking the AI agent to list available tools or perform a simple operation.

**Example prompts to test the connection:**

* "List my Deel contracts"
* "What time-off policies are available?"
* "Show my organization details"

If the connection is successful, the agent invokes the appropriate Deel MCP tool and returns results from the Deel platform.

## Troubleshooting

#### 401 Unauthorized on connection

**Cause**: The MCP client has not completed the OAuth2 authorization flow, or the token has expired.

**Solutions**:

* Restart the MCP connection in your client to trigger the OAuth2 flow
* If using a personal access token, verify the token is valid and correctly formatted in the `Authorization` header
* Check that the token has not expired (access tokens are valid for 1 hour)

#### Tools not appearing

**Cause**: The client is not discovering tools from the server.

**Solutions**:

* Verify the server URL is exactly `https://api.letsdeel.com/mcp` (no trailing slash)
* Confirm the client supports HTTP transport for MCP (not just stdio)
* Restart the client and reconnect to the MCP server
* Check client logs for connection errors

#### Connection timeout

**Cause**: Network connectivity issues or firewall restrictions.

**Solutions**:

* Verify you can reach `https://api.letsdeel.com` from your network
* Check that your firewall or proxy allows outbound HTTPS connections to `api.letsdeel.com`
* If you are behind a corporate proxy, configure your client to use the proxy settings

#### OAuth consent screen does not appear

**Cause**: The client is not handling the OAuth2 redirect correctly.

**Solutions**:

* Ensure your client supports OAuth2 for MCP connections
* Check that pop-ups or redirects are not blocked in your environment
* Try using a personal access token as an alternative authentication method

## Next steps

#### [Tools reference](/mcp/reference/tools-reference)

Browse the full list of available MCP tools

#### [Authorization](/mcp/authorization)

Understand the OAuth2 discovery and authorization flow

#### [Error handling](/mcp/error-handling)

Handle errors when invoking MCP tools

#### [Best practices](/mcp/best-practices)

Optimize your MCP integration for production use