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

# Connect other clients

> Generic setup for any MCP client that supports remote streamable HTTP servers.

Any client that supports remote MCP servers over streamable HTTP can connect to LeadLex.

| Setting | Value |
| - | - |
| Server URL | `https://mcp.leadlex.com/mcp` |
| Transport | Streamable HTTP |
| Authentication | OAuth 2.1 with dynamic client registration, or the `X-API-Key` header |

## OAuth

If your client supports OAuth for MCP, give it the server URL only. It discovers everything else from the server's metadata. See [Authentication](https://docs.leadlex.com/mcp-server/authentication.md#discovery).

## API key

If your client lets you set custom headers, use a workspace API key:

```json theme={null}
{
  "mcpServers": {
    "leadlex": {
      "type": "http",
      "url": "https://mcp.leadlex.com/mcp",
      "headers": {
        "X-API-Key": "wbk_your_api_key"
      }
    }
  }
}
```

The exact field names (`type`, `url`, `headers`, `serverUrl`) differ between clients. Check your client's documentation for its spelling.

## Test the connection with curl

An unauthenticated request returns `401` and a `WWW-Authenticate` header that points to the OAuth metadata:

```bash theme={null}
curl -i -X POST https://mcp.leadlex.com/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
```

To send the request with a workspace API key, add `-H "X-API-Key: wbk_your_api_key"`.


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