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

# MCP server

> Use Tracks from Claude Code, Cursor, Codex or another MCP client

Tracks is also an MCP server at `https://tracks.alpic.ai/mcp`. Connect it to an MCP client to start runs, follow them and launch experiments from a conversation. See every [tool](https://docs.tracks.alpic.ai/reference/mcp/tools.md) it offers, and [Use from your agent](https://docs.tracks.alpic.ai/use-from-your-agent.md) to choose between the MCP server and the CLI.

It takes an API key of your organization, created in **API keys** in the web app, as `Authorization: Bearer trk_...`. Clients that can't send this header, such as ChatGPT and Claude.ai connectors, can't connect yet.

The examples below read the key from `TRACKS_API_KEY` in your environment.

**Claude Code**

```bash theme={null}
claude mcp add --transport http tracks https://tracks.alpic.ai/mcp \
  --header "Authorization: Bearer $TRACKS_API_KEY"
```

Your shell replaces `$TRACKS_API_KEY` with the key, which Claude Code then keeps in its configuration.

**Cursor**

In `.cursor/mcp.json` in your project, or `~/.cursor/mcp.json` for every project:

```json theme={null}
{
  "mcpServers": {
    "tracks": {
      "url": "https://tracks.alpic.ai/mcp",
      "headers": { "Authorization": "Bearer ${env:TRACKS_API_KEY}" }
    }
  }
}
```

Cursor reads `TRACKS_API_KEY` from the environment it was started in: set it in your shell profile.

**Codex**

In `~/.codex/config.toml`:

```toml theme={null}
[mcp_servers.tracks]
url = "https://tracks.alpic.ai/mcp"
bearer_token_env_var = "TRACKS_API_KEY"
```

**Other clients**

Add a remote MCP server over Streamable HTTP, with the URL `https://tracks.alpic.ai/mcp` and the header `Authorization: Bearer trk_...`.


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