# Connecting an MCP client

The MCP endpoint is:

```text
https://dtrgbxembnbwlmpvhhms.supabase.co/functions/v1/cortex-mcp/mcp
```

The bare function root (`https://dtrgbxembnbwlmpvhhms.supabase.co/functions/v1/cortex-mcp`) also speaks MCP, for clients that will not accept a path suffix.
Authenticate with your organization's `ck_…` token as a Bearer token — see
[Authentication](/authentication).

## Clients with native remote MCP (HTTP)

```json
{
  "mcpServers": {
    "cortex": {
      "type": "http",
      "url": "https://dtrgbxembnbwlmpvhhms.supabase.co/functions/v1/cortex-mcp/mcp",
      "headers": { "Authorization": "Bearer ck_your_token" }
    }
  }
}
```

## Stdio-only clients, via `mcp-remote`

```json
{
  "mcpServers": {
    "cortex": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote", "https://dtrgbxembnbwlmpvhhms.supabase.co/functions/v1/cortex-mcp/mcp",
        "--header", "Authorization: Bearer ck_your_token"
      ]
    }
  }
}
```

## After connecting

- `tools/list` returns the tools this token may call — see [Tool scoping](/tool-scoping).
- Have the agent call [`get_data_coverage`](/tools/read-discovery#get_data_coverage) first in a
  new session, and load the [context pack](/context-pack) once per session before answering
  questions about the data.
- Supported protocol versions and methods are listed in [Protocol & methods](/protocol).