MCP server - Tracks

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 it offers, and Use from your agent 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
Cursor
Codex
Other clients

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.

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

{
  "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.

In ~/.codex/config.toml:

[mcp_servers.tracks]
url = "https://tracks.alpic.ai/mcp"
bearer_token_env_var = "TRACKS_API_KEY"

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